- Which statement correctly describes the objects while they are isolated?
Answer: Both remain visible, but the locked-layer object retains its editing restrictions.
When working with ISOLATEOBJECTS in AutoCAD, you need to keep two separate concepts clear in your mind: visibility and editability. These are controlled by different mechanisms, and isolation only affects one of them.
ISOLATEOBJECTS hides all objects that were not selected, making your chosen objects easier to work with. Critically, it does not modify layer properties — it simply suppresses the display of everything outside your selection. This means layer-based restrictions, including locking, remain fully intact. So when both objects are selected and isolation is applied, both stay visible — but the object on the locked layer still cannot be edited, moved, or modified. That's exactly what D describes, making it the correct answer.
A is wrong because ISOLATEOBJECTS has no authority over layer locking. It's a display tool, not a permissions override. Layer locks are set at the layer level and require an explicit unlock to remove.
B introduces a fictional concept — isolated objects do not inherit a "temporary locked state." In fact, the unlocked object remains fully editable during isolation, which directly contradicts this claim.
C describes what would happen if the locked layer were turned off or frozen, not isolated. Since both objects were selected before running ISOLATEOBJECTS, both remain visible. Isolation hides unselected objects, not locked ones.
A useful rule of thumb: think of ISOLATEOBJECTS as putting a spotlight on your selection — it changes what you see, never what you're allowed to do. Layer locking always travels with the object, regardless of visibility state.
- Which setting and workflow provide the required behavior?
Answer: Set OBJECTISOLATIONMODE to 1, hide the markup objects, and save the drawing.
When a question asks about hiding objects that persist across sessions, you need to think about AutoCAD's isolation and visibility memory system — specifically, whether hidden object states are saved with the drawing file or only exist temporarily in the current session.
The key variable here is OBJECTISOLATIONMODE. When set to 1, any objects you hide using the Hide Objects tool have their visibility state saved directly into the drawing file. This means when you save and reopen the drawing, those objects remain hidden — exactly what the scenario requires. Setting OBJECTISOLATIONMODE to 1 and then hiding the markup objects (choice A) is the correct workflow.
Choice B is tempting but flawed: setting OBJECTISOLATIONMODE to 0 means hidden object states are temporary — they only persist for the current session and are not saved with the drawing file. Running REGEN before saving has no effect on visibility persistence; REGEN simply regenerates the display, it doesn't write object visibility to the file.
Choice C introduces LAYLOCKFADECTL, which controls how faded locked layers appear on screen — it has nothing to do with hiding objects or persisting visibility states. Saving the workspace saves your UI layout (toolbars, palettes), not drawing content visibility.
Choice D is a different kind of trap: PICKFIRST controls whether you can select objects before issuing a command (noun-verb selection). It has no relationship to hiding objects. Layer states do save layer visibility, but the scenario involves specific objects, not entire layers.
Your takeaway: memorize the OBJECTISOLATIONMODE values as 0 = temporary and 1 = persistent. Exam questions will often test whether you know which setting actually writes visibility to the drawing file.
- Which action produces the intended result?
Answer: Run UNISOLATEOBJECTS so hidden objects return without undoing subsequent edits.
When working with object visibility in AutoCAD, it's important to understand that HIDEOBJECTS and ISOLATEOBJECTS are visibility-state commands — they don't modify geometry, and crucially, they operate outside the undo history in a meaningful way. Their counterpart, UNISOLATEOBJECTS, restores all hidden objects to visibility without touching anything else in the drawing — no geometry moves, no dimensions disappear. That's exactly what the scenario demands: restoring hidden objects while preserving the subsequent drafting work.
C is correct because UNISOLATEOBJECTS is specifically designed to reverse the hidden state created by HIDEOBJECTS (or ISOLATEOBJECTS), returning those objects to visibility without affecting any edits made before or after the hide operation. It's a targeted visibility toggle, not an undo action.
A is wrong because using UNDO to reverse HIDEOBJECTS would also roll back the object moves and the new dimension — the very changes the drafter wants to keep. You'd then have to redo those changes manually or hope REDO catches them cleanly, which is both risky and inefficient.
B is wrong because REGENALL regenerates the display of all viewports — it resolves visual glitches and updates object appearances, but it has absolutely no ability to restore objects hidden via HIDEOBJECTS. Hidden objects remain hidden after a regen.
D is wrong because layer states control layer properties (on/off, frozen, color, etc.), not the object-level visibility set by HIDEOBJECTS. Restoring a layer state could unintentionally alter layer configurations and still wouldn't un-hide objects hidden through the visibility tool.
Study tip: Remember the pairing — HIDEOBJECTS/ISOLATEOBJECTS are undone by UNISOLATEOBJECTS, not by UNDO or any display command.
- What is the expected display state immediately after object isolation ends?
Answer: All walls return, but furniture remains invisible because its layer is still off.
When working with object isolation in AutoCAD, the key is understanding that ISOLATEOBJECTS and UNISOLATEOBJECTS only control a temporary suppression layer that AutoCAD applies on top of your existing layer settings — they do not permanently alter or override your layer panel configuration.
Here's the logic: when you run ISOLATEOBJECTS on the wall, AutoCAD temporarily hides everything else that was previously visible. The FURNITURE layer was already off before isolation began, so AutoCAD had nothing to temporarily suppress there — furniture was already gone. When you run UNISOLATEOBJECTS, AutoCAD simply restores the temporary suppression, returning all objects that were visible before isolation. Since only the WALL layer was on and thawed at the start, only walls return. The FURNITURE layer remains off because UNISOLATEOBJECTS never touched it. This makes B the correct answer.
A is wrong because it misunderstands what UNISOLATEOBJECTS does — it absolutely does restore previously visible objects; that's its entire purpose. C is the most tempting trap: students assume "unisolate" means "show everything," but it only reverses the temporary suppression, not your layer settings. It has no authority over layers you manually turned off. D is fabricated behavior — there's no mechanism in AutoCAD where unselected objects on a visible layer remain suppressed after unisolation, and reopening the drawing is irrelevant here.
A useful rule of thumb: think of ISOLATEOBJECTS as a "temporary hide" sticky note placed over your drawing. UNISOLATEOBJECTS peels off that sticky note — but whatever was already hidden beneath it stays hidden.
- What happens when object isolation is ended?
Answer: The hidden reference returns showing the revised geometry from the shared block definition.
Whenever you see a question about block references and visibility in AutoCAD, the key concept to keep straight is the difference between an object's visibility state and its connection to the block definition. These are completely independent of each other.
In AutoCAD, all insertions of the same block point to a single shared block definition stored in the drawing database. When you use HIDEOBJECTS (or ISOLATEOBJECTS), you are only suppressing the display of a reference — you are not detaching it, copying it, or breaking its link to the definition. The hidden reference remains a fully active member of the block family; it simply isn't rendered on screen. So when you edit the block definition — changing the swing line in this case — every reference updates automatically, including the hidden one. When you end object isolation with UNISOLATEOBJECTS, that reference reappears showing the current, revised geometry. That makes B the correct answer.
A is wrong because hiding an object never "separates" it from its definition. HIDEOBJECTS is a display toggle, not a data operation. C is wrong because editing a block definition does not delete or invalidate any of its references — all six insertions survive the edit intact. D is wrong because block references never become independent copies through hiding; independence would only happen if you explicitly used EXPLODE or a similar destructive command.
A useful rule of thumb: in AutoCAD, visibility ≠ existence. Anything that only controls what you see on screen — HIDEOBJECTS, layers turned off, freeze — never breaks the underlying data relationships between objects and definitions.
- Which display sequence should result before and after running UNISOLATEOBJECTS?
Answer: Before: A and C; after: A, B, C, and D.
When working with AutoCAD's visibility commands, you need to track two separate layers of hidden state simultaneously — objects hidden by HIDEOBJECTS and objects affected by ISOLATEOBJECTS operate independently.
Here's how the sequence unfolds: Object B is hidden first via HIDEOBJECTS, leaving A, C, and D visible. Then ISOLATEOBJECTS is run on A and C, which hides everything currently visible except the selection — meaning D gets hidden. At this point, only A and C are displayed. This confirms the "before UNISOLATEOBJECTS" state in answer C.
When UNISOLATEOBJECTS runs, it reverses only what ISOLATEOBJECTS did — it restores D to visibility. However, it does not un-hide B, because B was hidden by a separate command (HIDEOBJECTS). AutoCAD tracks these states independently. So after UNISOLATEOBJECTS, you see A, C, and D — but not B. That gives you the "after" state in answer C, making it correct.
Answer A is wrong because it claims B reappears after UNISOLATEOBJECTS, which would require UNISOLATEOBJECTS to undo HIDEOBJECTS — it doesn't. Answer B is wrong because it implies UNISOLATEOBJECTS does nothing, restoring no objects at all. Answer D is wrong on both counts: it misidentifies the "before" state (B is hidden, not visible) and incorrectly brings B back after UNISOLATEOBJECTS.
A useful tip: think of HIDEOBJECTS and ISOLATEOBJECTS as two separate sticky notes tracking hidden objects. UNISOLATEOBJECTS only erases the ISOLATEOBJECTS sticky note — the HIDEOBJECTS list stays intact until you run UNISOLATEOBJECTS' counterpart, UNHIDEOBJECTS.
- What should you do to remove only the two obstructing clouds from view temporarily?
Answer: Select the two clouds, run HIDEOBJECTS, and later end object isolation.
When you need to hide specific objects without affecting other objects on the same layer, AutoCAD's object-level visibility tools are the right category to think about — not layer-level controls.
This is exactly what HIDEOBJECTS (found under the View tab or invoked directly) is designed for. By selecting the two revision clouds and running HIDEOBJECTS, you suppress only those objects while everything else on their layer remains visible. When you're done editing, you end the isolation state using UNISOLATEOBJECTS (or the status bar's object isolation toggle), and the hidden clouds reappear cleanly — no manual cleanup required. Answer D is the correct approach.
Answer A fails because freezing a layer hides everything on that layer across the entire drawing. Since the scenario explicitly states that other revision clouds on the same layer must stay visible, freezing would violate that requirement entirely.
Answer B describes the ISOLATE command, which works inversely — it hides everything except your selection. While restoring layers afterward is possible, it's cumbersome and error-prone. More importantly, isolating the detail objects still doesn't solve the core problem: those two clouds would remain visible unless hidden separately. The workflow is backwards.
Answer C has the same fatal flaw as A — turning off a layer affects all objects on it, not just the two clouds. REGEN simply refreshes the display and has no bearing on which objects are visible.
A useful pattern to remember: whenever a question specifies that some objects on a shared layer must stay visible while others must be hidden, the answer will always involve object-level visibility (HIDEOBJECTS/ISOLATE), never layer-level controls.
- Which workflow best satisfies the requirement?
Answer: Select the three valves, run ISOLATEOBJECTS, and later run UNISOLATEOBJECTS.
When a question asks you to temporarily focus on specific objects without altering layer visibility, think about AutoCAD's object isolation tools — commands designed precisely for this workflow.
ISOLATEOBJECTS (Option B) is the right choice here. You select your three valves first, run the command, and AutoCAD hides everything else at the object level — completely independent of layer settings. When you're done editing, UNISOLATEOBJECTS restores the previous display state exactly as it was. This is the only workflow that satisfies both conditions: temporary focus on selected objects and preserved layer visibility.
Option A is close but subtly wrong. LAYISO isolates by layer, not by individual object selection. If your valves share a layer with other objects, those objects remain visible too. Worse, it modifies layer visibility states — exactly what the question forbids — even though LAYUNISO can restore them afterward.
Option C misuses HIDEOBJECTS, which does suppress specific objects but has no clean "restore" command paired with it. Using REGEN doesn't un-hide objects hidden this way; you'd need UNISOLATEOBJECTS or similar. This reflects a misconception about REGEN's purpose — it redraws the display, it doesn't reverse object suppression.
Option D describes a fully manual layer-management process that directly violates the requirement to leave layer visibility settings unchanged. It's also tedious and error-prone on a complex mechanical plan.
Study tip: Memorize the pairing — ISOLATEOBJECTS / UNISOLATEOBJECTS for object-level isolation, LAYISO / LAYUNISO for layer-level isolation. Exam questions will test whether you know which tool operates at the object level versus the layer level.
- What should the drafter expect after ending object isolation?
Answer: The previously suppressed objects return, and the newly created hatch remains in the drawing.
When working with Object Isolation in AutoCAD, it helps to understand what the feature actually does: it temporarily hides objects from view without deleting or modifying them. Critically, isolation affects visibility only — it has no bearing on your ability to create new geometry while it's active.
When you use End Object Isolation (or End Object Hide), AutoCAD simply restores the display of everything that was hidden. The drawing database itself was never altered — suppressed objects were always present, just not rendered on screen. Any new geometry you created during isolation is a permanent part of the drawing and behaves like any other object. This confirms that A is correct: the suppressed room outlines return to view, and the new hatch persists as a normal drawing element.
B is wrong because it treats isolated mode like a sandbox or temporary workspace — it isn't. AutoCAD doesn't flag objects created during isolation as "temporary." New objects are committed to the drawing immediately upon creation, just like any other time. C is wrong for a related reason: new objects don't "inherit" a suppressed state. Only objects that were explicitly hidden before isolation ended carry that hidden status — and even they are restored when isolation ends. D is wrong because ending object isolation is a global restore action; visibility is not tied to manual layer operations in this workflow, and the hatch would not be uniquely visible while everything else stayed hidden.
A useful rule of thumb: Object Isolation is a display tool, not a session or environment tool. Anything you draw is permanent, regardless of what's currently visible on screen.
- What is the most appropriate next action?
Answer: Run UNISOLATEOBJECTS or choose End Object Isolation to restore suppressed objects.
When objects seem to vanish in AutoCAD despite their layers being on, thawed, and unlocked, your first instinct should be to check whether object isolation is active. Object Isolation (OBJECTISOLATIONMODE) is a display feature that hides individual objects regardless of layer state — and when set to persistent mode, that hidden state survives save-and-reopen cycles. This is exactly the scenario described, and it's a common source of confusion because the missing objects leave no obvious visual clue.
The correct move is D: run UNISOLATEOBJECTS or select End Object Isolation from the right-click menu. This command specifically reverses an active isolation session, restoring all suppressed objects to visibility instantly.
A is a tempting trap — layer states do record layer visibility settings, but they do not capture individually isolated objects. Object isolation operates at the object level, not the layer level, so restoring a layer state won't bring those objects back.
B misreads the situation entirely. Persistent object isolation is a normal, intentional feature — not a symptom of file corruption. Running AUDIT would be appropriate if you suspected damaged records, but nothing in the passage suggests that.
C contains a factual error. REGENALL regenerates the display but does not alter layer lock or freeze states, and isolated objects are not hidden because of layer settings in the first place — so toggling layers accomplishes nothing here.
As a study tip, remember that AutoCAD has two distinct "hiding" systems: layer-level (on/off, freeze/thaw) and object-level (isolate/unisolate). When layer settings check out but objects are still missing, immediately suspect object isolation.
