AutoCAD Quiz: Hatch Boundary Association
10 questions · exam conditions
0:00
Hatch Boundary AssociationQuestion 1 of 10

A consultant sends a drawing containing a hatch with no visible boundary object. A technician runs HATCHGENERATEBOUNDARY and obtains a closed polyline. The technician then grip-edits the new polyline, but the hatch does not change.

Which explanation best accounts for this behavior?

The generated polyline is nonassociative, so a separate association step is required before its edits control the hatch.
Grip edits cannot update associative hatches; only dimensional constraints can change a hatch boundary.
Generated boundaries control hatches only after both objects are moved to the same drawing layer.
The hatch needs a second generated polyline because one closed boundary cannot support associativity.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Hatch Boundary Association

Practice Hatch Boundary Association 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 Hatch Boundary Association, 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

A consultant sends a drawing containing a hatch with no visible boundary object. A technician runs HATCHGENERATEBOUNDARY and obtains a closed polyline. The technician then grip-edits the new polyline, but the hatch does not change.

Which explanation best accounts for this behavior?

  1. The generated polyline is nonassociative, so a separate association step is required before its edits control the hatch. (correct answer)
  2. Grip edits cannot update associative hatches; only dimensional constraints can change a hatch boundary.
  3. Generated boundaries control hatches only after both objects are moved to the same drawing layer.
  4. The hatch needs a second generated polyline because one closed boundary cannot support associativity.
Explanation: When working with hatches in AutoCAD, the key concept to understand is associativity — the live link between a hatch pattern and its boundary objects. A hatch can exist in two states: associative (it updates when its boundary changes) or nonassociative (it is independent of any boundary geometry). The HATCHGENERATEBOUNDARY command reconstructs a polyline around an existing hatch, but here's the critical detail: that newly created polyline is nonassociative by default. AutoCAD does not automatically re-link the hatch to this new boundary object. So when the technician grip-edits the polyline, the hatch has no awareness of those edits — it simply sits unchanged. Answer A correctly identifies this: the generated polyline and the hatch are two independent objects until an explicit association is established (typically by re-editing the hatch and selecting the new boundary). Answer B is wrong because grip editing can absolutely update associative hatches — that is precisely what associativity enables. Dimensional constraints are not required for hatch boundary edits. Answer C invents a layer-matching requirement that does not exist in AutoCAD; associativity has nothing to do with layer assignments. Answer D is wrong because a single closed polyline is perfectly capable of defining a hatch boundary — there is no rule requiring multiple boundaries for associativity to function. As a study tip, remember this pattern: generation ≠ association. Any time AutoCAD creates a derived object (like a generated boundary), assume it starts life as a "dumb" copy unless the documentation explicitly states otherwise. This mindset will help you on several hatch- and reference-related questions.

Question 2

A hatch boundary must be reconstructed. The drafter expects to adjust individual corners later with grips and wants the hatch to update after those edits.

When using Recreate Boundary, which choices best support that requirement?

  1. Create a region and decline association, because regions automatically expose individual vertex grips for editing.
  2. Create a polyline and accept association, because the polyline supports vertex-level grip editing and will control the hatch. (correct answer)
  3. Create a region and accept association, because only regions provide a valid associative boundary for hatches.
  4. Create a polyline and decline association, because matching extents make the hatch-boundary relationship automatic.
Explanation: When working with Recreate Boundary in AutoCAD, you need to think about two independent decisions: what type of boundary object to create, and whether to maintain associativity between that boundary and the hatch. Understanding how these choices interact is the key to this question. The scenario requires two things: grip-editing individual corners, and having the hatch update automatically afterward. A polyline is the right boundary type because it exposes individual vertex grips — you can click a corner and drag it precisely. Crucially, if you accept association, AutoCAD links the hatch to that polyline, so whenever you modify the polyline's shape, the hatch pattern redraws to match. That combination makes B the correct answer. Choice A fails on both counts. Regions do not expose individual vertex grips — they behave as monolithic solids, so you cannot drag a single corner with grips. Declining association also breaks the automatic update requirement entirely. Choice C correctly identifies that association should be accepted, but the claim that "only regions provide a valid associative boundary" is false. Polylines work perfectly well as associative hatch boundaries and are actually the more practical choice for vertex-level editing. Choice D selects the right boundary type (polyline) but declines association. Without association, editing the polyline does nothing to the hatch — you would have to manually re-hatch the area every time you adjust a corner. The idea that "matching extents make the relationship automatic" is simply not how AutoCAD works. A useful rule of thumb: whenever a question mentions grip-editing corners and automatic hatch updates together, think polyline + association — those two features were designed to work in exactly that pairing.

Question 3

An existing hatch must be reshaped to match a newly drawn closed polyline. The new polyline differs from the hatch's current outline, so recreating a boundary from the current hatch would produce the wrong shape.

Which hatch-editing approach should be used?

  1. Edit the existing hatch to select the new polyline as its controlling boundary, replacing the old outline with the desired shape. (correct answer)
  2. Recreate the boundary from the existing hatch, then manually move the resulting vertices to match the new polyline.
  3. Generate a boundary from the existing hatch, then use MATCHPROP to copy the association from the new polyline to it.
  4. Set the hatch and new polyline to the same layer and color, then run REGEN so AutoCAD recognizes their shared outline.
Explanation: When editing hatches in AutoCAD, the core concept to understand is hatch associativity — the link between a hatch pattern and the boundary that defines its shape. Questions like this are really asking whether you know how to reassign or manipulate that controlling boundary. The right move here is A: use the Hatch Editor (double-click the hatch to open it) and select the new polyline as the boundary. AutoCAD allows you to remove the old boundary and add the new closed polyline, so the hatch reshapes itself to match the new outline. This is the direct, intended workflow — no workarounds needed. B is a trap for students who know that AutoCAD can generate a boundary from a hatch (via the "Recreate Boundary" option), but the passage explicitly states that the existing hatch's shape is wrong. Recreating from it just gives you the same incorrect shape, and manually nudging vertices is both tedious and imprecise — not a professional solution. C misunderstands what MATCHPROP does. MATCHPROP copies properties like color, linetype, and hatch pattern settings between objects — it does not transfer boundary associations. You cannot use it to reassign which polyline controls a hatch. D reflects a fundamental misconception. Layer and color have no effect on hatch boundary recognition, and REGEN simply refreshes the display — it does not create logical geometric associations between objects. The study tip: whenever a question involves reshaping an existing hatch, think "Hatch Editor → modify the boundary," not "recreate or regenerate." Hatch associativity is controlled through editing, not display commands or property tools.

Question 4

Two separate hatches share one closed polyline as their visible outer edge. Hatch 1 is associative with the polyline, while Hatch 2 was created as nonassociative. The polyline is stretched while remaining closed.

What is the expected result?

  1. Both hatches update because sharing a geometric edge is sufficient to establish associativity.
  2. Neither hatch updates because one boundary object cannot control more than one displayed hatch.
  3. Hatch 1 updates, while Hatch 2 retains its previous outline until it is separately associated or edited. (correct answer)
  4. Hatch 2 updates, while Hatch 1 becomes nonassociative because the boundary was stretched rather than moved.
Explanation: When you see a question about hatch behavior in AutoCAD, focus on one core concept: associativity is a per-object property, not a property of the boundary geometry itself. A hatch is either linked to its boundary or it isn't — and that status is determined at the moment of creation, not by what other objects share that boundary. Hatch 1 was created as associative, meaning AutoCAD maintains an internal link between that hatch and the polyline. When the polyline is stretched and remains closed, AutoCAD automatically recalculates Hatch 1's fill region to match the updated boundary — this is exactly what associativity is designed to do. Hatch 2, however, was created as nonassociative, so no such link exists. It retains its original shape regardless of what happens to the polyline, until you manually re-associate or recreate it. This makes C the correct answer. A is wrong because sharing a geometric edge creates no associativity. Associativity is established during hatch creation (or explicitly set afterward), not by proximity or shared boundaries. B is wrong because it invents a fictional rule — AutoCAD places no limit on how many associative hatches can reference a single boundary object. D reverses the logic entirely: stretching a closed polyline does not break an existing associative link, and it certainly doesn't transfer associativity from one hatch to another. As a study tip, remember that in AutoCAD, associativity must be explicitly established — it's never inherited, assumed, or transferred. On exam questions, treat each hatch object independently and ask: "Was this specific hatch created with associativity enabled?"

Question 5

A nonassociative floor hatch currently contains an unhatched equipment opening. Replacement geometry has been drawn as one closed outer polyline and one closed inner polyline. The existing hatch must adopt both replacement loops and preserve the opening.

Which selection strategy is most appropriate when redefining the hatch boundary?

  1. Select only the outer polyline; AutoCAD will infer every inner loop from nearby closed geometry afterward.
  2. Select only the inner polyline; the hatch's previous outer edge will remain associated automatically.
  3. Select both replacement polylines so the outer loop and the opening participate in the new boundary definition. (correct answer)
  4. Select the hatch itself twice so AutoCAD recreates separate outer and inner associative boundary loops.
Explanation: When redefining a hatch boundary in AutoCAD, think carefully about what information the HATCH or HATCHEDIT command actually needs: it requires every loop — outer and inner — to be explicitly supplied. AutoCAD does not infer, inherit, or guess missing boundary components on your behalf, especially for a nonassociative hatch. Because the hatch is nonassociative, there is no live link to surrounding geometry. When you redefine its boundary, you must manually select both the outer polyline (which defines where hatching starts) and the inner polyline (which defines the opening where hatching stops). Selecting both tells AutoCAD to treat the outer loop as the fill region and the inner loop as a void, preserving the equipment opening exactly as intended. C is correct because it is the only choice that supplies the complete boundary definition. Choice A is wrong because AutoCAD will not scan nearby closed geometry to automatically detect inner loops — that kind of spatial inference does not exist in the HATCHEDIT workflow. You must select islands explicitly. Choice B fails for the opposite reason: the hatch's previous outer edge is not remembered or reattached automatically, particularly in a nonassociative hatch; omitting the outer polyline would leave the boundary undefined. Choice D misunderstands how HATCHEDIT works entirely — selecting the hatch object itself (even twice) does not trigger a boundary-recreation routine or generate separate associative loops. A useful rule of thumb: whenever a hatch contains islands (openings inside the fill area), count your loops before confirming. You need one selection per boundary loop — outer and inner alike — and AutoCAD will not fill in the gaps.

Question 6

An associative hatch remains in a drawing, but its original rectangular boundary was accidentally erased. The hatch still displays with its previous rectangular extents. The drafter wants a new editable boundary that follows those extents and controls future hatch updates.

Which workflow most directly restores the required relationship?

  1. Use HATCHEDIT, choose Recreate Boundary, create a polyline, and associate the hatch with the new object. (correct answer)
  2. Use HATCHGENERATEBOUNDARY to create a closed polyline, relying on its default settings to establish associativity automatically.
  3. Trace the hatch outline with PLINE, close the polyline, and place both objects on the same layer to link them.
  4. Set HPASSOC to 1, regenerate the drawing, and retain the existing hatch without any further boundary editing.
Explanation: When a hatch loses its associative boundary in AutoCAD, your goal is to restore a true geometric relationship — not just visually approximate the boundary. This question tests your knowledge of the HATCHEDIT command's "Recreate Boundary" function, which is specifically designed for exactly this scenario. The correct workflow is A. Inside HATCHEDIT, the Recreate Boundary option reads the hatch's stored extents and generates a new polyline (or region) that precisely matches them. Critically, it then prompts you to re-associate the hatch with that new object, restoring the live, editable relationship you need. This is AutoCAD's dedicated tool for recovering a lost hatch boundary. Option B is tempting because HATCHGENERATEBOUNDARY does create a closed polyline from the hatch's extents — but it does not automatically establish associativity. The resulting polyline is geometrically accurate but functionally disconnected from the hatch, so future edits to that polyline won't update the hatch pattern. Option C represents a manual workaround that will never create true associativity. Placing objects on the same layer has no effect on hatch association — layer matching is a display/organization setting, not a linking mechanism. Option D misunderstands what HPASSOC does. Setting it to 1 enables associativity for new hatches created going forward; it cannot retroactively reattach an existing hatch to a missing boundary. Regenerating the drawing won't help either. Study tip: Remember that HATCHEDIT → Recreate Boundary is the one built-in command that both generates the boundary and reassociates the hatch in a single workflow — keep that pairing in mind for any exam scenario involving lost hatch boundaries.

Question 7

Two closed polylines occupy exactly the same location. A hatch is explicitly associated with the first polyline. The second polyline is then grip-edited while the first remains unchanged.

How should the hatch respond?

  1. It should follow the edited second polyline because AutoCAD associates hatches with coincident locations.
  2. It should become nonassociative because moving either duplicate invalidates both boundary objects automatically.
  3. It should split between both outlines because coincident closed polylines are treated as separate hatch islands.
  4. It should remain unchanged because associativity refers to the selected boundary object, not any coincident object. (correct answer)
Explanation: When you see a question about hatch associativity in AutoCAD, the key is understanding what associativity actually tracks: a direct link between a hatch object and the specific boundary object you selected when creating it — nothing more. When you create an associative hatch, AutoCAD records a reference to that exact boundary object. If that object is modified — stretched, scaled, reshaped — the hatch updates to match it. This is why D is correct: the hatch was explicitly associated with the first polyline. The second polyline happens to sit in the same location, but the hatch has no knowledge of it whatsoever. Grip-editing the second polyline changes an object the hatch was never linked to, so the hatch stays exactly where it is, still conforming to the unmodified first polyline. A is wrong because AutoCAD does not track spatial coincidence — it tracks object identity. Two objects sharing a location are still two distinct database entries, and associativity does not transfer based on overlap or position. B is wrong because moving one coincident object does not invalidate the boundary of the other; each polyline is independent, and the hatch's associativity to the first polyline remains fully intact. C is wrong because coincident polylines are not automatically interpreted as hatch islands — island behavior depends on hatch style settings and how boundaries are nested, not on accidental overlap. A useful rule of thumb: in AutoCAD, associativity is always object-specific, not location-specific. When exam questions introduce a "nearby" or "coincident" object as a distractor, ask yourself whether the hatch was actually linked to that object — if not, it cannot influence the hatch.

Question 8

A user explodes an associative hatch, producing separate line objects that represent the hatch pattern. The original boundary polyline remains. The user then tries to use HATCHEDIT to associate the pattern lines with that polyline again.

Why will this workflow not restore the original associative hatch?

  1. Exploding preserves the hatch object but clears its scale factor, so only the pattern scale must be reassigned in HATCHEDIT.
  2. Exploding locks the pattern lines to their current layer, so they must be moved to an unlocked boundary layer first.
  3. Exploding converts the original boundary polyline into a region, which must be changed back before HATCHEDIT can be used.
  4. Exploding removes the hatch object, so the resulting lines must be replaced by a newly created hatch to restore associativity. (correct answer)
Explanation: When working with hatches in AutoCAD, it helps to understand what a hatch object actually is. A hatch is a single, unified object that contains its boundary definition, pattern data, and associativity information all bundled together. Associativity means the hatch is linked to its boundary so that editing the boundary automatically updates the hatch. This object-level structure is what makes HATCHEDIT work — it edits an existing hatch object's properties. When you explode a hatch, you don't strip properties from a surviving hatch object — you destroy the hatch object entirely. What remains are simple line segments that approximate the pattern visually. These lines have no memory of being a hatch, no boundary linkage, and no associativity. HATCHEDIT requires a hatch object to function; it cannot adopt orphaned lines and retroactively turn them into one. The only way to restore the associative hatch is to delete those lines and draw a brand-new hatch over the original boundary polyline. That makes D the correct answer. Choice A is wrong because exploding doesn't "preserve" any hatch object at all — there's nothing left to reassign a scale to. Choice B invents a layer-locking behavior that doesn't exist; exploded lines carry no special layer restrictions tied to their hatch origin. Choice C is incorrect because exploding a hatch has no effect whatsoever on the boundary polyline — it remains a polyline, not a region. As a study tip, remember this rule: exploding is always destructive and irreversible in terms of object type. Whenever a question describes an explode operation, check whether the original object type still exists — in most cases, it doesn't.

Question 9

A drawing contains several older nonassociative hatches. Before adding more hatches, a user changes HPASSOC from 0 to 1. The user then expects the older hatches to follow their surrounding polylines automatically.

What is the expected result, and what additional action is needed for an older hatch?

  1. All hatches become associative after REGEN, so no boundary-editing action is required.
  2. Only future hatches default to associative; an older hatch must be explicitly associated with boundary geometry. (correct answer)
  3. Only older hatches become associative; future hatches retain the setting used by their source polylines.
  4. No hatch can be associative until every surrounding polyline is converted into a region.
Explanation: When you see a question about hatch associativity in AutoCAD, focus on when a system variable takes effect — does it apply retroactively, or only going forward? The HPASSOC system variable controls whether newly created hatches are associative (1) or nonassociative (0) by default. Think of it like a factory setting: changing it only affects products made after the change, not ones already on the shelf. So when a user switches HPASSOC from 0 to 1, every hatch drawn from that point forward will default to associative — meaning it will update automatically when its boundary is edited. The older, existing hatches, however, were already created without associativity, and flipping the variable does nothing to them. To make an older hatch associative, you must explicitly reassociate it — typically by using the HATCHEDIT command or the Associate option to link it to its boundary geometry manually. This confirms that B is correct. Answer A is wrong because REGEN only regenerates the display; it does not change the associativity property of existing hatches. Answer C has it exactly backwards — older hatches are unaffected, and it's the future hatches that inherit the new setting. Answer D is a fabrication; regions are not a prerequisite for hatch associativity in any version of AutoCAD. As a study tip, watch for questions that test whether a setting change is prospective or retroactive. In AutoCAD, most system variable changes (like HPASSOC, LTSCALE, etc.) affect future operations only — existing objects generally require manual intervention to reflect new settings.

Question 10

A floor hatch contains an unhatched rectangular opening representing a column. Both the original outer boundary and the column boundary were erased, but the hatch still shows the opening correctly.

What should the drafter expect when recreating and associating the hatch boundary?

  1. Only the outer loop is recreated; the opening must always be redrawn and trimmed from the hatch manually.
  2. Boundary loops represented by the hatch, including the opening, can be recreated and associated with the hatch. (correct answer)
  3. Only the opening loop is recreated because AutoCAD treats the outer hatch edge as implicit geometry.
  4. One polyline crosses between both loops so the outer edge and opening become a single self-intersecting boundary.
Explanation: When working with hatches in AutoCAD, it helps to understand how the HATCHGENERATEBOUNDARY command works. This tool doesn't just redraw a single outline — it reconstructs all boundary loops that define the hatch, including any interior loops (called "island" boundaries) that create openings or voids within the hatch pattern. In this scenario, a hatch has two loops: the outer rectangular boundary and the inner rectangular column opening. Both were deleted, yet the hatch pattern — including the void — remains intact. That's possible because AutoCAD stores the hatch definition independently from the boundary geometry. When you use HATCHGENERATEBOUNDARY, AutoCAD traces the hatch's existing pattern to recreate every loop and associates them with the hatch object. That makes B the correct answer: both the outer boundary and the column opening loop are recreated and associated. A is wrong because it assumes only the outer loop can be regenerated. AutoCAD doesn't limit boundary recreation to a single loop — it rebuilds all loops the hatch already "knows about." C reverses the logic incorrectly; there's no concept of an "implicit outer edge" in AutoCAD — the outer boundary is just as recoverable as any island. D describes a self-intersecting polyline, which is a different (and problematic) boundary type entirely — HATCHGENERATEBOUNDARY creates separate, clean polylines for each loop, not one tangled path. As a study tip: remember that HATCHGENERATEBOUNDARY is a complete reconstruction tool — think of it as AutoCAD reading its own hatch pattern and re-outlining everything it sees, islands included.