AutoCAD Quiz: Exporting To Alternate Formats
10 questions · exam conditions
0:00
Exporting To Alternate FormatsQuestion 1 of 10

A supplier must edit a mechanical enclosure in a different solid-modeling application. The supplier requests a neutral file that is most likely to retain the enclosure as a connected solid rather than as a collection of independent surface patches. The supplier accepts both STEP and IGES.

Which export approach is most appropriate?

Export to STEP and verify that the receiving application imports the result as a solid body.
Export to IGES and assume that all transferred surfaces will automatically form a valid solid.
Export to ACIS SAT and rename the resulting file with a STEP file extension.
Plot the model to PDF and enable vector output so the geometry remains editable.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Exporting To Alternate Formats

Practice Exporting To Alternate Formats 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 Exporting To Alternate Formats, 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 supplier must edit a mechanical enclosure in a different solid-modeling application. The supplier requests a neutral file that is most likely to retain the enclosure as a connected solid rather than as a collection of independent surface patches. The supplier accepts both STEP and IGES.

Which export approach is most appropriate?

  1. Export to STEP and verify that the receiving application imports the result as a solid body. (correct answer)
  2. Export to IGES and assume that all transferred surfaces will automatically form a valid solid.
  3. Export to ACIS SAT and rename the resulting file with a STEP file extension.
  4. Plot the model to PDF and enable vector output so the geometry remains editable.
Explanation: When transferring solid geometry between CAD applications, your primary concern is whether the receiving system will interpret the file as a unified solid body or as a loose collection of surfaces. STEP (ISO 10303) was specifically designed with robust solid-model topology in mind, using manifold solid B-rep definitions that explicitly encode volume and connectivity. IGES, while widely supported, is older and more surface-patch oriented — it can carry solid intent, but gaps, tolerance mismatches, and missing topology data frequently cause the receiving application to reconstruct a "quilt" of surfaces rather than a true solid. Option A is the right approach because STEP gives the supplier the best chance of receiving a connected solid, and the verification step is critical — you should never assume a neutral file transferred cleanly without confirming the result in the target application. That confirmation step is what separates a professional workflow from a hopeful one. Option B is dangerous precisely because of that word "assume." IGES transfers require careful tolerance and entity-type settings, and auto-healing into a valid solid is far from guaranteed. Blind assumption is the trap this distractor is designed to set. Option C is outright deceptive. Renaming an ACIS SAT file with a STEP extension does not convert the file format — the internal data structure remains SAT, and any application expecting true STEP will either reject it or misread it entirely. File extensions are labels, not format converters. Option D replaces editable 3D geometry with a 2D document. A PDF plot preserves appearance, not solid topology, making it useless for solid-modeling work. Your study tip: on file-exchange questions, always consider format intent (surface vs. solid) and never skip validation of the received result.

Question 2

A drawing contains three ACIS-based 3D solids, dimensions in paper space, and two raster references. A downstream application using an ACIS-compatible modeler needs only two of the solids.

Which workflow best limits the delivered SAT file to the required model geometry?

  1. Run ACISOUT and explicitly select only the two required 3D solids when prompted. (correct answer)
  2. Plot the current layout to SAT and freeze the viewport layers containing the unwanted information.
  3. Run ACISOUT with no object selection so AutoCAD exports every visible paper-space object.
  4. Bind the raster references and dimensions, then include them with the selected solids in ACISOUT.
Explanation: When working with ACIS-based workflows in AutoCAD, the key question to ask yourself is: what does the destination application actually need, and how precisely can I control what gets exported? The ACISOUT command exports 3D solid geometry to the SAT format, which is the standard interchange format for ACIS-compatible modelers. The cleanest solution here is A — running ACISOUT and manually selecting only the two required solids at the selection prompt. This gives you surgical precision: only the explicitly selected objects are written to the SAT file. SAT is a solid-geometry format, so dimensions and raster references cannot be meaningfully included anyway, but selecting only your target solids ensures a clean, unambiguous file for the downstream application. B is wrong because ACISOUT is not a plot operation — you cannot "plot to SAT." Freezing viewport layers controls visual display, not export content. This confuses plotting workflows with geometry export workflows. C is wrong because running ACISOUT with no selection doesn't export "everything visible" in a useful way — more importantly, it would include the unwanted third solid, which defeats the entire purpose. You always want to be intentional about selection when exporting to SAT. D is wrong on two levels: binding raster references and dimensions does nothing to prepare them for SAT export, and including non-solid objects in an ACISOUT selection would either cause errors or be ignored — neither outcome helps. As a study tip, remember that ACISOUT respects explicit object selection, so whenever a question asks about limiting SAT export content, controlling the selection set is always your primary tool.

Question 3

A user follows instructions written for another AutoCAD product and cannot find a STEP or IGES export option in the installed version. ACIS SAT export is available. The delivery deadline is later that day.

What is the most appropriate next step?

  1. Export a layout to PDF because any vector output can be opened as an equivalent solid model.
  2. Rename a SAT file with the requested extension because neutral CAD formats differ only by file-name extension.
  3. Reinstall the plotter driver because STEP and IGES export options are supplied by Windows printing services.
  4. Confirm the installed release, product, and toolset support before choosing an available translator or approved conversion workflow. (correct answer)
Explanation: When troubleshooting missing export options in AutoCAD, the most important skill is diagnosing the root cause before acting — especially under deadline pressure, when the temptation to grab any quick fix is strongest. The scenario describes a version mismatch: instructions written for one AutoCAD product don't apply to the installed version. AutoCAD's full product family includes AutoCAD LT, AutoCAD for Mac, vertical toolsets (like AutoCAD Mechanical or Electrical), and the full desktop release — each with different translator support. STEP and IGES export, for example, are only available in specific releases and toolsets. The correct move is D: confirm exactly which product, release, and toolset is installed, then either use a supported translator that is available or follow an approved conversion workflow (such as using the available SAT export and converting through a capable intermediary tool). Choice A is wrong because PDF is a 2D page-description format — it cannot represent a solid model, and no CAD application treats PDF as equivalent to STEP or IGES geometry. Choice B reflects a dangerous misconception: STEP (.stp/.step), IGES (.igs/.iges), and ACIS SAT (.sat) are entirely different data formats with distinct geometry kernels and structures. Simply renaming the file extension does not change the underlying data, and the receiving application will either reject it or misread it. Choice C is wrong because CAD translators are part of the AutoCAD application itself, not the Windows print/plotter driver subsystem. Reinstalling plotter drivers has no effect on geometry export capabilities. Your study tip: on AutoCAD exam questions involving missing features, always check product, release, and toolset first — many features are version- or toolset-specific, not universal across the AutoCAD family.

Question 4

A current AutoCAD installation exports a SAT file successfully, but the recipient's older ACIS-based application reports that the SAT version is unsupported. The recipient confirms that the geometry type itself is acceptable.

Which action most directly addresses the compatibility problem?

  1. Reduce the layout plot resolution, publish again, and use the resulting output as the replacement SAT file.
  2. Increase the drawing's visual-style quality, export again, and ask the recipient to enable smooth shading.
  3. Change the SAT file extension to IGES so the older application invokes a different geometry reader.
  4. Set ACISOUTVER to a SAT version supported by the recipient, export again, and test the new file. (correct answer)
Explanation: When AutoCAD exports a SAT file, the version of the ACIS geometry format embedded in that file is controlled by the system variable ACISOUTVER. Older ACIS-based applications were built against earlier SAT specifications and cannot parse headers or data structures introduced in later versions — so even if the geometry itself is valid, a version mismatch causes the import to fail. This question tests whether you know which lever to pull when the problem is specifically a version incompatibility, not a geometry or display issue. Setting ACISOUTVER to a SAT version the recipient's application supports, re-exporting, and testing the result directly resolves the stated problem. The recipient already confirmed the geometry type is acceptable, so the only obstacle is the version number embedded in the file. D addresses exactly that. Choice A confuses plot resolution — a 2D output setting for paper layouts — with 3D solid export. Plot resolution has no bearing on SAT file version or ACIS compatibility. Choice B introduces visual-style quality, which affects on-screen rendering and shading display in AutoCAD, not the underlying ACIS data format written to a SAT file. Asking the recipient to enable smooth shading solves nothing if the file can't even be opened. Choice C is a common misconception: renaming a file's extension does not change its internal format or invoke a different parser in a meaningful, reliable way. The older application will still read (or fail to read) the same binary/text ACIS data regardless of the extension label. For the exam, remember that ACISOUTVER is your go-to variable for SAT export compatibility — whenever you see a version mismatch with ACIS-based applications, that's the first setting to check.

Question 5

A drawing contains a finished assembly, construction solids, and duplicate components on several model-space layers. The engineer must export only the released components to STEP. The translator supports selection of objects but does not use plot-area settings.

Which workflow provides the most reliable control over the exported contents?

  1. Make the released components visually shaded, leave construction solids in wireframe, and export all model objects.
  2. Set the layout plot area to Window, export the entire drawing, and assume the plot window limits STEP data.
  3. Isolate or otherwise identify the released components, explicitly select them for export, and verify the exported file. (correct answer)
  4. Move the released components behind a paper-space viewport, lock the viewport, and export the current layout.
Explanation: When exporting geometry from AutoCAD to a format like STEP, the critical principle is that the translator controls what gets exported, not visual or layout settings. The passage explicitly tells you the translator supports object selection but ignores plot-area settings — that one detail eliminates two of the four choices immediately. The most reliable workflow is C: isolate or explicitly select the released components, pass that selection directly to the STEP exporter, and then verify the output file. This gives you direct, intentional control over exactly which objects are included. Verification closes the loop by confirming the exported file contains what you intended — nothing more, nothing less. A is wrong because shading versus wireframe is a display property only. It has no effect on which objects a STEP translator exports; the translator will still capture all model geometry regardless of visual style. B is a classic trap: plot-area settings like a Window selection govern what gets printed or plotted, not what gets exported via a file translator. The passage directly states the translator does not use plot-area settings, making this approach entirely unreliable. D is similarly flawed. Paper-space viewports and locked viewport states are layout presentation tools. A model-space STEP export doesn't honor viewport visibility or positioning — the translator reads model-space objects directly. A useful pattern to remember: whenever an AutoCAD export question mentions a third-party translator (STEP, IGES, SAT), always ask yourself whether the method of control actually communicates with that translator. Visual styles, plot windows, and viewport locks do not — explicit object selection does.

Question 6

A manufacturer asks for a STEP file but also wants to revise individual fillets using the exact feature parameters and feature order used by the AutoCAD author. The author intends to archive only the exported file.

Which response best addresses the manufacturer's request?

  1. Deliver STEP for geometric exchange and retain the source DWG because neutral export may not preserve feature history. (correct answer)
  2. Deliver STEP alone because it necessarily stores every native command and feature parameter from the DWG.
  3. Deliver IGES alone because surface exchange always retains a fully editable parametric feature tree.
  4. Deliver SAT alone because an ACIS file necessarily includes the complete AutoCAD editing history and layouts.
Explanation: Whenever you see a question combining file exchange formats with parametric editing requirements, you need to think about two separate concerns: geometry transfer and feature history. These are not the same thing, and confusing them is exactly the trap this question sets. Neutral exchange formats like STEP, IGES, and SAT are designed for interoperability — they package geometry in a way different software can read. However, they capture the final shape, not the sequence of design decisions (feature trees, fillet parameters, sketch constraints) that produced it. That history lives in the native file. So when the manufacturer wants to revise specific fillets by their original parameters and order, they need access to the source DWG, not just the exported geometry. Answer A correctly recognizes both needs: deliver the STEP file for geometric exchange, and retain the source DWG because parametric feature history does not survive neutral export. Answer B is wrong because it makes a false claim — STEP does not "necessarily" store native commands or feature parameters. It stores boundary representation geometry, not design intent. Answer C is similarly wrong on two counts: IGES is a surface/wireframe exchange format, and no neutral format guarantees a fully editable parametric feature tree. Answer D fails for the same reason — SAT (ACIS format) stores solid geometry but does not carry AutoCAD's editing history or layout structures. The study tip here: on exam questions about file formats, always separate what the format transfers (geometry) from what it cannot transfer (parametric history, feature order, native intent). If a question mentions editing original features, the native file must be involved.

Question 7

A drawing contains a closed planar polyline representing a gasket outline. The recipient asks for an ACIS planar face that can participate in geometric operations, not merely a collection of line and arc entities.

Which preparation and export sequence best satisfies the request?

  1. Place the polyline inside a paper-space viewport, then export the viewport boundary with ACISOUT.
  2. Increase the polyline width, then publish the active layout to a high-resolution vector PDF.
  3. Convert the closed polyline to a region, then export the supported region geometry with ACISOUT. (correct answer)
  4. Explode the polyline into segments, then export the separate line and arc entities as a SAT face.
Explanation: When working with solid modeling and interoperability in AutoCAD, you need to recognize the distinction between drafting geometry (lines, arcs, polylines) and ACIS geometry (regions, solids) that supports true geometric operations like Boolean unions, intersections, and area calculations. The command ACISOUT exports geometry in the SAT (Standard ACIS Text) format — but it only works with ACIS-based objects: regions and 3D solids. A raw polyline, no matter how it's drawn, is simply a drafting entity with no volumetric or planar-face representation in the ACIS kernel. The correct preparation step is REGION, which converts a closed, planar polyline into a true ACIS planar face. Once converted, ACISOUT can export that region as a proper SAT file the recipient can use in geometric operations. That makes C the correct sequence. A is wrong because placing a polyline in a paper-space viewport doesn't change its object type — it's still a polyline, and ACISOUT cannot export viewport boundaries or polylines as ACIS faces. B is wrong on two counts: increasing polyline width only affects display thickness, not object type, and publishing to PDF produces a raster or vector print output, not an ACIS/SAT file for geometric computation. D is wrong because exploding a polyline produces individual lines and arcs — which moves you further from a unified ACIS face, not closer. ACISOUT cannot export lines or arcs as SAT faces regardless. Remember this workflow: closed polyline → REGION → ACISOUT. Anytime a question asks about exporting for geometric interoperability, your first instinct should be to check whether the geometry has been promoted to an ACIS object first.

Question 8

A part is modeled at the correct real-world size in AutoCAD. After neutral-format exchange, the recipient reports that the part is uniformly scaled by a large factor. No individual features are distorted.

What is the best corrective workflow before sending another file?

  1. Increase tessellation quality before export because coarse faceting causes uniform unit-scale errors in solid models.
  2. Confirm source drawing units and target import units, then test a known dimension after re-export and re-import. (correct answer)
  3. Change the active layout's paper size because neutral model dimensions are derived from the plotted sheet size.
  4. Explode the part before export because separate faces automatically adopt the recipient's preferred measurement system.
Explanation: Whenever you see a question about file exchange errors in AutoCAD, think first about unit mismatches — they are by far the most common cause of uniform scaling problems during neutral-format (STEP, IGES, SAT, etc.) transfers. A uniform scale error means every dimension is off by the same factor, which tells you no geometry was distorted; only the measurement system was misinterpreted. Choice B is correct because it targets the actual root cause. Different CAD systems may assume millimeters, inches, or meters when importing a neutral file. If your drawing is in inches and the recipient's system imports assuming millimeters, every dimension becomes 25.4× too large. The fix is to verify that your source units match what the target software expects, then validate by measuring a known dimension after re-export and re-import before sending. This systematic check-and-confirm workflow catches the problem without guesswork. Choice A is a distractor that confuses tessellation quality — which controls how smoothly curved surfaces are faceted for visualization or mesh export — with unit scaling. Coarse faceting affects surface smoothness, not overall size. Choice C is wrong because neutral-format model data is stored in model space coordinates, completely independent of any paper/layout sheet size you configure for plotting. Sheet size has no bearing on exported geometry dimensions. Choice D is wrong because exploding a solid into individual faces does nothing to resolve a unit mismatch; the faces still carry the same coordinate values in the same unit system. As a study tip, remember this pattern: uniform scale error → suspect units; non-uniform distortion → suspect geometry or export settings. Keeping those two failure modes distinct will help you quickly eliminate distractors on similar questions.

Question 9

A STEP export command completes without reporting an error. The file must be sent to a machining vendor, and failure to preserve one through-hole would make the model unusable.

Which verification method gives the strongest evidence that the export is suitable for delivery?

  1. Confirm that the STEP file has a nonzero size and that its file name matches the drawing name, then send it to the vendor.
  2. Import the STEP file into a test drawing or target-compatible viewer and check solid status, dimensions, and the through-hole. (correct answer)
  3. Open the original layout in plot preview, confirm the through-hole appears in the shaded viewport, and treat that as export confirmation.
  4. Check that the original DWG saves without errors and assume the neutral translator produced geometry identical to the source model.
Explanation: When working with STEP exports in AutoCAD, you're dealing with neutral file format translation — a process that converts proprietary DWG geometry into a universal format. The critical concept here is that a successful export command only confirms the process completed, not that the resulting geometry is accurate or complete. Always ask yourself: "Have I verified the output independently of the source?" The strongest verification is B because it closes the loop entirely. Importing the STEP file into a separate viewer or test drawing lets you inspect the actual translated geometry — confirming the solid is intact, dimensions match, and crucially, that the through-hole survived translation. This mirrors what the vendor's machining software will see, making it a direct, evidence-based check. Choice A is dangerously shallow. File size and naming conventions tell you nothing about geometric integrity — a STEP file can be nonzero in size while containing a broken solid or missing features. Choice C is a common trap: the plot preview reflects the original DWG viewport, not the exported STEP. You're essentially just verifying the source file looks correct, which was never in question. Choice D compounds two logical errors — a clean DWG save only confirms the native file is healthy, and assuming the neutral translator produced identical geometry is exactly the kind of assumption that causes costly machining failures. Translators can drop features, misinterpret topology, or corrupt solids silently. Study tip: On export-related questions, remember that "no error" means the process ran — it never guarantees output fidelity. Always verify the destination file, not the source.

Question 10

An industrial designer created a set of trimmed freeform surfaces. The recipient's legacy application cannot import STEP or SAT but can import IGES. The recipient expects to continue surface modeling and does not require the file to arrive as a watertight solid.

What should the designer do before delivering the model?

  1. Export the selected surfaces to IGES, then perform a test import to check trimming and surface continuity. (correct answer)
  2. Convert the surfaces into layout viewports, then export the paper-space layout as an IGES model.
  3. Export the surfaces to ACIS SAT, then change the file extension so the legacy importer accepts it.
  4. Publish the surfaces to a vector PDF, then ask the recipient to recover the original NURBS geometry.
Explanation: When delivering surface models to a recipient with a constrained legacy application, your job is to match the output format to what the receiver can actually use — and then verify the handoff didn't corrupt the geometry. That combination of format selection and quality assurance is exactly what this question tests. IGES (Initial Graphics Exchange Specification) is the correct format here because the recipient explicitly cannot accept STEP or SAT and needs continued surface modeling — not a solid. IGES natively supports NURBS and trimmed surfaces without requiring a watertight boundary representation. Critically, answer A goes one step further: it includes a test import to verify that trimming boundaries and surface continuity survived the translation. IGES translators are notoriously imperfect, and trimmed surfaces are especially vulnerable to losing their trim curves or developing gaps during export. A test import catches these problems before delivery. Answer B is nonsensical for 3D delivery — layout viewports exist in paper space for 2D plotting purposes. You cannot reconstruct a surface model from a paper-space IGES export; it would contain flat 2D projection data at best. Answer C is dangerously wrong: renaming a SAT file does not change its internal binary or ASCII structure. The legacy importer will still reject it or, worse, misread it and produce corrupt geometry. File format compatibility is determined by file content, not the extension. Answer D fails because PDF is a display and print format — it does not preserve parametric NURBS data. There is no meaningful way to "recover" original surface geometry from a vector PDF. Remember: format compatibility questions on AutoCAD exams often test whether you know why a format works, not just its name. Always pair export decisions with a verification step.