All questions
Question 1
A drawing contains an empty custom layer named WORK-TEMP. It is not referenced by blocks or external references, but PURGE will not remove it. WORK-TEMP is currently set as the drawing's current layer.
What is the minimum appropriate correction before attempting PURGE again?
- Unlock WORK-TEMP, make it current again, and then purge it.
- Freeze WORK-TEMP in every viewport, and then purge it.
- Set another valid layer current, and then purge WORK-TEMP. (correct answer)
- Turn WORK-TEMP off, save the drawing, and then reopen it before running PURGE.
Explanation: Whenever AutoCAD's PURGE command refuses to remove a layer, your first instinct should be to ask why — because PURGE has specific rules about what makes a layer "in use." One of those rules is absolute: the current layer can never be purged, regardless of whether it contains any objects, is referenced by blocks, or meets every other condition for removal. AutoCAD always protects the active layer.
That's exactly what's happening with WORK-TEMP. It's empty and unreferenced, so it should be purgeable — but it's set as the current layer, which creates an invisible lock that PURGE respects unconditionally. The fix is straightforward: switch to any other valid layer (like layer 0, which always exists), making that layer current instead. Once WORK-TEMP is no longer active, PURGE can remove it cleanly. That's why C is correct — it addresses the one and only reason PURGE is failing.
Choice A is a trap: unlocking a layer addresses a different restriction (locked layers can't be edited, but they can still be purged if unused). Re-making WORK-TEMP current after unlocking it just recreates the original problem. Choice B is similarly off-track — freezing a layer in viewports is a display/access control, not a condition that affects PURGE eligibility. Choice D suggests a save-and-reopen cycle, which is unnecessary busywork; PURGE doesn't require a file restart to work correctly once the actual blocker is resolved.
As a study tip, memorize the two things PURGE will never remove: layer 0 and whichever layer is currently active. Those are the most common "why won't PURGE work?" scenarios on the AutoCAD exam.
Question 2
A consultant's drawing contains the layers NOTES-OLD and NOTES-FINAL. NOTES-OLD still contains several valid text objects, but office standards require all retained notes to use the properties of NOTES-FINAL. After cleanup, NOTES-OLD must no longer exist.
Which workflow best meets the requirements while preserving the valid text?
- Run PURGE on NOTES-OLD, then recreate any text removed by the purge.
- Merge NOTES-OLD into NOTES-FINAL, using NOTES-FINAL as the target layer. (correct answer)
- Freeze NOTES-OLD, then run PURGE with nested items enabled.
- Merge NOTES-FINAL into NOTES-OLD, then rename the remaining layer.
Explanation: When a question asks you to move objects from one layer to another and eliminate the source layer, think about AutoCAD's Merge Layer tool (LAYMRG command). This tool does two things simultaneously: it reassigns all objects from a source layer onto a target layer (applying the target's properties) and then automatically deletes the source layer. That's the exact two-part requirement here — preserve the text and remove NOTES-OLD.
Option B is correct because merging NOTES-OLD into NOTES-FINAL transfers every valid text object onto NOTES-FINAL, so those objects inherit NOTES-FINAL's color, linetype, and lineweight. Once the merge completes, NOTES-OLD is gone automatically — no extra steps needed.
Option A misunderstands PURGE entirely. PURGE only removes empty, unused layer definitions — it cannot delete a layer that still contains objects. Running it on NOTES-OLD would do nothing while the text remains on it, and any text "removed" by some workaround would be lost, violating the requirement to preserve valid content.
Option C compounds the same misunderstanding. Freezing a layer hides its objects but doesn't empty the layer, so PURGE still won't delete it. Frozen layers with objects are simply invisible, not gone.
Option D has the merge direction backwards. Merging NOTES-FINAL into NOTES-OLD would move all objects onto NOTES-OLD and delete NOTES-FINAL — the wrong layer survives. Renaming NOTES-OLD afterward gives you a layer called NOTES-FINAL that was never the original, and the original NOTES-FINAL is lost.
Remember: the target layer in a merge is the one that survives. Always confirm which layer is the source and which is the destination before executing LAYMRG.
Question 3
The layer TEMP-GRID appears empty because it is both off and frozen. PURGE reports that the layer cannot be purged. The current layer is A-WALL, and TEMP-GRID is not used in any block definition.
What is the most likely reason TEMP-GRID cannot be purged?
- Objects remain on TEMP-GRID even though the layer is not currently visible. (correct answer)
- A frozen layer must be thawed before PURGE can evaluate its usage.
- An off layer is automatically treated as the drawing's current layer.
- PURGE can remove visible layers only when they are also unlocked.
Explanation: When working with AutoCAD's PURGE command, it's important to understand that layer visibility and layer usage are completely separate concepts. PURGE doesn't ask "can I see this layer?" — it asks "does anything reference this layer?" Keeping that distinction clear will help you answer questions like this one.
Even though TEMP-GRID appears empty and is both off and frozen, those visibility states have no bearing on whether objects actually exist on that layer. Objects on an off or frozen layer are simply hidden from view — they remain fully present in the drawing database. Since PURGE detects that at least one object still references TEMP-GRID, it refuses to delete the layer. That makes A the correct answer: the layer cannot be purged because objects still reside on it, regardless of visibility.
Choice B is a common misconception — AutoCAD does not require a layer to be thawed before PURGE can evaluate it. PURGE scans the database directly; the frozen state is irrelevant to that process. Choice C is simply false; turning a layer off never reassigns it as the current layer. The current layer here is explicitly A-WALL, and the off/frozen status of TEMP-GRID changes nothing about that designation. Choice D is also incorrect — PURGE has no rule about layers needing to be visible or unlocked before they can be removed. Its only criterion is whether the layer is unreferenced.
A useful rule of thumb: if PURGE refuses to remove a layer that looks empty, your first move should be to thaw and turn on that layer, then zoom extents — you'll often find hidden objects waiting to be discovered or deleted.
Question 4
Three obsolete layers—ELEC-TEMP, ELEC-REV1, and ELEC-REV2—contain wiring that must be retained. All wiring must end on ELEC-FINAL, and the three obsolete layer definitions must be removed.
When using LAYMRG, which selection plan produces the intended result directly?
- Select ELEC-FINAL as a source, then select the three obsolete layers as targets.
- Select ELEC-FINAL as the target, then use PURGE to transfer the obsolete objects.
- Select all four layers as sources, then accept the current layer as the target.
- Select the three obsolete layers as sources, then select ELEC-FINAL as the target. (correct answer)
Explanation: When using LAYMRG (Layer Merge), the key concept to keep straight is the source-to-target direction: objects on source layers get moved onto the target layer, and then the source layer definitions are automatically deleted. Think of it as "pouring" multiple layers into one.
That logic confirms why D is correct. You select the three obsolete layers—ELEC-TEMP, ELEC-REV1, and ELEC-REV2—as sources, then designate ELEC-FINAL as the target. AutoCAD moves all wiring from those three layers onto ELEC-FINAL and purges the obsolete layer definitions in a single operation. Both requirements from the passage are satisfied directly.
Choice A reverses the source and target roles entirely. Selecting ELEC-FINAL as a source means its objects would be moved to the obsolete layers—the opposite of what you want—and ELEC-FINAL's definition would be the one deleted. Choice B misunderstands LAYMRG entirely; PURGE removes unused definitions but cannot transfer objects between layers. There is no combination of PURGE commands that replicates what LAYMRG does in one step. Choice C would include ELEC-FINAL as a source along with the three obsolete layers, meaning ELEC-FINAL's objects get merged into whatever the "current layer" happens to be—losing the intended destination layer and likely producing an unwanted result.
A reliable memory anchor: in LAYMRG, sources disappear, the target survives. Whenever a question asks you to consolidate layers while keeping one specific layer intact, that surviving layer is always your target, and everything being eliminated are your sources.
Question 5
A drafter finds imported geometry on layer 0 and wants to eliminate layer 0 by merging it into A-ANNO. The geometry must remain in the drawing.
Which response correctly addresses this proposed cleanup?
- Use LAYMRG with layer 0 as the source because only current layers are protected.
- Purge layer 0 after freezing it because frozen standard layers become removable.
- Move the geometry to A-ANNO, but retain layer 0 because it is a protected layer. (correct answer)
- Rename layer 0 to A-ANNO so its objects and definition are consolidated.
Explanation: Whenever you see a question about layer management in AutoCAD, the first thing to lock in is the special status of Layer 0 — it is a protected, built-in layer that cannot be deleted, renamed, or purged, regardless of whether it contains objects or not. This is a foundational rule AutoCAD enforces unconditionally.
The correct answer is C because it accurately reflects both parts of the situation: the geometry can be moved from layer 0 to A-ANNO (preserving it in the drawing as required), but layer 0 itself cannot be eliminated. Even after all objects are moved off of it, layer 0 will remain in the drawing file permanently. The drafter must accept this limitation.
A is wrong because LAYMRG can merge user-created layers together, but layer 0 is explicitly protected from deletion even through this command — AutoCAD will refuse to remove it as a target or source if doing so would eliminate the layer entirely.
B is wrong because freezing a layer does not change its protected status. Layer 0 cannot be purged whether it is frozen, empty, or both. Freezing only controls visibility, not layer existence.
D is wrong because layer 0 cannot be renamed. AutoCAD locks its name permanently. Attempting to rename it will produce an error, so no consolidation through renaming is possible.
Your study tip: memorize the "three nevers" for Layer 0 — it can never be deleted, never be renamed, and never be purged. Any answer choice that implies otherwise is automatically wrong.
Question 6
Layer XREF1|A-WALL appears in the host drawing's layer list. It comes from an attached external reference named XREF1. The project manager wants that layer definition removed from the host drawing without modifying the referenced DWG.
Which action is most likely to accomplish the stated result?
- Unload XREF1 to hide its geometry, and then use PURGE to remove the dependent layer.
- Freeze XREF1|A-WALL in all viewports, and then run PURGE to remove the dependent layer.
- Rename XREF1|A-WALL in the host drawing so it is no longer treated as an xref-dependent layer.
- Detach XREF1, which removes the external-reference definition and its dependent layers from the host drawing. (correct answer)
Explanation: When working with external references in AutoCAD, it helps to understand the relationship between an xref and its dependent objects. Any layer, block, or linetype that belongs to an attached xref is called an xref-dependent object. These objects are "owned" by the xref — they exist in the host drawing only because the xref is attached. You cannot edit or permanently remove them without addressing the xref itself.
Detaching XREF1 (option D) is the correct action. Detaching fully removes the external reference definition from the host drawing — its geometry disappears, and all dependent layers like XREF1|A-WALL are eliminated from the layer list automatically. The referenced DWG file on disk remains completely untouched, which satisfies the project manager's requirement.
Option A is a common trap. Unloading an xref hides its geometry temporarily but keeps the xref definition — and all its dependent layers — registered in the host drawing. PURGE will not remove those layers while the xref is still attached (even in an unloaded state), because AutoCAD considers them in use.
Option B makes a similar mistake. Freezing a layer controls visibility only; it does not sever the ownership relationship between the layer and its xref. PURGE still cannot remove a dependent layer that belongs to an attached reference.
Option C misunderstands xref-dependent naming. The pipe character (|) in the layer name is a protected convention enforced by AutoCAD — you cannot rename an xref-dependent layer in the host drawing at all.
A useful rule of thumb: if a layer is owned by an xref, only detaching that xref will cleanly remove it. Visibility commands (freeze, unload) never affect layer ownership.
Question 7
A drawing has an unused block definition that references an unused linetype, and that linetype is assigned to an otherwise unused layer. A first purge pass removes only the block definition, but the layer remains.
Which explanation and next step best fit this result?
- Dependencies may become purgeable in stages; run PURGE again or enable nested-item purging. (correct answer)
- PURGE never removes layers after blocks; use LAYMRG to move the nonexistent objects.
- The layer became current when the block was purged; freeze it before trying again.
- The linetype permanently protects the layer; rename both items before another purge.
Explanation: When you run PURGE in AutoCAD, it removes unreferenced objects — but only those with no remaining dependencies. This question tests whether you understand that purging is often an iterative process because objects exist in a dependency chain: a block can reference a linetype, which is assigned to a layer. When the block is removed, the linetype it referenced becomes unused. When the linetype is removed, the layer it was assigned to becomes unused. Each stage only becomes purgeable after the previous dependency is cleared.
That's exactly why A is correct. The first PURGE pass successfully removed the block definition, which was the outermost dependency. The linetype and layer weren't purgeable yet on that pass — but now that the block is gone, running PURGE again will remove the linetype, and a third pass (or the "Purge nested items" option) will finally remove the layer. This staged behavior is normal and by design.
B is wrong because LAYMRG merges layers with existing objects — it doesn't help when the issue is simply a dependency-chain purge. C invents a false behavior; purging a block doesn't reassign the current layer. The current layer is entirely unrelated to block deletion. D is wrong because linetypes don't permanently protect layers from purging — once the linetype itself is purged, the layer becomes eligible.
As a study tip, remember that PURGE often needs multiple passes for nested dependencies. AutoCAD also offers a "Purge nested items" checkbox in the dialog that handles this automatically — knowing both the manual and automated approaches will help you on scenario-based exam questions like this one.
Question 8
Layer DETAIL-OLD uses red with a dashed linetype. Layer DETAIL-NEW uses blue with a continuous linetype. On DETAIL-OLD, one line has both color and linetype set to ByLayer, while a second line has an explicit green color and a ByLayer linetype. DETAIL-OLD is merged into DETAIL-NEW.
What property result should be expected after the merge?
- Both lines become blue and continuous because merging removes all object-level overrides.
- The first becomes blue and continuous; the second stays green but becomes continuous. (correct answer)
- The first stays red and dashed; the second stays green and dashed after reassignment.
- The first becomes blue and dashed; the second stays green and continuous.
Explanation: When AutoCAD merges one layer into another, it reassigns all objects from the source layer to the destination layer — but it only changes properties that were set to ByLayer. Object-level overrides (explicit property assignments) survive the merge unchanged.
Here's the logic applied to the passage: The first line on DETAIL-OLD has both color and linetype set to ByLayer, meaning it inherits everything from whichever layer it belongs to. After the merge moves it onto DETAIL-NEW, it now inherits DETAIL-NEW's properties: blue and continuous. The second line has an explicit (object-level) green color but a ByLayer linetype. After the merge, its color stays green because that override is preserved, but its linetype switches to continuous because it was ByLayer and now inherits from DETAIL-NEW. That's exactly what answer B describes, making it correct.
Answer A is wrong because merging does not strip object-level overrides — explicit properties always travel with the object. Answer C incorrectly assumes the objects retain DETAIL-OLD's properties after reassignment; once an object moves to DETAIL-NEW, any ByLayer property pulls from DETAIL-NEW, not the old layer. Answer D gets the first line wrong — since both its properties were ByLayer, it inherits everything from DETAIL-NEW, including the continuous linetype, not the old dashed one.
A useful way to remember this: think of ByLayer as a live link to the current layer. When the layer changes, that link updates automatically. Explicit overrides are hardcoded and ignore the layer entirely. On merge questions, always sort each property by whether it's ByLayer or explicit before predicting the result.
Question 9
No visible object in model space or any layout is assigned to layer SYMBOL-OLD. However, PURGE identifies SYMBOL-OLD as non-purgeable. The drawing contains an unused block definition named VALVE-OLD whose internal geometry is on SYMBOL-OLD.
Which action sequence can remove both unused definitions without deleting placed drawing objects?
- Purge VALVE-OLD first, and then purge SYMBOL-OLD after its reference is removed. (correct answer)
- Purge SYMBOL-OLD first, and then redefine VALVE-OLD on layer 0.
- Turn off SYMBOL-OLD, and then purge VALVE-OLD without checking dependencies.
- Set SYMBOL-OLD current, and then purge the block and layer together.
Explanation: Whenever you encounter a question about purging in AutoCAD, think about dependency chains: AutoCAD will not let you purge a definition if something else still references it. Here, SYMBOL-OLD can't be purged because VALVE-OLD's internal geometry lives on that layer — the layer has a dependent, even though nothing is placed in the drawing.
The correct sequence is A: purge VALVE-OLD first, then purge SYMBOL-OLD. Once VALVE-OLD is removed from the block definition table, nothing references SYMBOL-OLD anymore, and it becomes purgeable. Critically, because VALVE-OLD is an unused block definition (never inserted into model space or any layout), deleting it removes no visible drawing objects.
Here's why the other options fail. B has the order completely backwards — you cannot purge SYMBOL-OLD while VALVE-OLD still references it, so the first step would simply fail. Redefining VALVE-OLD on layer 0 would change the dependency but still leave VALVE-OLD itself in the definition table, requiring an extra purge step anyway. C is a misconception: turning a layer off only hides objects visually — it does nothing to remove the layer from the drawing database or break block dependencies. You still cannot purge a layer that's referenced inside a block definition. D is invalid because AutoCAD's PURGE command doesn't allow you to simultaneously purge a block and its referenced layer in one action; the dependency must be resolved sequentially.
The study tip to carry forward: always purge dependents before dependencies. If a layer, linetype, or style is blocked from purging, ask yourself what still points to it — that item must go first.
Question 10
Before issuing a drawing to a client, a technician must consolidate duplicate layers without losing valid objects and then remove any remaining unused layer definitions. The file contains OLD-DOOR with valid objects, DOOR as the approved target, and several empty temporary layers.
Which ordered workflow is the safest and most efficient?
- Purge all temporary and duplicate layers first, then merge OLD-DOOR into DOOR.
- Merge OLD-DOOR into DOOR, verify the result, and then purge remaining unused layers. (correct answer)
- Freeze OLD-DOOR, purge all layers, and then thaw the surviving door geometry.
- Delete OLD-DOOR from Layer Properties, purge DOOR, and then restore the objects.
Explanation: When managing layers before issuing a drawing, you need to think sequentially: protect valid objects first, then clean up what remains. The critical principle is that you can only safely remove what's empty — never what still holds geometry.
The safest workflow is B because it respects that order. Merging OLD-DOOR into DOOR first moves all valid objects onto the approved layer, effectively eliminating OLD-DOOR as a populated layer. Once you verify the geometry transferred correctly, you can confidently purge — because now OLD-DOOR is empty, and any remaining temporary layers were never populated to begin with. Nothing of value can be accidentally lost.
A fails because purging first risks deleting OLD-DOOR before its objects are relocated. AutoCAD's PURGE command targets unused layer definitions, but if OLD-DOOR is mistakenly considered "unused" or if temporary layers still hold stray objects, you may corrupt the drawing before the merge even happens. Purging before merging inverts the safe sequence.
C is dangerous because freezing a layer doesn't protect it from being purged — frozen layers with no objects can still be purged, and thawing afterward won't restore deleted layer definitions or geometry that was lost in the process.
D is the most destructive option. Deleting a layer from Layer Properties Manager in AutoCAD will either refuse the deletion (if objects exist) or move objects to layer 0 unpredictably. There is no reliable "restore" step afterward.
As a study tip: on AutoCAD workflow questions, always ask "does this step protect existing geometry before removing anything?" — the correct answer will always secure objects before cleanup.