Difficulty: Easy
Correct Answer: System.Process, System.Drawing2D, System.Drawing3D
Explanation:
Introduction / Context:Knowing which namespaces actually exist in the .NET Framework is essential for correct using directives, type resolution, and avoiding compile-time errors. This question focuses on spotting invalid or mistyped namespaces.
Given Data / Assumptions:
Concept / Approach:Validate each candidate against commonly used namespaces. For example, processes are under System.Diagnostics (type Process), and drawing sub-namespaces use System.Drawing.Drawing2D, not System.Drawing2D. There is no System.Drawing3D in the BCL.
Step-by-Step Solution:
Check System.Process → Incorrect namespace; Process is a type in System.Diagnostics.Check System.Drawing2D → Incorrect; the real namespace is System.Drawing.Drawing2D.Check System.Drawing3D → Does not exist in the standard BCL.Check System.Web, System.Data, System.Threading, System.Xml → These are valid namespaces.Verification / Alternative check:Use an IDE’s object browser or official documentation to confirm exact namespace paths (e.g., GraphicsPath is in System.Drawing.Drawing2D).
Why Other Options Are Wrong:A and E include legitimate namespaces; D includes a wrong one but omits another; C mixes one real (System.Web) with one fictitious (System.Drawing3D).
Common Pitfalls:Confusing a type name (Process) with a namespace, and forgetting nested namespace segments like Drawing.Drawing2D.
Final Answer:System.Process, System.Drawing2D, System.Drawing3D
Discussion & Comments