Fields for Automatic Values - AutoCAD

1. Which combination should be used so the title block reports the required event?
   Answer: Use a PlotDate field and enable the plot bit in FIELDEVAL so the field evaluates each time a sheet is produced. When working with fields in AutoCAD title blocks, you need to match two things precisely: the field type (what event it captures) and the FIELDEVAL setting (what triggers the field to update). Confusing these two independent controls is exactly what this question tests. The scenario demands a timestamp that reflects the plot event specifically — not when the file was saved or created. The PlotDate field is designed exactly for this: it stores the date and time the drawing was last plotted. Pairing it with FIELDEVAL's plot bit (value 8) ensures the field recalculates automatically at plot time, so every sheet carries an accurate, current timestamp. That combination makes B correct. Choice A trips up students who recognize FIELDEVAL correctly but grab the wrong field. SaveDate records the last save event — so if you save at 9 AM and plot at 3 PM, the title block shows 9 AM, which violates the requirement stated in the passage. Choice C compounds two errors: CreateDate captures when the file was originally created (a fixed, never-changing value), and enabling the save bit wouldn't help even if the field were correct — you'd just be refreshing a timestamp that never changes. Choice D misunderstands how fields work. Disabling all FIELDEVAL bits means fields only update when you manually force a regeneration. This introduces human error and defeats the purpose of using a field in the first place. A useful rule of thumb: always ask yourself "what event does this field track?" before worrying about FIELDEVAL. The field type and the trigger bit must describe the same event.
2. What is the best way to restore automatic area reporting?
   Answer: Edit the field, select the replacement polyline, and choose its Area property as the new source. When working with fields in AutoCAD, the key concept to understand is that a field is a live link to a specific object's property — not just a snapshot of a value. When that source object is erased, the link breaks entirely. No amount of regeneration or updating can reconnect a field to a deleted object, because the object's handle no longer exists in the drawing database. The correct approach, answer C, is to edit the MTEXT containing the field, open the Field Editor, and repoint the Object field to the replacement polyline, selecting its Area property as the new source. This re-establishes a live, dynamic link. From that point forward, any change to the replacement polyline's boundary will automatically update the displayed area when the field refreshes. Answer A is tempting because it "solves" the immediate display problem, but converting the field to plain text destroys the automatic reporting entirely — you'd have to manually update the number every time the polyline changes, defeating the whole purpose of using a field. Answer B reflects a common misconception: UPDATEFIELD refreshes existing valid field references, but it cannot resurrect a broken link to an erased object. Running it repeatedly accomplishes nothing when the source no longer exists. Answer D misrepresents what FIELDDISPLAY does. That command simply controls whether invalid field results are shown with a gray background — it has no ability to reassign or locate a substitute object automatically. As a study tip, remember: fields reference object handles, not geometry. Erasing an object permanently severs the link, so restoring automatic reporting always requires manually reconnecting the field through the Field Editor.
3. Which approach creates the appropriate automatic value?
   Answer: Insert a SystemVariable field that references CANNOSCALE and refresh it after the annotation scale changes. When AutoCAD questions involve automatically displaying a drawing property inside text, you should immediately think about Fields — dynamic placeholders that pull live data from the drawing rather than storing static text. The key is identifying which field category holds the specific variable you need. The annotation scale you see in the status bar is controlled by the system variable CANNOSCALE (Current ANNotation SCALE). Inserting a SystemVariable field that references CANNOSCALE means the note automatically updates to reflect whatever annotation scale is active. When you refresh the field (or let AutoCAD refresh it automatically on plot/regen), the displayed value stays current without any manual editing — exactly what the passage requires. D is correct. A is flawed on two levels: MTEXT height is a geometric property of the text object itself, not the annotation scale, and appending a manually formatted suffix defeats the "no manual entry" requirement. You'd be engineering a workaround, not a solution. B targets the wrong system variable. DIMSCALE controls the overall scale factor applied to dimension geometry — it is not tied to the annotation scale workflow and won't reflect what appears in the annotation scale drop-down. C pulls from the Document field category, which stores metadata like the drawing title, author, or file path. It has no mechanism to express or format a scale ratio, making this choice doubly wrong in both category and capability. For the exam, memorize the pairing: annotation scale → CANNOSCALE. Questions about dynamic, auto-updating text in AutoCAD almost always hinge on selecting the correct field category and the correct variable within it — getting only one right is enough to pick a distractor.
4. Which action best meets the requirement for that one note?
   Answer: Convert the field to text, preserving its current displayed result as a static value. When working with AutoCAD fields, you need to understand the fundamental distinction between dynamic and static content. Fields are live placeholders that automatically update to reflect current drawing property values — which is exactly what makes them powerful, and exactly what makes them a problem for archival documents that must be frozen in time. The only way to permanently sever a field's connection to its source data is to convert it into plain text. When you use the MTEXT editor to convert a field to text (or use the CONVERTPTEXT approach), the displayed value is captured as literal characters — no source, no update mechanism, no way for future property edits to change what's shown. This makes D the correct answer: it's the only action that truly guarantees the value never changes again. The distractors each misrepresent how fields actually behave. A is misleading because disabling regeneration doesn't disable field evaluation permanently — fields can still update through other triggers like REGEN, UPDATEFIELD, or file open events, so the value remains vulnerable. B is a common trap: FIELDDISPLAY controls only the gray background shading that makes fields visually identifiable on screen; setting it to zero changes the appearance, not the update behavior — the field still evaluates and changes. C is perhaps the most tempting distractor because UPDATEFIELD sounds like it controls updates, but it actually forces an immediate update — it doesn't lock or disable future evaluations in any way. Your study tip: whenever a question asks about permanently freezing a dynamic value in AutoCAD, think "convert to static." Features that control display or timing never truly break the live link — only conversion does.
5. What should be done to hide the shading while retaining the fields and their automatic behavior?
   Answer: Set FIELDDISPLAY to zero; the field backgrounds will be hidden without converting the values to text. When you see a question about fields in AutoCAD, focus on two separate system variables: one controls how fields are evaluated, and the other controls how they are displayed. Keeping those two concepts distinct is the key to answering this correctly. The system variable FIELDDISPLAY is a display-only toggle. Setting it to 0 turns off the gray background shading that appears behind field values in the drawing editor. Critically, it does nothing to the field itself — the value still updates automatically based on its source, and it still plots as a live field. This is exactly what the scenario requires: hide the visual noise for the reviewer without sacrificing automatic behavior. So A is correct. B is a trap because FIELDEVAL controls when fields are recalculated (for example, on save, on plot, or never). Setting it to zero would freeze field updates entirely — the opposite of retaining automatic behavior — and it would have no effect on the gray background shading at all. C is the most tempting distractor. Converting fields to static text does remove the gray background, but it also destroys the automatic updating behavior. The question explicitly requires that you retain the automatic behavior, so this approach fails the core requirement. D is a fabricated concept. There is no "background plotting" setting in AutoCAD that suppresses field shading. This distractor tests whether you might confuse background plotting (a performance option) with field background display. A good study tip: memorize FIELDDISPLAY (appearance) vs. FIELDEVAL (recalculation schedule) as a pair — exam questions love to swap them.
6. Which field source should be used for the label so it reflects the correct viewport scale and updates when that viewport's scale changes?
   Answer: An Object field referencing the specific viewport's Standard Scale property. When working with fields in AutoCAD, the key question to ask is: what object actually owns the property I want to display? Fields are most reliable when they reference the specific object that holds the data you need — not a system-wide variable that might reflect something else entirely. In this scenario, the viewport itself stores its Standard Scale property. When you insert an Object field and select that specific viewport, you can target its Standard Scale property directly. This means if someone later changes that viewport from $1:100$ to $1:50$, regenerating the drawing updates the field automatically — because the field is tethered to that exact viewport object. That's why C is correct. A is a trap for students who confuse annotative scaling with viewport scale display. An MTEXT object's Annotative property describes how the text itself scales across viewports — it has nothing to do with reporting a viewport's assigned scale. B is tempting because CANNOSCALE sounds relevant — it's the "current annotation scale" system variable. However, CANNOSCALE reflects whatever scale is active at the moment, which changes depending on which viewport is active when you work. If you click into a different viewport, CANNOSCALE shifts, making this field unreliable for labeling one specific viewport's scale. D is a distractor that tests whether you know field categories. A Document field pulls drawing-level metadata like revision numbers or dates — completely unrelated to viewport geometry or scale. Your study tip: when a field must track a specific object's property, always choose an Object field referencing that object directly. System variables are global and context-sensitive — too unpredictable for viewport-specific labeling.
7. Which field configuration will display the required value as $125.00$ and update when the polyline changes?
   Answer: Insert an Object field for Area, apply a conversion factor of $1/144$, and set decimal precision to two places. Whenever AutoCAD fields are involved, you need to think carefully about two things: which property you're extracting, and what conversion factor actually transforms that property into the desired unit. Area in AutoCAD is stored in square drawing units. Since one drawing unit equals one inch, the drawing reports area in square inches. To convert square inches to square feet, you divide by $144$ (because $12 \times 12 = 144$ square inches per square foot). Applying this to the polyline: $18{,}000 \div 144 = 125.00$ square feet — exactly the target value. The correct approach is B: insert an Object field referencing the polyline's Area property, set the conversion factor to $1/144$, and set decimal precision to two places. Because the field is linked to the polyline object, it automatically recalculates whenever the geometry changes. A is tempting but wrong. Dividing by $12$ converts linear inches to feet, not square inches to square feet. Using $1/12$ would yield $1{,}500$, not $125.00$ — a classic unit-dimension error. C makes two mistakes: it references the Length property instead of Area, and it uses the wrong conversion factor of $1/12$. Length is a perimeter measurement, which has nothing to do with the floor area the question asks about. D hardcodes the value $18{,}000/144$ directly into a Formula field. While the math is correct, a static formula won't update if the polyline changes shape — it breaks the live-link requirement stated in the passage. A useful memory rule: every time you move between unit dimensions, square the linear conversion factor. Linear: divide by $12$. Area: divide by $12^2 = 144$. Volume would require dividing by $1{,}728$.
8. What is the most direct way to refresh the displayed value immediately without changing the automatic-update settings?
   Answer: Select the MTEXT object and run UPDATEFIELD to evaluate the field on demand. When working with fields in AutoCAD, it helps to understand that fields are dynamic text placeholders that pull live data from objects or drawing properties. The key concept here is the difference between automatic evaluation (triggered by events like saving or regenerating) and manual, on-demand evaluation — which is what this question tests. When a field's displayed value is stale and you need to refresh it immediately without touching the FIELDEVAL system variable, the tool you reach for is UPDATEFIELD. By selecting the MTEXT object and running UPDATEFIELD (choice A), you force AutoCAD to re-evaluate only the selected field right now, regardless of what FIELDEVAL allows or prohibits. This is the most direct, surgical solution — no settings change required. Choice B is tempting but wrong. REGENALL regenerates all viewports, but field evaluation during regeneration is explicitly disabled by the FIELDEVAL setting described in the passage. Running REGENALL won't override that restriction, so the field stays stale. Choice C is not a field update at all — it replaces a dynamic field with a static typed value, which defeats the entire purpose of using a field and breaks the live link to the polyline. Choice D misunderstands what FIELDDISPLAY does. That variable controls only whether fields are displayed with a gray background highlight — it has nothing to do with triggering recalculation or replacing cached values. Your study tip: remember that UPDATEFIELD = on-demand refresh without altering any automatic-update behavior. Exam questions about fields often test whether you know this manual override exists, so keep it in your toolkit alongside FIELDEVAL.
9. Which setup best satisfies the requirement?
   Answer: Insert a Filename document field, include the extension, exclude the path, and enable field updating on save. When AutoCAD drawing files need to display dynamic, self-updating text — especially file names — the tool to reach for is a document field. Fields are placeholder values that AutoCAD recalculates automatically based on triggers you configure, making them far more reliable than static text for information that can change. The Filename document field is specifically designed to pull the active drawing's file name. When you insert it, AutoCAD gives you two key options: whether to include the file extension and whether to include the folder path. The company standard calls for the extension but not the path, so you configure it exactly that way. Crucially, you must also enable field updating on save, so that after a Save As operation renames the file, the footer immediately reflects the new name on the next save cycle. Option A does all of this correctly — right field type, right format options, right update trigger. Option B fails on two counts: it excludes the extension (violating the standard) and triggers updates on open rather than on save, meaning a Save As wouldn't update the footer until the file is reopened. Option C uses ordinary static text, which never updates automatically regardless of what triggers you enable — field-update settings only affect actual fields, not typed text. Option D misuses the SaveDate field, which stores the last-saved date/time, not the file name; no formatting option converts it into a meaningful file name. Study tip: On AutoCAD field questions, always match three things: the correct field type, the correct format options, and the correct update trigger. Missing any one of the three will make the setup fail in practice.
10. Which method preserves automatic calculation most effectively?
    Answer: Place a table formula referencing A1 and A2 in A3, then update the affected fields after edits. When AutoCAD tables need to stay synchronized with changing geometry, the key distinction is between static values and live, linked content. Ask yourself: if a boundary changes, how many things need updating — and can any of those updates happen automatically? The most robust solution is B: placing a table formula in A3 that references cells A1 and A2 (e.g., =A1+A2). Since A1 and A2 already contain Object fields linked to each zone's area, updating those fields after a boundary edit causes A3 to recalculate automatically. You get a fully dynamic chain — geometry drives the fields, and the formula drives the summary cell. No manual arithmetic required. A breaks that chain at the summary level. You're still updating the two Object fields, but A3 holds a hardcoded number. Every time areas change, you must remember to manually revise A3 — a reliable source of human error on complex drawings. C is a conceptual mismatch. A Filename field reports file-related metadata (the drawing's name or path), not geometric area. Reformatting it as an "area" doesn't give you real geometry data — it's meaningless in this context. D collapses the automation entirely. Copying the A1 Object field gives you one live value, but adding A2's result as plain text means that second value is frozen at the moment you typed it. Any future change to Zone 2's boundary goes unnoticed in A3. Study tip: On AutoCAD table questions, watch for answers that update some links but leave at least one value static — that partial automation is a classic distractor designed to look almost correct.

Start this quiz