- What additional action is required to obtain a conventional WCS plan view?
Answer: Run PLAN and choose World because restoring WCS does not itself realign the view
Whenever you see a question mixing UCS and view orientation, remember that AutoCAD treats coordinate system and view direction as two completely independent settings. Changing one does not automatically change the other.
When you run UCS → World, you restore the World Coordinate System as the active UCS — meaning new geometry will be referenced to WCS. However, your viewport's camera direction remains exactly where it was: perpendicular to the old, tilted UCS plane. The screen still shows a skewed, non-plan view of the world. To get a true plan view aligned to WCS (looking straight down the WCS Z-axis), you must explicitly run PLAN and choose World. That command reorients the view so it looks straight down onto the WCS XY plane. This confirms that B is correct.
Choice A is wrong on two counts: UCS → World does change the active coordinate system fully (not just the displayed axes), and running UCS → Previous would simply undo the World restoration — the opposite of what you want. Choice C incorrectly claims PLAN cannot handle 3D views; PLAN works in any context and is precisely the tool for resetting view orientation. ALIGN is for repositioning geometry, not adjusting the view angle. Choice D is a nonsense distractor — MOVE with zero displacement does nothing meaningful to the view or the UCS.
A useful rule of thumb: UCS controls where you draw; PLAN controls where you look. Also note that UCSFOLLOW = 1 would automate this by triggering a plan view whenever the UCS changes — knowing that setting helps you reason through questions like this one.
- What should occur as the user activates each viewport?
Answer: Each viewport restores its saved UCS while the model objects retain the same WCS locations
Whenever you see a question involving UCSVP and floating viewports, focus on what that variable actually controls: whether each viewport independently remembers its own UCS. When UCSVP is set to 1 in a viewport before you establish a UCS there, AutoCAD saves that UCS with that viewport. Switching to another viewport won't disturb it — each viewport restores its own saved UCS when you reactivate it. This is exactly what option C describes, making it correct. Crucially, this is a display and orientation behavior only — the actual WCS coordinates of every model object never change. The UCS simply changes how AutoCAD presents the coordinate system to you in that viewport.
Option A is wrong because UCSVP = 1 is specifically designed to prevent the "last active UCS everywhere" behavior. When UCSVP is 0, viewports share a global UCS — that's the scenario A describes, not what happens here.
Option B describes something that doesn't exist in AutoCAD. Objects are always stored in WCS regardless of which UCS is active. No viewport "converts" object coordinate data into UCS-relative storage — the UCS is a working tool for input and display, not a storage format.
Option D confuses UCS with WCS. A viewport cannot create an independent WCS — there is only one WCS per drawing. What UCSVP saves is a UCS, not a new world coordinate system, and the origin is a UCS origin, not a WCS redefinition.
Your study tip: remember the UCSVP toggle as a simple switch — 0 = shared UCS across viewports, 1 = each viewport owns its UCS independently. - Which statement correctly describes the circle in the model?
Answer: It remains in the former UCS XY plane, with its normal parallel to that UCS's Z-axis
When working with coordinate systems in AutoCAD, the key concept to understand is that geometry is permanently stored in WCS coordinates at the moment of creation — the current UCS only affects how you input that geometry, not how it's saved.
When you draw a circle while a custom UCS is active, AutoCAD records that circle's center point and orientation in absolute WCS space. Specifically, the circle's plane is defined by a normal vector (its Z-axis direction) that matches the UCS's Z-axis at creation time. Once the object exists in the model, it is completely independent of whatever coordinate system happens to be current afterward. That's why answer A is correct: the circle remains permanently aligned to the former UCS's XY plane, with its normal parallel to that UCS's Z-axis, even after you restore WCS.
Answer B is a common misconception — restoring WCS is simply changing which coordinate system is active for input purposes. It does not transform, rotate, or move any existing geometry. Answer C confuses circles with screen-aligned objects like certain 2D annotation entities; standard model-space circles are fully three-dimensional planar objects and do not reorient when you orbit the view. Answer D invents a fictitious problem: AutoCAD internally unifies all coordinates into WCS when objects are stored, so there is no "mixed coordinate" conflict that could make a circle nonplanar.
A useful rule of thumb: think of UCS as a drafting overlay for easier input, not a container that owns your geometry. Objects live in WCS permanently from the moment you confirm their creation.
- Which statement correctly describes the point after the new UCS becomes current?
Answer: The point remains at WCS (30,40,0) and has UCS coordinates (20,30,0)
Whenever you see a question about UCS (User Coordinate System) in AutoCAD, the key distinction to internalize is this: changing the UCS never moves existing geometry — it only changes the lens through which you view and enter coordinates.
Think of the UCS as a new ruler laid over your drawing. When you define a UCS with origin (10,10,0) in WCS (with parallel axes), you're simply shifting the reference frame. Any point already in the drawing stays exactly where it is in the real world (WCS). What changes is the reported UCS coordinate of that point, because it's now measured relative to the new origin instead of (0,0,0).
To convert the existing point from WCS to the new UCS coordinates, subtract the new UCS origin from the WCS coordinates:
UCS=(30−10, 40−10, 0−0)=(20,30,0)
That confirms B — the point stays at WCS (30,40,0) and its UCS coordinates become (20,30,0).
A is wrong because it claims the point moves in WCS — defining a UCS never relocates geometry. C incorrectly adds the origin offset instead of subtracting it, giving (40,50,0), which reverses the math. D claims the point moves in WCS to (20,30,0), again confusing a coordinate transformation with actual object displacement.
A reliable tip: on AutoCAD exam questions about UCS, always ask yourself "did the geometry move, or did the coordinate system move?" They are never the same thing. - After this UCS is established, where does the absolute UCS point (5,2,0) lie in WCS?
Answer: (8,15,0), because UCS X follows WCS positive Y and UCS Y follows WCS negative X
When working with a custom UCS in AutoCAD, your job is to figure out the orientation of the new axes in WCS terms, then apply your UCS coordinates as offsets along those axes.
Start by analyzing the three points given. The origin is at WCS (10,10,0). The positive UCS X-axis points toward WCS (10,20,0), meaning UCS X runs in the WCS +Y direction. The positive UCS Y side is toward WCS (0,10,0), meaning UCS Y runs in the WCS −X direction. This is the critical insight — the axes are rotated, not parallel to WCS.
Now apply the UCS point (5,2,0): start at the origin (10,10,0), move 5 units along UCS X (which is WCS +Y), giving (10,15,0), then move 2 units along UCS Y (which is WCS −X), giving (10−2, 15, 0)=(8,15,0). That confirms C is correct.
Choice A assumes UCS X and WCS X are parallel, which ignores the rotated orientation entirely — a common mistake when students skip the axis-direction analysis. Choice B swaps the offset values but keeps the origin-parallel assumption, producing a number that has no geometric basis in the actual transformation. Choice D applies both offsets backward from the origin, which misunderstands how UCS coordinates add to — not subtract from — the origin along their respective axes.
As a study strategy, always determine the WCS direction vector for each UCS axis before doing any coordinate math. Sketch it out if needed — getting the axis orientation wrong will invalidate every calculation that follows. - Which description best explains the coordinate-system behavior?
Answer: A temporary UCS aligns with the wall during input, then the prior floor UCS is restored
When you see a question about coordinate systems in AutoCAD, focus on the distinction between permanent UCS changes and temporary, command-scoped behavior — that's exactly what this question is testing.
Dynamic UCS (DUCS) is designed to be non-destructive to your current coordinate system setup. When you hover over a planar face during an active drawing command, AutoCAD automatically detects that face's orientation and creates a temporary UCS aligned to it, allowing you to pick points accurately on that surface. Crucially, this alignment only exists for the duration of that input sequence. The moment the command ends, AutoCAD silently restores whichever UCS was active before — in this case, your named floor UCS. That's exactly what D describes, making it the correct answer.
A is wrong because it confuses the UCS with the WCS. The World Coordinate System is a fixed, absolute reference in AutoCAD — it never rotates or changes under any circumstance. Dynamic UCS has no effect on the WCS whatsoever.
B describes what would happen if you explicitly used the UCS command to redefine the named UCS by selecting a face — a deliberate, permanent action. Dynamic UCS does nothing of the sort; it never modifies saved or named UCS definitions.
C contains a subtle misconception: object snaps locate geometry, but they don't explain why points on an angled wall face are accepted in the correct plane. The active coordinate plane does change — temporarily — which is the entire purpose of Dynamic UCS.
A helpful rule of thumb: any AutoCAD feature with the word "Dynamic" in its name typically implies automatic, temporary behavior scoped to a single operation — not a persistent setting change.
- At a point prompt, the user enters the absolute UCS coordinate (20,10,0). At which WCS coordinate is the point created?
Answer: (90,70,0), because the rotated UCS axes determine the WCS offsets
When working with a custom UCS in AutoCAD, you need to understand that entering absolute UCS coordinates doesn't simply shift values — it transforms them through the UCS orientation. The key is to treat each UCS axis as a direction vector in WCS space, then compute how your UCS input offsets from the WCS origin.
In this problem, the UCS origin sits at WCS (100,50,0). The UCS X-axis points in the WCS +Y direction, and the UCS Y-axis points in the WCS −X direction. When you enter UCS point (20,10,0), you're saying "move 20 units along the UCS X-axis and 10 units along the UCS Y-axis." Translating those into WCS offsets: 20 units along WCS +Y gives (0,+20,0), and 10 units along WCS −X gives (−10,0,0). Adding both offsets to the WCS origin: (100+0−10, 50+20+0, 0)=(90,70,0). That confirms C is correct.
A is wrong because it ignores the axis rotation entirely, naively adding (20,10) directly to the origin as if the UCS were aligned with WCS. B incorrectly reverses both axis directions, which has no basis in the described UCS orientation. D subtracts the raw UCS values from the origin — another made-up rule with no geometric justification.
As a study tip, always sketch the UCS axes as WCS vectors first, then multiply each UCS coordinate component by its corresponding WCS direction — this prevents you from falling for the "just add the numbers" trap that makes A so tempting. - What does restoring the named UCS reliably restore?
Answer: The saved UCS origin and axis directions, without automatically restoring the earlier orbit view
Whenever AutoCAD questions involve named UCS settings, you need to clearly separate two independent concepts: the coordinate system definition (origin and axis directions) and the view or viewport orientation. These are stored and restored separately, and confusing them is exactly what most distractors exploit.
When you save a UCS with a name like ASSEMBLY, AutoCAD records the origin point and the X, Y, Z axis directions at that moment — nothing more. Restoring that named UCS brings those axis directions and origin back precisely, regardless of how the view has been orbited or what the current UCS is. This makes B correct: restoring ASSEMBLY reliably gives you back the saved origin and axis orientation, but the viewport's visual direction — changed by the manual orbit — stays exactly as it was. AutoCAD does not automatically snap the camera back to a previously used view when you restore a UCS.
A is wrong on both counts: object positions are never stored in a UCS (objects don't move when you switch coordinate systems), and the orbit view is not restored either. C flips the truth entirely — it's the view direction that isn't restored, while the coordinate-system origin is reliably restored. D misrepresents what happens when switching between WCS and a named UCS; model coordinates don't change numerically when you switch coordinate systems, but that's a general truth about UCS switching, not a description of what a named UCS restores.
A useful rule of thumb: think of a saved UCS as a bookmark for axes, not for cameras. Views require separate saving with commands like VIEW, while UCS handles coordinate geometry only.
- What is the result of this workflow?
Answer: The view aligns normal to the current UCS XY plane, but existing model geometry is not transformed
When working with coordinate systems and views in AutoCAD, it's essential to distinguish between two independent concepts: where you're looking and where your geometry lives. The PLAN command controls your viewpoint; the UCS controls your working plane. These operate separately.
Running PLAN with the Current UCS option reorients your view so you're looking straight down (normal) onto the current UCS XY plane — in this case, the sloped roof face. This is answer A, the correct choice. Critically, no geometry moves. Your model stays exactly where it was modeled in WCS; AutoCAD simply adjusts the camera angle so the sloped plane appears flat in your viewport. Think of it like tilting your head to look straight at a wall — the wall doesn't move, your perspective does.
Answer B is wrong because PLAN never transforms or repositions geometry. It's purely a display/viewing command. Answer C describes the opposite behavior — resetting to WCS — but PLAN with "Current UCS" selected explicitly aligns to the active UCS, not WCS. If you wanted WCS alignment, you'd choose the World option instead. Answer D confuses a UCS with WCS. A user-defined UCS is always a temporary, local coordinate frame. It cannot overwrite or "become" the WCS, which is fixed and permanent in every AutoCAD drawing.
A reliable study tip: whenever you see PLAN on the exam, ask yourself — "Is this moving geometry or moving the view?" The answer is always the view. Geometry only moves with transform commands like ROTATE3D or MOVE.
- Which entry directly specifies that WCS location?
Answer: *100,200,0, which explicitly interprets the coordinate values relative to WCS regardless of the current UCS
When working with coordinate systems in AutoCAD, the critical distinction is between the World Coordinate System (WCS) — the fixed, absolute reference frame — and the User Coordinate System (UCS) — a custom orientation a drafter defines. Most coordinate entry methods interpret values through whatever UCS is currently active, which becomes a problem when you need to pin a point to a specific WCS location without resetting the UCS first.
The asterisk prefix, *100,200,0, is AutoCAD's dedicated syntax for WCS-absolute entry. Regardless of where the UCS origin sits or how it's rotated, the asterisk tells AutoCAD to interpret the values directly in WCS. That makes D the correct answer and the only entry that guarantees the fixed location (100,200,0) in world space.
The distractors each represent a distinct trap. A (@100,200,0) uses the @ prefix, which signals a relative offset from the last picked point — not an absolute location at all, and still evaluated in the current UCS. B (#100,200,0) is a dynamic input modifier that forces absolute entry when dynamic input is in relative mode, but it still interprets those absolute values within the current UCS, not WCS — so if your UCS is rotated or shifted, you'll land in the wrong place. C (100,200,0) is a plain absolute coordinate, which sounds right intuitively but is evaluated in the active UCS, meaning it only matches WCS when UCS and WCS happen to coincide.
A useful memory rule: *** means "world."** Whenever a question asks how to bypass a custom UCS and target a true WCS coordinate, look for the asterisk prefix.
