Spellcheck - AutoCAD

  1. What should the drafter do to perform the required comprehensive review?
    Answer: Run SPELL with the appropriate drawing scope; live checking does not replace a drawing-wide scan When working with spelling tools in AutoCAD, it helps to distinguish between two separate features: live (as-you-type) spell checking and the SPELL command. Live checking only flags misspellings while you are actively editing a text object — it does not scan text that already exists in the drawing. Understanding this distinction is exactly what this question tests. To review all existing annotation in a drawing, you need to run the SPELL command, which lets you select a scope — current selection, current space/layout, or the entire drawing. This draws-wide scan is the only way to catch errors in preexisting notes and dimensions that were never opened in the text editor since live checking was enabled. Answer A is correct because it accurately reflects that live checking and a drawing-wide SPELL scan serve different, complementary purposes. Answer B is wrong because reopening the drawing does not trigger any automatic spell-correction process — AutoCAD has no mechanism that retroactively corrects annotation on file open. Answer C is a trap: REGEN refreshes the display of geometry and linetype scales, but it has absolutely no interaction with the spelling engine and will not produce underlines on closed text objects. Answer D confuses the AUDIT command, which repairs drawing file integrity issues (corrupt objects, database errors), with spelling functionality — AUDIT has nothing to do with text content or spell checking. A useful habit: whenever an AutoCAD question contrasts a real-time editor feature with a drawing-wide operation, ask yourself whether the feature requires something to be actively open. If yes, a dedicated command (like SPELL) is needed for the broader task.
  2. What should the drafter do when SPELL identifies the acronym?
    Answer: Select Add to Dictionary, using the active custom dictionary When working with AutoCAD's SPELL command, you need to understand the distinction between session-level responses and persistent, workstation-level responses. The question specifically asks for a solution that both stops the current flagging and carries over to future drawings on the same machine — that two-part requirement is your filtering clue. Selecting Add to Dictionary (D) writes the word directly into the active custom dictionary file (a .dct file stored on the workstation). Once saved there, SPELL will recognize the term in every future drawing opened on that machine, satisfying both conditions in the scenario. This is the correct approach. A is wrong because Ignore only skips the word for the remainder of the current SPELL session. The moment you close the dialog or open a new drawing, the word gets flagged again — no permanent record is created anywhere. B is wrong on two counts. First, Ignore All still only applies to the active session, not future drawings. Second, Ignore All does not write anything to any dictionary — it simply suppresses the flag globally within the current run. The claim that it "writes the word to the main dictionary" is entirely false. C is wrong because Change All would replace the acronym throughout the drawing with a substitution, which is the opposite of what the drafter wants. The goal is to preserve "FACP," not eliminate it. A helpful study tip: on AutoCAD exam questions about SPELL, watch for phrases like "future drawings" or "other users on the same workstation" — those cues always point to Add to Dictionary, since it's the only option that creates a lasting, reusable record.
  3. Which action most directly meets the requirement?
    Answer: Choose Change All and replace "seperator" with "separator" When AutoCAD's SPELL command flags a misspelled word, you have several response options — and understanding exactly what each one does is what this question tests. The key distinction here is between correcting one occurrence, correcting all occurrences, and managing dictionary entries. The requirement has two parts: fix every matching instance in one action, and avoid adding anything to the dictionary. Choice A, Change All, does precisely this — it replaces every instance of "seperator" with your typed correction "separator" throughout the drawing in a single operation, without touching any dictionary file. This is the most efficient and targeted solution. Choice B is a trap because Ignore All does the opposite of correcting — it tells AutoCAD to skip all occurrences of the flagged word for the rest of the session. You cannot pair it with a replacement; it simply suppresses further flags. Choice C, Add to Dictionary, actually works against you here. Adding "separator" to the custom dictionary would make AutoCAD accept the correct spelling as known, but it does nothing to fix the misspelled instances already in the drawing. It also violates the requirement of not creating a dictionary entry. Choice D, Change once, only corrects the single currently flagged instance. You would then need to relaunch SPELL repeatedly for each remaining occurrence — an inefficient workaround that defeats the purpose of a batch correction tool. As a study tip, remember that AutoCAD's spell-check options mirror those in word processors: Change/Change All corrects, Ignore/Ignore All skips, and Add modifies the dictionary. Matching the right tool to the stated scope — one occurrence vs. all — is a frequent exam theme.
  4. What best explains the result?
    Answer: Both words are correctly spelled, and SPELL does not determine meaning from context When working with AutoCAD's SPELL command, it's important to understand exactly what the tool does — and doesn't — do. SPELL performs orthographic checking: it compares each word against a dictionary to confirm the word exists as a valid spelling. It has no awareness of grammar, intent, or context. That's precisely why answer B is correct. Both "brake" and "break" are real, correctly spelled English words. SPELL finds each word in its dictionary and flags no errors. The second note contains a semantic error — the wrong word was chosen — but SPELL cannot detect that because it never evaluates whether a word fits the surrounding meaning. Answer A is a trap that invents a fictional limitation. SPELL does not filter words by part of speech. Verbs, nouns, adjectives — all are checked equally. There is no verb-exclusion behavior in AutoCAD's spelling checker. Answer C misrepresents how the custom dictionary works. Custom dictionaries in AutoCAD allow you to add specialized or domain-specific words so they aren't flagged as errors. They do not group homophones or treat similar-sounding words as interchangeable entries — that concept simply doesn't exist in this tool. Answer D is also fabricated. SPELL can check text across multiple object types, including multiline text, single-line text, dimension text, and attribute values. It doesn't selectively exclude "ordinary note sentences" — that distinction doesn't exist. The broader study tip here: on AutoCAD exam questions about SPELL, always ask yourself whether the issue is a spelling problem or a meaning problem. SPELL catches the former, never the latter.
  5. Which dictionary configuration is most appropriate?
    Answer: Use a British English main dictionary and retain the equipment codes in a custom dictionary When configuring AutoCAD's spell checker for a specialized drawing, you need to think in two layers: the main dictionary controls the language standard, while the custom dictionary handles project-specific terms that no standard dictionary would know. AutoCAD allows you to select a main dictionary by language — including British English variants. Switching to a British English main dictionary means words like "centre" and "colour" are natively recognized without any workarounds. Then, because equipment codes are unique to your project, they belong in the custom dictionary, which acts as a supplemental word list sitting alongside the main one. This two-tier setup — correct answer A — is exactly the right configuration. B is a workflow trap. Clicking "Ignore All" for every flagged British word silences the warnings session by session, but those dismissals don't persist across drawings or users. You'd repeat the process indefinitely, and equipment codes would still go unmanaged. C sounds creative but breaks the system. The main dictionary is the authoritative language foundation; disabling it leaves you with only your custom list, meaning thousands of correctly spelled common words would be flagged. You'd be building a dictionary from scratch unnecessarily. D reverses the logic entirely. The main dictionary is a locked, vendor-supplied file — you cannot add project-specific equipment codes to it. Custom dictionaries exist precisely because they are user-editable. Study tip: On AutoCAD exam questions about SPELL, remember the rule: main dictionary = language standard (select the right one), custom dictionary = your additions. Any answer that inverts or bypasses this structure is a distractor.
  6. Which workflow best limits corrections to the revised annotation?
    Answer: Choose Selected Objects and specify only the revised notes and dimensions When using AutoCAD's SPELL command, the critical decision is scope — which objects get checked. The command offers several scope options, and choosing the right one determines whether you accidentally alter approved content. Whenever a question describes pre-selected objects and restricted editing, your instinct should be to work with that selection set directly. Since the drafter already selected the three revised notes and two dimensions before launching SPELL, choosing Selected Objects (answer C) restricts the spell check exclusively to those five objects. AutoCAD honors the pre-existing selection, so no approved annotation is ever at risk of unintended changes. This is the most precise, professional workflow. A is flawed because "Entire Drawing" scans every text object in the file, and relying on "Ignore All" to protect approved content is error-prone — one misclick could alter something that was already signed off. It's manual and risky. B sounds reasonable, but locking layers prevents editing, not checking. SPELL may still flag words on locked layers, and the workflow adds unnecessary complexity. It also doesn't leverage the pre-selected objects at all, wasting the drafter's preparation. D is the worst approach. Adding every approved term to a custom dictionary just to protect them pollutes the dictionary permanently and still runs the check across the entire drawing. It's a workaround that creates a new problem. The study tip here: pre-selecting objects before a command is a deliberate, powerful workflow in AutoCAD. When a question mentions objects selected before a command, the answer almost always involves using the "Selected Objects" scope to honor that selection.
  7. Which SPELL scope should the reviewer use?
    Answer: Entire Drawing, because the required text spans model space and multiple layouts When working with SPELL in AutoCAD, the key concept to understand is scope — the range of objects the spell-checker will examine. AutoCAD gives you three main scope options: Selected Objects, Current Space/Layout, and Entire Drawing. Choosing the right one determines whether annotations across different environments get checked. In this scenario, text lives in three distinct locations: model space, the current layout, and two additional layouts. To catch all of it in a single pass, you need a scope that crosses every environment — and that's exactly what Entire Drawing does. It instructs SPELL to scan model space and all paper-space layouts simultaneously, making option B the correct choice. Option A is tempting but wrong. Current Space/Layout only checks the active environment — it does not automatically pull in model-space content when you're in a layout, or vice versa. You'd miss annotations in the other environments entirely. Option D extends this same flawed logic by suggesting you repeat the process per layout — that technically works but defeats the purpose of doing it "in one operation," which the question explicitly requires. Option C misrepresents how SPELL works; the tool does not inherently exclude dimension text or layout text, and forcing a manual selection on a large drawing introduces the risk of missing objects. A good study tip: whenever an AutoCAD question asks about checking or modifying content that spans both model space and multiple layouts, think immediately of commands or settings that operate at the Entire Drawing level. That phrasing in the scenario is your signal to rule out any scope limited to a single environment.
  8. Which correction preserves the dimension's measured value while fixing the annotation?
    Answer: Change only EQUL to EQUAL, leaving <> and SPACES unchanged When working with dimension text overrides in AutoCAD, you need to distinguish between two components: the measurement placeholder (<>) and any supplemental annotation you add around it. The <> token dynamically displays the dimension's measured value — it's what keeps the dimension "associative," meaning it updates automatically when geometry changes. Your goal in editing is to fix only what's broken without disturbing that live connection. Here, the override <> EQUL SPACES contains a typo in the supplemental word. The fix is straightforward: edit the override text to read <> EQUAL SPACES, changing only the misspelled word while leaving <> and SPACES intact. This is exactly what C does, preserving the dynamic measurement while correcting the annotation. A is tempting if you misread the goal as "make the text accurate," but replacing the entire override with EQUAL SPACES removes <> entirely. The dimension would then display static text instead of the measured value — breaking associativity and defeating the purpose of using a dimension in the first place. B misrepresents how AutoCAD works. You absolutely can edit dimension text overrides; they aren't locked. Adding a misspelling to your custom dictionary just suppresses the spell-check warning without actually fixing the error — that's never the right professional approach. D compounds the problem by deleting the override and hardcoding the current measurement as fixed text. This is even worse than A, because now if the geometry changes, the dimension annotation silently lies. Strategy tip: On AutoCAD exam questions involving dimension text, always ask yourself: "Does this action preserve or destroy the <> placeholder?" Losing <> means losing associativity — almost always the wrong trade-off.
  9. Which corrective action addresses the cause rather than only the existing text?
    Answer: Remove "alighnment" from the custom dictionary, then correct existing occurrences When AutoCAD's spell checker accepts a misspelled word, it's usually because that word was added to the custom dictionary — a persistent file that applies across all drawings. This question tests whether you understand the difference between fixing a symptom (bad text in one drawing) versus fixing the root cause (a corrupted dictionary entry). The real problem here isn't just text on a canvas — it's that the custom dictionary is poisoned. Every future drawing, and every spell check run on existing drawings, will continue to accept "alighnment" as correct. The only way to truly fix this is to remove the misspelling from the custom dictionary, then go back and correct any text where that wrong spelling already slipped through. That's exactly what B does, targeting both the cause and the consequence. Choice A only cleans up text in a single drawing using Change All, but leaves the dictionary corrupted — so every other drawing remains vulnerable and future spell checks will still miss the error. Choice C misunderstands what "Selected Objects" does; it narrows the scope of a spell check to highlighted objects rather than the whole drawing, but it does nothing about what the dictionary considers valid. The misspelling would still be accepted. Choice D is particularly dangerous — adding the correct spelling "alignment" doesn't remove the incorrect one; AutoCAD doesn't treat dictionary entries as synonyms or replacements, so both spellings would simply coexist as "correct." A useful rule of thumb: whenever a problem originates from a settings or configuration file (like a custom dictionary), the fix must happen at that level — not just in the output it produces.
  10. Which action best provides consistent spell-check results at both offices?
    Answer: Provide the custom dictionary file to the receiving office and configure that installation to use it When AutoCAD's SPELL command runs, it references a custom dictionary file stored externally on the local workstation — typically a .cus file. This file lives outside the DWG and is never embedded in the drawing itself. Whenever you see a question about spell-check consistency across offices, ask yourself: where does AutoCAD actually store custom word data, and does that file travel with the drawing? Because the custom dictionary is a separate file, simply sending the DWG is never enough. The correct approach, as C states, is to physically provide the custom dictionary file to the receiving office and configure that AutoCAD installation to point to it. Once both workstations reference the same .cus file, SPELL produces identical results everywhere. A is a creative-sounding but completely fictional workflow — AutoCAD's SPELL tool reads from dictionary files, not from text objects placed in model space. Hiding multiline text in the drawing has no effect on spell-check behavior whatsoever. B is a trap for students who assume PURGE optimizes or "packages" file data; PURGE removes unused named objects like layers and blocks, and has nothing to do with dictionary storage. D exploits a misconception about legacy DWG formats — no version of the DWG format supports embedded dictionary storage. Saving to an older format would only risk losing newer drawing features, not solve the dictionary problem. The key study tip here: remember that AutoCAD's support files — custom dictionaries, plot styles, linetypes, and templates — live outside the DWG. Cross-office workflows almost always require manually sharing and configuring those support files on each workstation.

Start this quiz