AutoCAD Quiz: Purge
10 questions · exam conditions
0:00
PurgeQuestion 1 of 10

An unused block definition named DETAIL-BUBBLE contains objects on layer DETAIL-TEMP. No other objects use that layer. A technician runs PURGE with Purge nested items cleared and removes DETAIL-BUBBLE, but DETAIL-TEMP remains in the drawing.

What is the most appropriate next step to remove DETAIL-TEMP?

Run PURGE again and select DETAIL-TEMP now that the block dependency is gone.
Run AUDIT so AutoCAD converts DETAIL-TEMP into an unused layer automatically.
Regenerate the drawing so the block's former layer reference is recalculated and deleted.
Close without saving, reopen the drawing, and purge DETAIL-TEMP before the block.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Purge

Practice Purge in AutoCAD with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Purge, giving you a quick way to practice the rules, question types, and explanations that matter most for AutoCAD.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

An unused block definition named DETAIL-BUBBLE contains objects on layer DETAIL-TEMP. No other objects use that layer. A technician runs PURGE with Purge nested items cleared and removes DETAIL-BUBBLE, but DETAIL-TEMP remains in the drawing.

What is the most appropriate next step to remove DETAIL-TEMP?

  1. Run PURGE again and select DETAIL-TEMP now that the block dependency is gone. (correct answer)
  2. Run AUDIT so AutoCAD converts DETAIL-TEMP into an unused layer automatically.
  3. Regenerate the drawing so the block's former layer reference is recalculated and deleted.
  4. Close without saving, reopen the drawing, and purge DETAIL-TEMP before the block.
Explanation: When working with AutoCAD's PURGE command, it helps to understand that drawing dependencies are hierarchical — objects depend on layers, blocks depend on both, and PURGE resolves these one level at a time unless Purge nested items is enabled. When that option is cleared, AutoCAD only removes items that are currently unreferenced. If a layer is still referenced by a block definition, it cannot be purged yet, even if that block itself is unused. In this scenario, DETAIL-TEMP couldn't be purged initially because DETAIL-BUBBLE held a reference to it — the block owned an object on that layer, keeping the layer "in use." Once DETAIL-BUBBLE is removed, that dependency is broken, and DETAIL-TEMP becomes a true orphan. Running PURGE a second time, as option A suggests, is exactly the right move — the layer is now unreferenced and will appear in the purge list. Option B is wrong because AUDIT checks for structural corruption in the drawing database (broken entities, invalid objects) — it has no mechanism to identify or remove unused layers. Option C is wrong because REGEN refreshes the display and recalculates geometry on screen, but it doesn't affect the drawing database or remove any definitions. Option D is wrong and counterproductive — closing without saving discards the work you just did removing the block, forcing you to repeat the entire process unnecessarily. The study tip here: think of PURGE as a peeling process. Nested dependencies must be unwrapped layer by layer. If something won't purge, ask what still references it — remove that first, then purge again.

Question 2

The BLOCKS category in PURGE does not list ROOM-TAG as purgeable. There are no direct ROOM-TAG insertions in model space or layouts. However, ROOM-TAG is nested inside UNIT-A, and an insertion of UNIT-A remains in the drawing.

Why is ROOM-TAG not available for purging?

  1. A nested block is considered referenced while a placed parent block depends on it. (correct answer)
  2. A block must be inserted directly at least once before PURGE can recognize its definition.
  3. Only block definitions created in the current drawing can be removed with PURGE.
  4. PURGE excludes every block containing attributes, even when all insertions have been erased.
Explanation: When working with AutoCAD's PURGE command, you need to understand how block dependency chains work. PURGE evaluates whether a block definition is currently "in use" — and that check extends beyond direct insertions into the drawing canvas. A block is considered referenced if any currently placed object depends on it, even indirectly. In this scenario, UNIT-A is inserted in the drawing, and UNIT-A's definition contains ROOM-TAG as a nested component. Because UNIT-A relies on ROOM-TAG to display correctly, AutoCAD treats ROOM-TAG as actively referenced. Removing its definition would corrupt UNIT-A's appearance, so PURGE correctly withholds it. This makes A the right answer — a nested block is protected from purging as long as its parent block remains placed. B is wrong because PURGE has no rule requiring a block to have been directly inserted to be recognized. Nested blocks are fully registered in the block definition table regardless of whether you ever placed them independently. C is a misconception — PURGE doesn't distinguish between blocks created in-session versus those imported via xrefs or copy-paste; it only checks whether a definition is currently referenced. D describes a rule that simply doesn't exist in AutoCAD. Attribute-containing blocks are purgeable once all their insertions are removed, just like any other block. A useful pattern to remember: PURGE follows the dependency chain, not just the canvas. If a parent block is inserted, every block nested inside it is implicitly protected. Always purge from the outermost unused block inward when cleaning up complex nested structures.

Question 3

A technician sees no model-space objects on layer ISSUE-CLOUD and assumes it is unused. PURGE reports that the layer cannot be removed. A title-block layout contains one revision cloud on ISSUE-CLOUD.

What must occur before PURGE can remove ISSUE-CLOUD?

  1. The revision cloud must be deleted or moved to another layer in the layout. (correct answer)
  2. The layout must be made current while ISSUE-CLOUD is selected in the PURGE dialog.
  3. The layer must be frozen in every viewport and then selected under purgeable layers.
  4. The revision cloud must be hidden so PURGE no longer detects it as visible geometry.
Explanation: Whenever you see a question about the PURGE command in AutoCAD, remember the core rule: a layer can only be purged if it contains zero objects across the entire drawing — including all layouts and paper space environments, not just model space. This is the key insight the question is testing. The technician checked model space and found nothing on ISSUE-CLOUD, but AutoCAD's drawing database doesn't care where an object lives — if it exists anywhere and references a layer, that layer is considered "in use." The revision cloud sitting in the title-block layout is a real object on ISSUE-CLOUD, which is exactly why PURGE refuses to remove it. The correct path forward, choice A, is to either delete that revision cloud or reassign it to a different layer — only then will ISSUE-CLOUD have no dependents and become purgeable. Choice B is wrong because making a layout current has no effect on what PURGE considers purgeable; the dialog reads from the database, not from what's currently displayed on screen. Choice C confuses freezing with deleting — freezing a layer in viewports hides it visually but leaves all objects intact and still referencing the layer, so PURGE still cannot remove it. Choice D reflects a similar misconception: hiding geometry (through visibility settings or layer off states) does not remove the object from the database, so PURGE will still detect the dependency. As a study tip, always think of PURGE as scanning the entire drawing file, not just your current view or space — if an object touches a layer anywhere, that layer stays.

Question 4

Layer TEMP-ANNO contains no objects and is not referenced by any block definition. It is nevertheless absent from the list of purgeable layers. The layer is currently set as the drawing's current layer.

Which action will make TEMP-ANNO eligible for removal by PURGE?

  1. Turn off TEMP-ANNO, save the drawing, and rerun PURGE without changing layers.
  2. Set another layer current, then rerun PURGE and select TEMP-ANNO. (correct answer)
  3. Lock TEMP-ANNO, regenerate the drawing, and select it under purgeable layers.
  4. Freeze TEMP-ANNO in all viewports, then use Purge All to remove it.
Explanation: When a question asks why a layer can't be purged despite being empty, always think about AutoCAD's one hard rule: the current layer can never be purged. AutoCAD protects it unconditionally, regardless of whether it contains objects, is turned off, locked, or frozen. Because TEMP-ANNO is the current layer, AutoCAD excludes it from the purgeable list no matter what you do to its visibility or state. The only fix is to make a different layer current first. Once another layer holds the "current" designation, TEMP-ANNO loses its protected status, and PURGE can recognize it as an empty, unreferenced layer eligible for removal. That's exactly what B describes — set another layer current, then rerun PURGE. A is wrong because turning a layer off only affects its visibility; it does nothing to change which layer is current. Saving and rerunning PURGE won't help if TEMP-ANNO is still current when you save. C is wrong for a similar reason — locking a layer restricts editing on it but has no effect on the current-layer protection rule. Regenerating the display is a visual refresh, not a database operation. D is wrong because freezing a layer in all viewports also doesn't change its current status. In fact, AutoCAD won't even let you freeze the current layer in the first place, so this option is doubly invalid. Your study tip: whenever you see "why can't this layer be purged," your first instinct should be to check whether it's the current layer — that single condition blocks PURGE more reliably than any other factor.

Question 5

A project drawing contains two unused definitions: the obsolete block TITLE-OLD and the approved linetype FUTURE-PHASE. The linetype is intentionally loaded for work that will be added next week, but the block must be removed now.

Which PURGE approach best meets the project requirement?

  1. Use Purge All because AutoCAD preserves any unused definition that may be needed later.
  2. Select TITLE-OLD individually and leave FUTURE-PHASE unselected during the purge. (correct answer)
  3. Assign FUTURE-PHASE to TITLE-OLD, then purge the block while retaining its linetype dependency.
  4. Purge FUTURE-PHASE first, then purge TITLE-OLD and reload both definitions next week.
Explanation: When working with the PURGE command in AutoCAD, the key concept to understand is selective purging — AutoCAD does not make decisions for you about what to keep. It simply removes what you tell it to remove, and you control exactly which unused definitions get deleted. In this scenario, you have two unused definitions with different statuses: one obsolete (TITLE-OLD) and one intentionally reserved (FUTURE-PHASE). The correct approach, answer B, is to open the Purge dialog, locate TITLE-OLD in the list, select only that definition, and execute the purge while leaving FUTURE-PHASE unchecked. AutoCAD's Purge dialog lets you select items individually, giving you precise control over what gets removed. FUTURE-PHASE stays loaded and ready for next week's work. Answer A is wrong because it assumes AutoCAD automatically protects definitions it "thinks" you'll need — it doesn't. Purge All removes every unused definition without exception, which would delete FUTURE-PHASE along with TITLE-OLD. Answer C describes a technically nonsensical workflow. You cannot assign a linetype to a block definition in a way that creates a protective dependency that prevents purging — this option invents a fictional AutoCAD behavior to mislead you. Answer D is unnecessarily destructive: deliberately purging a definition you plan to use next week, then reloading it, wastes time and risks losing configuration details. There's no reason to remove FUTURE-PHASE at all. The study tip here: on AutoCAD exam questions involving PURGE, always look for the option that gives you manual, item-level control. "Purge All" shortcuts are almost always a trap when any definition needs to be preserved.

Question 6

A cleanup standard calls for removing every unused layer. After all user-created unused layers are purged, Layer 0 remains even though it contains no visible objects and is not current.

What is the correct interpretation of this result?

  1. Layer 0 remains because it must first be renamed before PURGE can identify it as unused.
  2. Layer 0 remains because PURGE removes only layers whose names contain alphabetic characters.
  3. Layer 0 remains because it is a required built-in layer and cannot be purged. (correct answer)
  4. Layer 0 remains because built-in layers can be purged only from an empty paper-space layout.
Explanation: When working with AutoCAD's layer system, it helps to distinguish between user-created layers and built-in layers — because PURGE treats them very differently. AutoCAD ships with Layer 0 as a permanent, protected layer. It exists in every drawing file by design and serves as the default foundation layer. Because it is built into the application, PURGE will never remove it — regardless of whether it contains objects, is current, or has been renamed. This makes C the correct interpretation: Layer 0 survives every purge session simply because it is a required built-in layer that AutoCAD protects from deletion. A is wrong because renaming has no effect on PURGE's behavior toward Layer 0. PURGE evaluates whether a layer is in use, not what it is named — and even an unused Layer 0 cannot be purged regardless of its name. B is a fabricated rule with no basis in AutoCAD; PURGE does not filter layers based on whether their names contain alphabetic characters. D is equally false — there is no mechanism in AutoCAD that allows built-in layers to be purged from a paper-space layout, empty or otherwise. Paper-space context is irrelevant to the purge protection on Layer 0. A useful study tip: AutoCAD has a small set of built-in, non-deletable elements — Layer 0, the Continuous linetype, and the Standard text style are the most commonly tested. Whenever an exam question describes one of these surviving a purge or deletion attempt, the answer almost always comes back to their protected, built-in status.

Question 7

An attached external reference creates layers such as ARCH|WALL and ARCH|DOOR. The xref has been unloaded because it is no longer needed, but the layers are still not available for removal through PURGE.

Which workflow correctly addresses these layer definitions?

  1. Reload the xref, freeze its layers, and then purge the frozen layer definitions.
  2. Bind the xref, erase its visible objects, and purge only the resulting block definition.
  3. Detach the xref, then use PURGE for any remaining unused local definitions. (correct answer)
  4. Rename the xref-dependent layers, unload the xref again, and purge the renamed layers.
Explanation: When working with external references in AutoCAD, understanding the difference between unloading and detaching is essential. Unloading an xref temporarily suppresses it from display and regeneration, but the reference definition — along with all its dependent layers (those pipe-delimited names like ARCH|WALL) — remains registered in the drawing. Because those layer definitions still belong to an active xref record, PURGE cannot remove them; they aren't truly "unused" from AutoCAD's perspective. The correct workflow is C: detaching the xref completely severs its definition from the drawing file. Once detached, AutoCAD removes the xref record, and any dependent layers that were exclusively tied to it become genuinely orphaned and unused. PURGE can then clean them out normally. Choice A fails because freezing xref-dependent layers doesn't break the xref's hold on them — frozen layers still belong to the reference, and PURGE will not touch them. Choice B is a misuse of the Bind command. Binding converts the xref into a permanent block, which actually keeps the objects and layers in the drawing under new names — the opposite of removal. Erasing visible objects afterward still leaves the block definition intact. Choice D is a logical trap: renaming xref-dependent layers doesn't dissolve their dependency. When you reload or even just maintain the xref record, those renamed layers remain tied to it, so PURGE still won't touch them. A helpful rule of thumb: unload = pause, detach = delete. On the AutoCAD exam, any question asking you to permanently remove xref-related definitions requires detaching, not just unloading or freezing.

Question 8

All insertions of the obsolete block CHAIR-OLD have been erased from model space and every layout. No other block contains CHAIR-OLD as a nested block. The name still appears as an available definition when the INSERT command is started.

What should happen after CHAIR-OLD is selected and successfully removed with PURGE?

  1. Its definition is converted to an anonymous block, so it remains insertable under a new name.
  2. Its erased insertions are restored temporarily, allowing the definition to be edited before deletion.
  3. Its definition remains available, but all objects formerly contained in it move to Layer 0.
  4. Its block definition is removed, so CHAIR-OLD no longer appears as an insertable block. (correct answer)
Explanation: When working with blocks in AutoCAD, it helps to understand the difference between a block insertion (an instance placed in the drawing) and a block definition (the stored template in the drawing's database). The PURGE command targets unused definitions — those with zero insertions — and removes them entirely from the database. In this scenario, CHAIR-OLD has no remaining insertions and no nested references, making it a valid purge target. Once PURGE successfully removes it, the definition is gone. You'll confirm D is correct: CHAIR-OLD disappears from the INSERT dialog entirely, as if it were never defined in the file. Each distractor reflects a common misconception worth addressing. A is incorrect because anonymous blocks (those with names beginning with *) are a separate AutoCAD concept used internally for things like hatch patterns and dimensions — purging a named block does not convert it into one. B describes behavior that simply doesn't exist; PURGE is a deletion operation, not a recovery or editing workflow. Erased insertions are not restored at any point. C confuses block purging with what happens when a block is exploded — exploding moves constituent objects to their original layers (not necessarily Layer 0), but purging a definition deletes it outright; no objects are released because there are no active insertions to release. A useful study tip: think of PURGE as a database cleanup tool. It only removes unreferenced definitions, and when it does, they're gone permanently. If CHAIR-OLD reappears after purging, that means a hidden reference still exists — check nested blocks and layouts carefully.

Question 9

A drawing contains an empty, unused layer named REV-NOTE. Its assigned linetype is REV-DASH, which is not assigned to any other layer or object. Both definitions must be removed during one cleanup operation.

Which PURGE configuration best accomplishes the cleanup?

  1. Select REV-DASH first and clear Purge nested items before confirming the purge.
  2. Select REV-NOTE and enable Purge nested items so its unused dependency can also be removed. (correct answer)
  3. Select REV-NOTE and clear Purge nested items so REV-DASH remains assigned during removal.
  4. Select REV-DASH only and enable confirmation so AutoCAD also deletes its referencing layer.
Explanation: When working with AutoCAD's PURGE command, think about dependency chains: a layer can depend on a linetype, meaning if you delete the layer, its assigned linetype may become orphaned — or it may need to be removed simultaneously. The key setting that controls this behavior is Purge nested items, which tells AutoCAD to recursively remove unused definitions that become unreferenced after the primary purge. In this scenario, REV-NOTE is the layer you want to remove, and REV-DASH is the linetype assigned exclusively to it. Since REV-DASH has no other references, deleting REV-NOTE makes REV-DASH immediately unused — a perfect candidate for nested purging. Answer B is correct because selecting REV-NOTE and enabling Purge nested items instructs AutoCAD to delete the layer and then automatically clean up REV-DASH in the same operation, accomplishing both goals in one step. Answer A fails because selecting REV-DASH first is backwards logic — you cannot purge REV-DASH while REV-NOTE still references it; AutoCAD will block the operation since the linetype is still in use. Answer C is a trap: clearing Purge nested items means REV-DASH survives the purge, leaving an orphaned linetype definition behind and failing the stated goal. Answer D is fundamentally wrong because PURGE does not cascade upward — deleting a linetype does not trigger deletion of layers that reference it; the dependency relationship only flows downward. Your study tip: remember that Purge nested items works top-down — select the parent object (the layer), and AutoCAD cleans up its now-unused dependencies beneath it, not the other way around.

Question 10

A custom linetype named SITE-FENCE was loaded into a drawing from the company file Office.lin. SITE-FENCE is no longer assigned to any layer or object, so it is removed using PURGE. The company may need the linetype again in a future project.

Which statement correctly describes the effect of this purge?

  1. SITE-FENCE is removed from Office.lin but retained as a hidden definition in the drawing.
  2. SITE-FENCE is deleted from both the drawing and Office.lin, so it must be recreated.
  3. SITE-FENCE remains in the drawing but is marked unavailable until Office.lin is reopened.
  4. SITE-FENCE is removed from the drawing, but it can later be reloaded from Office.lin. (correct answer)
Explanation: When working with linetypes in AutoCAD, it helps to think of two completely separate containers: the drawing file (.dwg) and the linetype definition file (.lin). Loading a linetype copies its definition into the drawing — the .lin file is simply the source library, not an ongoing dependency. When you purge an unused linetype, AutoCAD removes only the definition stored inside the drawing. The original .lin file sits untouched on your company's file system, exactly as it was before. This is why D is correct — SITE-FENCE disappears from the current drawing, but since Office.lin still holds its definition, any future project can reload it instantly using the LINETYPE command or the Layer Properties Manager. A is wrong because AutoCAD doesn't retain "hidden definitions" after a purge — the definition is genuinely gone from the drawing, not tucked away invisibly. B describes a scenario that would make linetype files nearly useless as shared libraries; PURGE has no mechanism to reach outside the drawing and modify an external file like Office.lin. C misrepresents how AutoCAD handles linetype availability — there is no "marked unavailable" state. A linetype is either defined in the drawing and usable, or it isn't present at all. A helpful pattern to remember: in AutoCAD, PURGE always operates only within the current drawing. It cannot alter blocks, linetypes, or styles stored in external library files. Whenever an exam question involves purging and mentions an external source file, the source file is always safe — only the drawing-side copy is affected.