AutoCAD Quiz: Annotative Properties
10 questions · exam conditions
0:00
Annotative PropertiesQuestion 1 of 10

A drawing uses millimeters as model-space units. An annotative text object has a paper text height of 2.5 mm2.5\ \mathrm{mm} and supports annotation scales of 1:501{:}50 and 1:1001{:}100.

Which statement correctly describes the text representations AutoCAD uses?

Both representations are 2.5 mm2.5\ \mathrm{mm} high in model space and are enlarged only during plotting.
The model-space representations are effectively 125 mm125\ \mathrm{mm} and 250 mm250\ \mathrm{mm} high, producing the same paper height.
The model-space representations are effectively 250 mm250\ \mathrm{mm} and 125 mm125\ \mathrm{mm} high, producing different paper heights.
Both representations are 125 mm125\ \mathrm{mm} high in model space because the text object has one stored height.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Annotative Properties

Practice Annotative Properties 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 Annotative Properties, 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 drawing uses millimeters as model-space units. An annotative text object has a paper text height of 2.5 mm2.5\ \mathrm{mm} and supports annotation scales of 1:501{:}50 and 1:1001{:}100.

Which statement correctly describes the text representations AutoCAD uses?

  1. Both representations are 2.5 mm2.5\ \mathrm{mm} high in model space and are enlarged only during plotting.
  2. The model-space representations are effectively 125 mm125\ \mathrm{mm} and 250 mm250\ \mathrm{mm} high, producing the same paper height. (correct answer)
  3. The model-space representations are effectively 250 mm250\ \mathrm{mm} and 125 mm125\ \mathrm{mm} high, producing different paper heights.
  4. Both representations are 125 mm125\ \mathrm{mm} high in model space because the text object has one stored height.
Explanation: Whenever you see a question about annotative objects, the key concept to keep in mind is this: AutoCAD stores a separate model-space representation for each annotation scale, and each representation is sized so that it prints at the correct paper height regardless of viewport zoom. The rule is straightforward: model-space height = paper height × scale factor. For a 2.5 mm2.5\ \mathrm{mm} paper height at 1:501{:}50, the model-space height is 2.5×50=125 mm2.5 \times 50 = 125\ \mathrm{mm}. At 1:1001{:}100, it becomes 2.5×100=250 mm2.5 \times 100 = 250\ \mathrm{mm}. When each viewport applies its respective scale and shrinks the geometry back down to paper size, both representations print at exactly 2.5 mm2.5\ \mathrm{mm}. That makes B correct — two differently-sized model-space representations that converge on the same paper height. A is wrong because it describes non-annotative behavior, where a single object is plotted at whatever size it happens to be. Annotative objects don't work that way — the scaling is baked into the representation, not applied at plot time as a surprise. C contains the right model-space heights but inverts the relationship — it assigns 250 mm250\ \mathrm{mm} to the 1:501{:}50 scale and 125 mm125\ \mathrm{mm} to the 1:1001{:}100 scale, which is backwards. More critically, it claims the paper heights differ, which defeats the entire purpose of the annotative feature. D confuses annotative objects with standard (non-annotative) text, which truly does store only one height. Study tip: Always multiply paper height by the scale denominator to find model-space height — and remember that annotative objects store one representation per scale, not one global height.

Question 2

An annotative dimension appears in a 1:251{:}25 viewport but not in a 1:501{:}50 viewport. Its layer is on and thawed in both viewports. Setting ANNOALLVISIBLE on makes the dimension appear in the 1:501{:}50 viewport.

What is the best permanent correction for normal documentation output?

  1. Leave ANNOALLVISIBLE on so every annotative object appears at every viewport scale.
  2. Add the 1:501{:}50 annotation scale to the dimension, then return ANNOALLVISIBLE to its normal setting. (correct answer)
  3. Convert the dimension to nonannotative and set its overall dimension scale to 5050.
  4. Freeze and thaw the dimension layer in the 1:501{:}50 viewport to regenerate its representation.
Explanation: Whenever you see a question about annotative objects behaving differently across viewports, think about annotation scales. AutoCAD's annotative system works by assigning one or more scales to each annotative object — the object only displays in viewports whose scale matches one of those assigned scales. If your dimension was created with only the 1:251{:}25 scale, it simply has no representation at 1:501{:}50, which is exactly what the passage describes. The correct fix is B: add the 1:501{:}50 annotation scale directly to the dimension, then restore ANNOALLVISIBLE to its default (off). This teaches AutoCAD to generate a properly scaled representation of that dimension for the 1:501{:}50 viewport permanently, without side effects. You can do this by selecting the dimension, opening the Annotation Scale list, and adding the needed scale. A is a workflow trap. Leaving ANNOALLVISIBLE on forces every annotative object to display at every scale regardless of intent — you lose precise control over what appears in each viewport, which defeats the whole purpose of the annotative system in production drawings. C converts the dimension to a nonannotative object and hard-codes a scale factor. This destroys the annotative workflow entirely; the dimension will no longer respond intelligently to viewport scales, creating maintenance headaches as your drawing evolves. D is based on a misconception. Freezing and thawing a layer only forces a visual refresh — it cannot create an annotation scale representation that doesn't already exist. As a study tip: on AutoCAD exam questions, any answer that disables or bypasses the annotative system rather than working within it is almost always wrong. Look for the option that correctly configures the annotative properties.

Question 3

A linear dimension measures a model-space distance of 3000 mm3000\ \mathrm{mm}. It uses an annotative dimension style and has representations for 1:501{:}50 and 1:1001{:}100 viewports.

Assuming no alternate-unit or dimension-factor overrides are applied, what should occur in the two viewports?

  1. The displayed values are 6060 and 3030, while the arrows remain the same paper size.
  2. The displayed values are 30003000 and 15001500, because the larger scale halves the measurement.
  3. Both display 30003000, but the 1:1001{:}100 viewport plots the arrows at twice the paper size.
  4. Both display 30003000, and the text and arrows maintain their specified paper sizes. (correct answer)
Explanation: When working with annotative dimensions in AutoCAD, the key concept to keep in mind is the purpose of the annotative system: it automatically scales text, arrows, and other annotation elements so they appear at a consistent paper size across different viewport scales — while always displaying the true model-space measurement. An annotative dimension style stores a fixed paper-space size for its text height and arrowheads. When you add representations for 1:501{:}50 and 1:1001{:}100, AutoCAD handles the scaling internally. The dimension reads the actual geometry — 3000 mm3000\ \mathrm{mm} — and displays that value in both viewports. Simultaneously, the annotation scale ensures that text and arrows plot at the same physical size on paper regardless of which viewport you're in. That's exactly what D describes, making it correct. A is wrong because it confuses dimension values with scale ratios. Dividing 30003000 by 5050 or 100100 to get 6060 or 3030 would only apply if you had a dimension scale factor override — annotative dimensions don't alter the measured value this way. B makes a similar error, suggesting the displayed number changes with viewport scale. The measurement reflects true model geometry, not a scaled version of it; 15001500 would only appear if the actual distance were 1500 mm1500\ \mathrm{mm}. C gets the dimension value right but reverses the arrow behavior. The entire point of annotative scaling is that arrows and text do not change paper size between viewports — AutoCAD compensates automatically. As a study tip, remember the annotative system's core promise: one true value, consistent paper appearance. Any answer suggesting the displayed number changes with scale, or that annotation sizes vary between viewports, is almost certainly a trap.

Question 4

A designer grip-edits the position of an annotative note while working at 1:1001{:}100. The note's 1:501{:}50 and 1:201{:}20 representations remain at older locations. The designer decides that all representations should again use the current 1:1001{:}100 representation's location.

Which command is intended for this correction?

  1. Use REGENALL to force every representation to adopt the current location.
  2. Use OBJECTSCALE to remove and then recreate every scale assigned to the note.
  3. Use MATCHPROP to copy the note's properties onto each scale representation.
  4. Use ANNORESET on the note while 1:1001{:}100 is the current annotation scale. (correct answer)
Explanation: When working with annotative objects in AutoCAD, each assigned scale can have its own independently stored position. This happens the moment you grip-edit an object while one particular scale is current — only that scale's representation moves, leaving others behind. The question is testing whether you know which command exists specifically to resynchronize those drifted representations back to a single "master" location. That command is ANNORESET, making D correct. When you run ANNORESET on an annotative object, AutoCAD takes whatever position the current annotation scale's representation occupies and resets all other scale representations to match it exactly. Since the designer is already working at 1:1001{:}100 and that representation is in the right place, running ANNORESET while 1:1001{:}100 is active solves the problem in one step. Choice A is wrong because REGENALL simply regenerates the display of all viewports — it recalculates geometry visually but has no mechanism to relocate annotative representations. Choice B misunderstands OBJECTSCALE, which adds or removes scale entries from an object's annotation scale list. Deleting and re-adding scales would not reposition them; it would just re-register them at their existing (or default) locations and adds unnecessary rework. Choice C is a tempting trap — MATCHPROP copies properties like layer, color, and text style between objects, but it does not transfer the positional data of annotative representations from one scale to another. A good study tip: whenever you see a question about annotative objects behaving differently across scales, think about representation independence — ANNORESET is the dedicated fix for positional drift, and it always defers to the current scale as the authority.

Question 5

Several eligible annotative notes currently support only 1:501{:}50. A user plans to change the current annotation scale to 1:1001{:}100 and wants AutoCAD to add the new scale automatically to the existing notes rather than editing each note with OBJECTSCALE.

Which setup is required before changing the current annotation scale?

  1. Set the global linetype scale to 100100, then use REGENALL to apply it to all annotative notes.
  2. Set ANNOALLVISIBLE on, then select 1:1001{:}100 as the current annotation scale in the status bar.
  3. Enable automatic annotation-scale addition through ANNOAUTOSCALE, then select 1:1001{:}100 as the current annotation scale. (correct answer)
  4. Enable annotative visibility in the text style dialog, then update each note's paper text height to match.
Explanation: Whenever you see a question about annotative objects and scale management in AutoCAD, focus on the system variable that controls automatic scale behavior — that's the key distinction this question is testing. AutoCAD's ANNOAUTOSCALE system variable is specifically designed to add the current annotation scale to all eligible annotative objects automatically when you switch scales. By enabling ANNOAUTOSCALE (setting it to a positive value), AutoCAD watches for scale changes and updates supported annotative objects — like your 1:50 notes — without requiring you to manually run OBJECTSCALE on each one. So the correct workflow is exactly what C describes: enable ANNOAUTOSCALE first, then switch the current annotation scale to 1:1001{:}100 in the status bar. AutoCAD handles the rest. A is a trap for students who confuse linetype scale (LTSCALE or PSLTSCALE) with annotation scale. Global linetype scale affects how dash patterns display — it has nothing to do with adding scales to annotative objects. REGENALL simply regenerates the display and won't update annotative scale lists. B describes ANNOALLVISIBLE, which controls whether annotative objects without the current scale assigned are still shown (as faded). It's a visibility toggle, not an automatic-addition tool. Turning it on won't add 1:1001{:}100 to your notes' scale list. D is a distractor mixing up text style settings with annotative scale management. Paper text height is defined per style, and editing it won't propagate scale support to existing objects automatically. As a study tip, remember the pairing: ANNOAUTOSCALE = automatic scale addition, ANNOALLVISIBLE = visibility of unrepresented scales. Exam questions often swap these two, so know exactly what each one does.

Question 6

An annotative room label is used in a viewport whose view has been rotated to fit a sheet. The room geometry should remain rotated in the viewport, but the label text should read horizontally relative to the layout sheet.

Which object setting most directly controls this behavior?

  1. Enable Match text orientation to layout for the annotative text object or style. (correct answer)
  2. Enable Upside down in the text style and rotate the viewport back afterward.
  3. Set ANNOALLVISIBLE on so the unrotated text representation becomes visible.
  4. Disable annotative behavior and apply a fixed model-space rotation to the label.
Explanation: When working with annotative objects in rotated viewports, the core concept being tested is how AutoCAD handles the orientation of annotation relative to the layout sheet versus the model geometry. Annotative scaling solves the size problem, but orientation is a separate concern — and that's exactly what this question targets. The setting described in A — "Match text orientation to layout" — is built precisely for this scenario. When enabled on an annotative text object or style, AutoCAD automatically keeps the text reading horizontally on the layout sheet regardless of how the viewport has been rotated. The geometry inside the viewport stays at its rotated angle, but the annotation reorients itself to remain legible. This is the most direct, purpose-built solution. B is a workaround that creates more problems than it solves. Enabling "Upside down" is a text style flag designed for mirroring corrections, not viewport rotation compensation. Rotating the viewport back afterward defeats the entire purpose of fitting the geometry to the sheet layout. C misidentifies the role of ANNOALLVISIBLE. That system variable controls whether annotation representations for non-current scales are displayed — it has nothing to do with correcting text orientation in a rotated viewport. D abandons annotative behavior entirely. Applying a fixed model-space rotation means the label won't automatically adapt if the viewport angle or annotation scale ever changes, eliminating the core benefit of using annotative objects in the first place. The study tip here: when you see viewport rotation + annotation behavior in the same question, your first instinct should be to look for orientation-matching settings rather than workarounds involving manual rotation or style flags.

Question 7

New multileaders will identify equipment in two viewports scaled at 1:251{:}25 and 1:751{:}75. The leader text and arrowheads must plot at consistent sizes, and each equipment callout must remain a single multileader object.

Which workflow best meets these requirements?

  1. Use an annotative multileader style and assign both required annotation scales to each multileader. (correct answer)
  2. Use a nonannotative multileader style and scale each viewport's leader layer independently.
  3. Create one multileader at 1:251{:}25 and a geometrically scaled copy for 1:751{:}75.
  4. Use an annotative text style but keep the multileader style and arrowheads nonannotative.
Explanation: When a drawing must display correctly across multiple viewport scales, AutoCAD's annotative feature is the key concept being tested. Annotative objects store multiple scale representations internally, so they automatically display at the correct plotted size in each viewport — no manual copying or layer manipulation required. Answer A is correct because an annotative multileader style lets you assign both 1:251{:}25 and 1:751{:}75 annotation scales directly to each multileader object. AutoCAD then manages both representations within that single object, keeping leader text and arrowheads at consistent plotted sizes in both viewports. This directly satisfies all three requirements: consistent text/arrowhead size, single object per callout, and correct appearance at both scales. Answer B fails because scaling a layer affects all objects on that layer uniformly — it doesn't intelligently resize text and arrowheads to match a viewport's scale factor. You'd end up with incorrectly proportioned leaders, and the layer-scaling approach isn't even a standard AutoCAD workflow for this purpose. Answer C violates the requirement that each callout remain a single multileader object. Creating a geometrically scaled copy produces two separate objects, doubling your editing workload and making the drawing harder to manage. Answer D is internally inconsistent. Making the text style annotative while leaving the multileader style and arrowheads nonannotative means your arrowheads and leader lines won't scale correctly — only the text would adapt, producing mismatched components. Study tip: On AutoCAD exam questions, whenever you see "consistent plotted size across multiple scales" paired with "single object," that's your signal to immediately think annotative style with multiple assigned scales — that combination is the intended solution.

Question 8

A note is created in model space while the current annotation scale is 1:501{:}50. The note is annotative and appears correctly in a 1:501{:}50 layout viewport. It must also appear at the same plotted text height in a 1:1001{:}100 viewport, but it is currently absent there. Both viewports display the note's layer.

Which action most directly produces the required result without creating a duplicate note?

  1. Use OBJECTSCALE to add the 1:1001{:}100 annotation scale to the existing note. (correct answer)
  2. Change the note's text height to twice its current paper text height.
  3. Set the 1:1001{:}100 viewport's standard scale to match the 1:501{:}50 viewport.
  4. Use SCALE to enlarge the existing note by a factor of two in model space.
Explanation: Whenever you see a question about annotative objects appearing in multiple viewports, the core concept is AutoCAD's annotation scale system — annotative objects only display in viewports whose scale matches one of the scales assigned to that object. When you created the note at a 1:501{:}50 annotation scale, AutoCAD automatically assigned 1:501{:}50 to that note. The 1:1001{:}100 viewport has a different scale, so the note is simply invisible there — not missing, just unrecognized. The fix is to tell the note to also support 1:1001{:}100. The OBJECTSCALE command does exactly this: it adds additional annotation scales to an existing annotative object. AutoCAD then automatically calculates the correct model-space size for the new scale so the plotted text height remains identical across both viewports. This makes A the correct answer — one note, two scales, no duplicates. B is wrong because manually changing the text height breaks the annotative workflow. It alters the object's actual size rather than adding a scale representation, and it won't make the note appear in the 1:1001{:}100 viewport at all. C is wrong because forcing the 1:1001{:}100 viewport to display at 1:501{:}50 defeats the purpose of having two different-scale viewports and changes your drawing's intended presentation. D is wrong because using SCALE enlarges the note's model-space geometry permanently, which distorts how it appears in the 1:501{:}50 viewport and still doesn't add the required annotation scale. For the exam, remember: visibility in a viewport = matching scale assigned to the object. When an annotative object is missing from a viewport, your first tool should be OBJECTSCALE, not geometry edits.

Question 9

A single annotative label supports 1:201{:}20, 1:501{:}50, and 1:1001{:}100. The label should no longer appear in 1:201{:}20 detail viewports, but it must remain available at the other two scales.

Which edit satisfies the requirement while preserving the label as one object?

  1. Delete the label while the current annotation scale is 1:201{:}20.
  2. Turn off the label's layer only in every 1:201{:}20 viewport.
  3. Use OBJECTSCALE to delete only the 1:201{:}20 scale from the label. (correct answer)
  4. Set the label to nonannotative while the current scale is 1:501{:}50.
Explanation: Annotative objects in AutoCAD can support multiple annotation scales simultaneously — think of each scale as a "representation" stored inside the same single object. The key concept here is that you can add or remove individual scales from an annotative object without deleting the object itself or affecting its other scale representations. The OBJECTSCALE command is exactly the tool for this. It opens a dialog listing every scale currently assigned to the selected annotative object, and you can delete any individual scale entry. Removing 1:201{:}20 from the label means it simply won't display in 1:201{:}20 viewports, while the 1:501{:}50 and 1:1001{:}100 representations remain intact — one object, two active scales. That makes C the correct answer. Choice A is a permanent, destructive action. Deleting the label while 1:201{:}20 is the current annotation scale deletes the entire object, erasing it from all scales — not just the one you want to remove. Choice B controls visibility at the layer level, but turning off a layer in every 1:201{:}20 viewport also hides every other object on that layer, creating unintended consequences; it also doesn't truly remove the scale from the label. Choice D misunderstands what "nonannotative" means — converting the label to a nonannotative object doesn't selectively hide it at one scale; it removes all scale-aware behavior entirely and would affect its appearance at 1:501{:}50 and 1:1001{:}100 as well. A useful rule of thumb: whenever a question asks you to hide or remove an annotative object at one specific scale while preserving it at others, OBJECTSCALE is almost always the precise, non-destructive solution to reach for.

Question 10

A poche hatch is used symbolically to identify cut construction. It is shown in 1:101{:}10 details and 1:501{:}50 plans. The pattern should have approximately the same printed spacing and visual density on both sheets rather than represent a real-world module size.

How should the hatch be configured?

  1. Make the hatch annotative and include both 1:101{:}10 and 1:501{:}50 annotation scales so the pattern plots at consistent density. (correct answer)
  2. Keep the hatch nonannotative so its model-space pattern spacing stays physically constant across all viewports.
  3. Make the hatch associative but nonannotative, because associativity governs how the pattern density is plotted.
  4. Use one nonannotative hatch and manually override the hatch scale property in each viewport's properties palette.
Explanation: Whenever you see a question about hatching across multiple drawing scales, ask yourself: should the pattern represent a real-world measurement, or a consistent visual symbol? Poche hatching is purely symbolic — it signals "this material is cut," so its printed density should look the same whether you're reading a 1:101{:}10 detail or a 1:501{:}50 plan. That's exactly what annotative hatching solves. When you make a hatch annotative and assign both 1:101{:}10 and 1:501{:}50 as supported annotation scales, AutoCAD automatically adjusts the pattern's model-space spacing for each viewport so the plotted result appears at the same visual density on paper. Answer A is correct because it directly addresses the requirement: consistent printed appearance across different scales without manual intervention. Answer B is the most tempting distractor. A nonannotative hatch does keep a fixed model-space spacing — but that means it will plot at very different densities depending on the viewport scale. At 1:101{:}10 the pattern appears ten times denser than at 1:501{:}50, which is exactly the problem the question asks you to solve. Answer C confuses associativity with annotativity. Associativity only controls whether the hatch boundary updates when its geometry changes — it has no effect on how pattern density scales between viewports. Answer *D describes a valid workaround, but "manually override the hatch scale in each viewport's properties palette" is not a standard AutoCAD workflow. Viewport-level hatch scale overrides aren't a built-in per-viewport property the way annotative scaling is. Study tip: Remember that annotative = scale-aware appearance; associative = boundary-aware shape. Exam questions often swap these two terms, so keep their definitions clearly separated.