AutoCAD Quiz: Packaging Drawings For Sharing
10 questions · exam conditions
0:00
Packaging Drawings For SharingQuestion 1 of 10

A consultant must receive a host drawing and its architectural and structural xrefs. The consultant needs to revise each referenced discipline drawing separately and then reload the changes in the host drawing.

Which transmittal approach best preserves the required workflow?

Include the xref files with the package, retain them as external references, and use portable reference paths.
Bind the xrefs into the host drawing and purge the original external-reference definitions from the package.
Bind the xrefs using the Insert option so matching layers merge into the host drawing automatically.
Export the host layout to PDF and omit the referenced DWG files to prevent path-related errors.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Packaging Drawings For Sharing

Practice Packaging Drawings For Sharing 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 Packaging Drawings For Sharing, 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 must receive a host drawing and its architectural and structural xrefs. The consultant needs to revise each referenced discipline drawing separately and then reload the changes in the host drawing.

Which transmittal approach best preserves the required workflow?

  1. Include the xref files with the package, retain them as external references, and use portable reference paths. (correct answer)
  2. Bind the xrefs into the host drawing and purge the original external-reference definitions from the package.
  3. Bind the xrefs using the Insert option so matching layers merge into the host drawing automatically.
  4. Export the host layout to PDF and omit the referenced DWG files to prevent path-related errors.
Explanation: When a question describes a multi-party workflow where a consultant must edit referenced files independently and reload changes, you should immediately focus on preserving the xref relationship — not collapsing it. The entire point of external references is that they remain live, updateable links. Any approach that destroys that link defeats the purpose. Option A is correct because it keeps the xrefs as true external references, packages them alongside the host drawing, and uses portable paths (typically relative paths) so the consultant's machine can resolve the file locations regardless of drive letter or folder structure. The consultant can open each discipline DWG, make revisions, save, and then reload the xref in the host — exactly the workflow described. Option B fails because binding an xref permanently embeds it into the host drawing as a block, severing the external link entirely. Once bound, there is no separate discipline file to revise and reload — the whole workflow collapses. Option C describes the Insert method of binding, which goes even further than standard binding: it merges xref layers directly into the host's layer list and dissolves the xref definition completely. This causes layer naming conflicts and, again, destroys the live reference — making independent revision impossible. Option D is a dead end. Exporting to PDF converts the drawing to a static image format. No DWG files means no editing, no reloading, and no xref workflow at all. Study tip: On AutoCAD workflow questions, match the tool to the task. If the workflow requires updating referenced files, the answer will always preserve external references — binding or exporting are finishing moves, not collaboration tools.

Question 2

An office drawing uses a custom shape font named archspec.shx. On the packaging workstation, AutoCAD displays the text with a substitute font because archspec.shx is missing. The operator does not notice any visibly blank text.

What should the operator do before issuing the transmittal?

  1. Accept the displayed substitution and include only the current font-mapping file in the transmittal package.
  2. Explode all affected text into linework so the recipient will not require any text-related support files.
  3. Rename an available SHX file to archspec.shx so the drawing's stored font name resolves during packaging.
  4. Obtain the correct licensed SHX file, verify the intended text display, and regenerate the transmittal with that dependency. (correct answer)
Explanation: When preparing a transmittal package in AutoCAD, your goal is to ensure the recipient experiences the drawing exactly as intended — same fonts, same appearance, no substitutions. Font substitution is a silent problem: AutoCAD replaces a missing SHX file with a proxy font and keeps rendering text, so nothing looks obviously broken on your screen, even though the underlying dependency is unresolved. The correct path is D. Before packaging, you must obtain the actual archspec.shx file, load it so AutoCAD renders the text correctly, visually confirm the output matches the original design intent, and then regenerate the transmittal so the real font file is captured as a dependency. Only at that point can you be confident the recipient's session will behave identically. Choice A fails because including only a font-mapping file documents the substitution rather than fixing it — the recipient still won't have the correct font, and the mapping file simply perpetuates the workaround. Choice B is tempting but destructive: exploding text into linework eliminates editability, inflates file size, and is an irreversible change that should never be a default transmittal strategy for a font problem. Choice C is dangerous — renaming an unrelated SHX file to archspec.shx feeds AutoCAD the wrong glyph definitions, which could silently corrupt all text rendered from that font; the displayed characters would be wrong, not just substituted. As a study tip, watch for any AutoCAD question where a "workaround" looks convenient — on the exam, the right answer almost always resolves the root cause rather than masking it. When fonts are involved, ask yourself: does this solution guarantee identical output for the recipient?

Question 3

A host drawing references Civil\grid.dwg and Electrical\grid.dwg. The two files have the same base filename but contain different discipline information. Both references currently resolve correctly.

Which eTransmit folder strategy most safely preserves both references?

  1. Place every dependency in one folder and allow the later grid.dwg file to replace the earlier file.
  2. Maintain an organized folder structure and verify that the transmitted drawings use the corresponding portable paths. (correct answer)
  3. Remove both xref paths and rely on AutoCAD's support-file search order to distinguish the two filenames.
  4. Exclude one grid.dwg file and let the recipient reload both references from the remaining packaged copy.
Explanation: When packaging drawings for transmission in AutoCAD, the core challenge is preserving how xref paths resolve — especially when two referenced files share the same filename but live in different folders. This question tests whether you understand that folder structure is what disambiguates identically named xrefs. Maintaining the original folder hierarchy (Civil\ and Electrical) is the safest strategy because each grid.dwg retains its unique relative path. When eTransmit packages files using relative (portable) paths, the host drawing can still distinguish Civil\grid.dwg from Electrical\grid.dwg — they never collide. This is exactly what B describes, making it the correct answer. A is dangerous precisely because flattening everything into one folder forces both files to compete for the same filename in the same location. The second file copied would silently overwrite the first, leaving the recipient with only one grid.dwg serving both xref slots — corrupting the discipline-specific data one reference was meant to provide. C misunderstands AutoCAD's support-file search path. That mechanism helps AutoCAD find a file when no path is specified, but it cannot distinguish between two files with identical names in different searched folders — it simply returns whichever it finds first. Stripping paths doesn't solve the collision; it makes it worse. D is essentially the same problem as A, just stated more explicitly. Dropping one file and expecting the recipient to load both references from a single copy means one xref will always display wrong content. As a study tip: whenever you see eTransmit questions involving shared filenames, think path uniqueness first — the folder structure is the only thing AutoCAD uses to tell those files apart.

Question 4

A project uses standard AutoCAD objects and was created in a newer DWG format than the recipient can open. The sender must retain the current-format source files while delivering compatible copies of the host drawings and xrefs.

Which workflow best meets both requirements?

  1. Run SAVEAS on only the host drawing and leave every packaged xref in its original newer file format.
  2. Configure eTransmit to convert packaged drawings to the recipient's format, then validate the converted package separately. (correct answer)
  3. Create a normal ZIP package because ZIP compression automatically converts all enclosed DWG file versions.
  4. Tell the recipient to rename each DWG extension after extraction so AutoCAD treats it as an older format.
Explanation: When AutoCAD file compatibility is the issue, think in two layers: preserving the original source files and delivering a complete, self-contained package where all referenced files — including xrefs — are also compatible. Missing either layer creates a problem. eTransmit is AutoCAD's dedicated tool for bundling drawings with their dependencies (xrefs, fonts, images) into a single transmittal package. Critically, it includes a format-conversion option that lets you downgrade all packaged DWGs to an older version during the transmittal process — without touching your originals. This is exactly why B is correct: eTransmit handles both the host drawing and every xref simultaneously, and validating the converted package afterward confirms the recipient can actually open everything. A fails because it only converts the host drawing. Any xrefs left in the newer format will cause missing or unresolvable reference errors when the recipient opens the file — a classic incomplete workflow trap. C is a common misconception worth eliminating firmly: ZIP compression is a lossless archiving format. It reduces file size but never alters file contents, version numbers, or DWG format headers. Zipping a newer DWG produces a smaller newer DWG, nothing more. D describes a workaround that simply doesn't work. AutoCAD reads the internal DWG file header to determine format version — it ignores the file extension entirely. Renaming .dwg files accomplishes nothing. Your study tip: on AutoCAD workflow questions, always ask yourself whether a proposed solution handles all associated files (especially xrefs), not just the primary drawing. eTransmit exists precisely because manual SAVEAS misses dependencies.

Question 5

At 10:00 a.m., a coordinator creates an eTransmit ZIP file and reviews its report. At 11:00 a.m., the structural consultant replaces a referenced DWG with a revised file using the same filename and path. The coordinator then emails the 10:00 a.m. ZIP file.

What is the quality-control problem, and what is the appropriate correction?

  1. There is no problem because the ZIP resolves the xref from its original network path whenever the recipient opens it.
  2. Reload the revised xref in the source host drawing, but continue distributing the original ZIP without modification.
  3. Only the transmittal report is stale; replace the report while retaining the original packaged DWG dependencies.
  4. The package is stale; recreate eTransmit after the revision and verify the new package's contents and report. (correct answer)
Explanation: When working with eTransmit, the key concept to understand is that the ZIP package captures a snapshot of all referenced files at the moment of creation — it does not maintain a live link to any network location. So when timing and file revisions are involved, ask yourself: does the package reflect the current state of all dependencies? In this scenario, the consultant updated the structural DWG after the 10:00 a.m. package was created. That means the ZIP contains the old version of the file. When the coordinator emails it, recipients receive outdated geometry — a serious quality-control failure. The correct fix, as D states, is to recreate eTransmit after the revision, then verify both the packaged files and the transmittal report to confirm the right versions are included. A is fundamentally wrong because eTransmit does not resolve xrefs from their original network paths at open time — that's precisely why eTransmit exists. It bundles everything locally so recipients without network access can open the drawing successfully. There is no live-path fallback. B reveals a misunderstanding of scope: reloading the xref updates the host drawing's session, but the already-created ZIP is completely independent. Distributing the old package still sends stale data. C is a subtle trap. The report is indeed stale, but the packaged DWG dependency itself is also the wrong version — you can't fix a content problem by only swapping the report file. As a study tip, remember: eTransmit = point-in-time snapshot. Any file change after packaging invalidates the entire bundle, not just its documentation.

Question 6

A contract set is organized in a sheet set containing 24 sheet drawings. The cover drawing directly references only three of those files. The coordinator runs eTransmit on the cover DWG and assumes the entire contract set will be included.

Which action most reliably packages all required sheets and their dependencies?

  1. Select all required sheets through the sheet-set transmittal workflow, then review the resulting file list before release. (correct answer)
  2. Bind the three cover-sheet references, because binding causes AutoCAD to discover and include every drawing listed in the sheet set.
  3. Add the sheet-set DST file beside the cover drawing, because the DST file contains complete embedded copies of all sheet DWGs.
  4. Transmit only the cover drawing, because eTransmit automatically includes every DWG located anywhere in the project folder tree.
Explanation: When working with eTransmit and sheet sets, the key concept to understand is that eTransmit only discovers dependencies by following explicit file references — it cannot infer what belongs to a project based on folder location or sheet-set membership alone. The coordinator's mistake is assuming eTransmit is "project-aware" when it is only "reference-aware." The most reliable approach is A: using the sheet-set transmittal workflow, which lets you explicitly select all 24 sheets as the starting point, then review the complete file list before packaging. This method ensures every sheet DWG — plus each sheet's own xrefs, images, fonts, and plot styles — gets captured and verified before release. B is a trap because binding xrefs in the cover drawing only resolves the three files the cover directly references. Binding has no mechanism to scan or discover unrelated sheets listed in a sheet set — it simply internalizes already-attached references. C misrepresents what a DST file is. The sheet-set data file (.dst) stores pointers and metadata about sheets — it does not contain embedded copies of any DWG files. Including it in a transmittal does not bring the actual drawing files along. D is flat-out false. eTransmit does not crawl your entire folder tree looking for project-related files. It follows only the reference chain (xrefs, images, etc.) anchored to the specific DWG you transmit. Drawings with no xref connection to the cover are simply ignored. Study tip: On AutoCAD workflow questions, always ask yourself whether a tool is reference-driven or project-aware — eTransmit is strictly reference-driven, so your file selection is everything.

Question 7

An xref named future-equipment.dwg is intentionally Unloaded so it does not appear in the current issue. The recipient must nevertheless receive the file because it will be reloaded during the next design phase. It is listed in the Create Transmittal dialog.

How should the coordinator handle this file?

  1. Bind the unloaded xref before packaging so it remains invisible but can later be restored as an external reference.
  2. Exclude the xref because an unloaded reference can never be reloaded after a package is extracted elsewhere.
  3. Leave the listed xref selected for inclusion, document its unloaded status, and verify that it exists in the package. (correct answer)
  4. Detach the xref and copy only its cached display data, which preserves the option to reload the source file later.
Explanation: When working with eTransmit and external references, the key distinction to understand is that xref status (loaded vs. unloaded) and xref inclusion are two separate concerns. An unloaded xref is still a legitimate part of the drawing's reference structure — it simply isn't displayed. AutoCAD's Create Transmittal dialog recognizes this and lists unloaded xrefs precisely because the host drawing still depends on them for future use. Option C is correct because it honors the workflow's intent. The file is unloaded by design, not by accident, and the recipient will need it during the next phase. Leaving it selected in the transmittal package ensures the file travels with the drawing set. Documenting its unloaded status prevents confusion for the recipient, and verifying its presence in the package confirms nothing was accidentally omitted. Option A is wrong because binding an xref merges it permanently into the host drawing, destroying the external reference relationship entirely. You cannot later "un-bind" it and restore the original xref link. Option B is a factual misconception — an unloaded xref absolutely can be reloaded after a package is extracted, as long as the source file is present and the path resolves correctly. Option D describes something that doesn't exist in AutoCAD; there is no "cached display data" for an unloaded xref, and detaching an xref removes it from the reference list permanently. A useful rule of thumb: in transmittal questions, inclusion is about making sure all referenced files are packaged — xref status (loaded/unloaded) is a display setting, not a reason to exclude a file from the package.

Question 8

A drawing's page setup uses office.ctb and production.pc3. The PC3 file was configured for a printer driver that the recipient may not have. The recipient needs the drawing files and a dependable record of the approved plotted appearance.

Which package provides the strongest quality-control result?

  1. Include only production.pc3, because a PC3 file embeds the printer driver and all color-dependent plotting rules.
  2. Include only office.ctb, because the plot style table automatically recreates the missing device configuration.
  3. Include the CTB and PC3 dependencies and also provide an approved PDF produced on the sender's validated system. (correct answer)
  4. Omit both support files and set every transmitted drawing's default plotter to the recipient's system printer.
Explanation: When a drawing depends on external support files, you need to think about two separate problems: file dependency and output verification. A recipient missing the right software or driver may not be able to reproduce the plotted result accurately, even if you send the support files. Sending the CTB and PC3 files together is the necessary first step — the CTB (office.ctb) controls how colors map to pen weights and styles, while the PC3 (production.pc3) stores the device configuration, paper sizes, and port settings for the target plotter. Neither file alone is sufficient. However, even with both files, the recipient could still encounter driver conflicts or misconfiguration on their end. That's why C is the strongest answer: providing an approved PDF generated on your own validated system gives the recipient a locked, device-independent visual reference of exactly what the drawing is supposed to look like. The PDF acts as a quality-control benchmark that no missing driver can corrupt. Choice A is wrong on a factual point — a PC3 file does not embed the printer driver itself; it only references it. If the driver isn't installed on the recipient's machine, the PC3 file alone solves nothing. Choice B is equally flawed: a CTB file only defines plot style assignments; it has no ability to recreate device configuration or compensate for a missing plotter setup. Choice D is the weakest option — omitting both support files and defaulting to the recipient's system printer almost guarantees inconsistent output with no way to verify accuracy. Your study takeaway: on AutoCAD exam questions about file sharing, look for answers that address both dependency transfer and output verification — the most defensible workflow always includes a validated reference document.

Question 9

For a regulatory archive, all xrefs must be incorporated into one DWG. The archive must still preserve the distinction between a host layer named WALL and an xref layer also named WALL.

Which xref binding method should be selected when creating the archive package?

  1. Use Bind, which retains xref-dependent symbol distinctions by assigning qualified names in the host drawing. (correct answer)
  2. Use Insert, which merges identically named dependent symbols into existing host-drawing definitions.
  3. Use the Overlay attachment type, which limits nested xref display but does not incorporate xref content into a single DWG file.
  4. Use Detach, which removes the reference definition and its associated geometry from the host drawing entirely.
Explanation: Whenever you see a question about combining xref files into a single DWG while preserving layer identity, focus on how AutoCAD handles name conflicts between host and xref symbols during binding. When you bind an xref using the Bind method (answer A), AutoCAD converts all xref-dependent layer names using a qualified naming convention. A layer originally called WALL inside the xref becomes XREFNAME$0$WALL in the host drawing. This means the host's WALL layer and the xref's WALL layer coexist as distinctly named definitions — exactly what the regulatory archive requires. Bind is the correct choice here. Answer B describes the Insert method, which is the critical trap in this question. Insert does incorporate the xref into a single DWG, but it merges identically named symbols — so the xref's WALL layer collapses into the host's WALL layer, destroying the distinction the archive must preserve. This is the most common mistake students make when comparing Bind and Insert. Answer C describes the Overlay attachment type, which is a setting applied when attaching an xref, not when binding it. Overlays also remain as live references — they do not consolidate content into one file — so this fails the "single DWG" requirement entirely. Answer D describes Detach, which actually removes the xref and its geometry from the drawing. This is the opposite of archiving content. Your study tip: memorize the Bind vs. Insert distinction as a pair — Bind = qualified names preserved, Insert = names merged. Exam questions almost always test exactly this contrast.

Question 10

A project drawing contains four external references. Three show a status of Loaded, while survey.dwg shows Not Found because its source folder was renamed. The designer creates an eTransmit ZIP file without correcting the reference.

Which action should the designer take to ensure that the recipient receives a functional survey.dwg reference?

  1. Copy survey.dwg beside the completed ZIP file without changing the reference path in the host drawing.
  2. Locate and repath survey.dwg, reload it successfully, and then create and review a new transmittal package. (correct answer)
  3. Unload survey.dwg before recreating the package so eTransmit treats the reference as an optional dependency.
  4. Bind the three loaded references and assume eTransmit will reconstruct the unresolved reference from cached graphics.
Explanation: When working with external references in AutoCAD, think of eTransmit as a packaging tool that can only bundle files it can actually find. If a reference shows Not Found, eTransmit has nothing to grab — it cannot locate, copy, or transmit a missing file, regardless of any cached display data. The correct path forward is B: locate the renamed folder, update the reference path in the External References palette, confirm the status changes to Loaded, and then regenerate the transmittal. Only at that point does eTransmit have a resolved file to include. Reviewing the transmittal report afterward confirms survey.dwg was actually packaged — closing the loop before the file leaves your hands. A is a manual workaround that fails for two reasons: the recipient's host drawing still contains the old, broken path, so AutoCAD on their machine won't find survey.dwg even if it sits in the same folder. Path mismatches must be fixed inside the drawing, not patched around externally. C is a trap. Unloading a reference doesn't make eTransmit treat it more generously — it simply suppresses the display. An unloaded xref is still a dependency, and a Not Found unloaded reference remains unresolvable for the recipient. D is a dangerous misconception. Binding resolves loaded references by merging them into the host drawing, but it does nothing for an unresolved one. eTransmit cannot reconstruct geometry from cached graphics — there is no such mechanism in AutoCAD. Study tip: On AutoCAD exam questions involving eTransmit, always check reference status first. Any xref that isn't Loaded must be resolved before packaging — everything else is just guesswork.