Autodesk Fusion 360 Quiz: Export Import Troubleshooting
10 questions · exam conditions
0:00
Export Import TroubleshootingQuestion 1 of 10

A bracket was modeled in Fusion with a width of 2 in2\text{ in}. After it is exported as an STL file and opened by a fabrication vendor, the vendor reports a width of 2 mm2\text{ mm}. The bracket is otherwise geometrically correct.

Which action most directly resolves the problem while preserving the intended physical size?

Re-export with finer tessellation so the STL records the original inch dimensions more accurately.
Have the vendor interpret the unitless STL coordinates as inches, or apply a scale factor of 25.425.4 to the imported geometry.
Convert the solid to a surface body before export so its document units remain embedded in the file.
Have the vendor interpret the STL coordinates as centimeters, then uniformly scale the result by 2.542.54.
← Back to quizzes

Autodesk Fusion 360 Quiz

Autodesk Fusion 360 Quiz: Export Import Troubleshooting

Practice Export Import Troubleshooting in Autodesk Fusion 360 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 Export Import Troubleshooting, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Fusion 360.

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 bracket was modeled in Fusion with a width of 2 in2\text{ in}. After it is exported as an STL file and opened by a fabrication vendor, the vendor reports a width of 2 mm2\text{ mm}. The bracket is otherwise geometrically correct.

Which action most directly resolves the problem while preserving the intended physical size?

  1. Re-export with finer tessellation so the STL records the original inch dimensions more accurately.
  2. Have the vendor interpret the unitless STL coordinates as inches, or apply a scale factor of 25.425.4 to the imported geometry. (correct answer)
  3. Convert the solid to a surface body before export so its document units remain embedded in the file.
  4. Have the vendor interpret the STL coordinates as centimeters, then uniformly scale the result by 2.542.54.
Explanation: Whenever you see a question about file format compatibility across CAD tools, focus on what data the file format actually stores — not what it displays. STL files are unitless: they record raw coordinate values as floating-point numbers with no embedded unit label. A coordinate of 2.0 could mean 2 inches, 2 millimeters, or 2 furlongs — the file itself doesn't say. Here's what happened: Fusion 360 exported the bracket with a coordinate value of 2.0 representing 2 inches. The vendor's software assumed those coordinates were in millimeters (a common default), so it rendered the part as 2 mm wide. The geometry is correct; only the unit interpretation is wrong. B is correct because it addresses the root cause directly. Either the vendor reinterprets the raw 2.0 coordinate as inches, or they apply a scale factor of 25.425.4 (since 1 in=25.4 mm1 \text{ in} = 25.4 \text{ mm}), scaling the 2 mm result up to the intended 50.8 mm — which equals exactly 2 inches. Both paths restore the correct physical size. A is wrong because tessellation quality controls triangle density and surface smoothness, not unit encoding. Finer tessellation cannot embed inch information into a unitless format. C is wrong because surface bodies have no special unit-embedding capability. STL files derived from surface or solid bodies are equally unitless. D is wrong because the coordinates are being misread as millimeters, not centimeters. Scaling by 2.542.54 would only correct a centimeter misinterpretation, leaving the result still 10×10\times too small. Study tip: On Fusion 360 questions, remember that STL = unitless coordinates. Unit mismatches are always an interpretation problem, solved by rescaling or re-importing with the correct unit assumption — not by changing geometry or export settings.

Question 2

A machined housing contains a smooth cylindrical bore. The bore is smooth when inspected in Fusion, but the exported STL shows visible flat facets in both a slicer and a mesh viewer. The measured bore diameter is still correct.

What is the most appropriate first correction?

  1. Reduce the mesh refinement so fewer triangles are generated around the cylindrical bore.
  2. Increase mesh refinement by tightening deviation and angular tolerances during mesh export. (correct answer)
  3. Increase the design's display quality because viewport faceting controls exported mesh density.
  4. Export the body in larger document units because small units create planar cylindrical faces.
Explanation: When you export geometry from Fusion 360 as an STL, the software converts smooth parametric surfaces into a triangulated mesh. The key insight here is that STL quality is controlled at export time through tolerance settings, not by how the model looks in the viewport. Two critical parameters govern this: deviation tolerance (how far a triangle edge can stray from the true surface) and angular tolerance (the maximum angle between adjacent triangle normals). Tightening either value forces Fusion to generate more, smaller triangles that hug the curved surface more closely — eliminating visible facets on cylindrical bores. Answer B is correct because increasing mesh refinement by tightening these tolerances directly addresses the root cause: the triangles approximating the bore are too large and angular, producing flat-faced artifacts in downstream tools. Answer A describes the opposite action — reducing refinement generates fewer triangles, which would make the faceting worse, not better. This is a classic reversal trap. Answer C is tempting but wrong because Fusion's viewport display quality is a visual rendering setting only. It controls how smooth geometry looks on your screen during modeling but has absolutely no effect on the tolerance values written into an exported STL file. These are independent systems. Answer D is a misconception about units. Document units affect scale and measurement, not how curved surfaces are tessellated. Small units don't cause planar faces; insufficient angular/deviation tolerance does. A useful rule of thumb: if faceting appears in an exported mesh but not in the Fusion viewport, always look to export settings first — the model geometry itself is fine.

Question 3

A designer exports a fully parametric Fusion part as STEP. A coworker imports the STEP file into a new design and obtains an accurate solid body, but the original sketches, constraints, and feature-by-feature timeline are absent.

Which conclusion and corrective workflow are most appropriate?

  1. The STEP file is damaged; increasing STEP export precision should reconstruct the original timeline.
  2. The import units are incorrect; matching document units should restore sketches and constraints.
  3. This is expected for STEP; share a Fusion archive or native design when editable history is required. (correct answer)
  4. The body was exported at coarse tessellation; using a refined mesh should preserve feature history.
Explanation: When working with file formats in Fusion 360, the critical concept is understanding what each format actually stores. STEP (.stp) is a geometry exchange format — it captures precise boundary representation (B-rep) solid geometry, but it is fundamentally a neutral, non-parametric format. It has no mechanism to encode sketches, parametric constraints, or a feature timeline, because those constructs are specific to Fusion 360's internal data model. This makes C the correct conclusion and workflow. The missing history isn't a bug or error — it's an inherent characteristic of the STEP format. When editable feature history is required, you should share a Fusion archive file (.f3d or .f3z) or grant the coworker access to the native cloud design, both of which preserve the full parametric timeline. Each distractor reflects a different misconception worth understanding. A suggests that export precision controls timeline reconstruction — but STEP precision settings only affect the mathematical tolerance of surface representation, not parametric data, which simply doesn't exist in the format. B implies unit mismatch causes the missing history — but units affect scaling, not whether sketches and constraints are present; they were never included in the STEP file to begin with. D confuses STEP with mesh formats like STL or OBJ — tessellation and mesh density are irrelevant here because STEP stores exact B-rep geometry, not a triangle mesh, and neither affects feature history. As a study tip, remember that file format questions in Fusion 360 often hinge on the distinction between geometry fidelity (what shape data is captured) and parametric fidelity (whether design intent and history survive). Neutral formats like STEP, IGES, and STL always sacrifice the latter.

Question 4

A supplier sends a DXF profile that should measure 100 mm100\text{ mm} across. After it is inserted into a Fusion sketch, it measures approximately 3.937 mm3.937\text{ mm}. The profile shape and proportions are otherwise correct.

Which diagnosis best explains the result, and what is the preferred correction?

  1. The DXF was interpreted as inches and converted twice; reinsert it using millimeters as the source unit.
  2. The DXF was interpreted as millimeters instead of inches; reinsert it using inches as the source unit. (correct answer)
  3. The DXF spline tolerance is too coarse; reduce the tolerance until the width reaches 100 mm100\text{ mm}.
  4. The sketch plane is incorrectly oriented; rotate it by 90∘90^\circ to restore the intended width.
Explanation: When working with imported DXF files in Fusion 360, unit mismatches are one of the most common scaling problems you'll encounter. The key diagnostic clue here is the ratio between the expected and observed dimensions: 3.937100≈0.03937\frac{3.937}{100} \approx 0.03937, which is precisely the conversion factor for millimeters to inches (1 inch=25.4 mm1\text{ inch} = 25.4\text{ mm}, so 125.4≈0.03937\frac{1}{25.4} \approx 0.03937). This tells you Fusion read the file's inch-based values as if they were millimeters, making everything appear about 25.4 times too small. The correct fix, as answer B describes, is to reinsert the DXF and specify inches as the source unit. Fusion will then multiply each coordinate by 25.4 during import, restoring the geometry to its intended 100 mm100\text{ mm} size. Answer A is a trap — it describes a double conversion scenario, which would produce a dramatically different (and much larger) error, not the precise 1-in-25.4 ratio you observed. Answer C conflates spline tolerance with geometric scale; tolerance controls curve smoothness and deviation, not overall dimensions — adjusting it cannot resize the profile. Answer D misidentifies the problem as an orientation issue; rotating the sketch plane would change which axes the geometry projects onto, but the measured width would remain unchanged at 3.937 mm3.937\text{ mm}. As a study tip, whenever you see a scaling discrepancy in Fusion 360 that's close to a factor of 25.4 (or its reciprocal), immediately suspect an inches/millimeters unit mismatch during DXF import — it's almost always the culprit.

Question 5

A prototype model exports as a 240 MB240\text{ MB} STL and causes long processing times in the slicer. Inspection shows that large planar faces contain many triangles, while only two small fillets require a smooth approximation.

Which adjustment offers the best balance between file size and retained shape quality?

  1. Use a coarser or custom mesh tolerance, then verify that the small fillets remain within acceptable deviation. (correct answer)
  2. Use the highest mesh refinement globally so the slicer can automatically merge redundant planar triangles and reduce file size.
  3. Increase the model's physical scale before export so that fewer triangles are required per unit of length.
  4. Convert all planar faces to spline surfaces so the STL exporter generates fewer triangles for those regions.
Explanation: When troubleshooting bloated STL files in Fusion 360, you need to think about where mesh density is actually necessary. STL files approximate curved surfaces with triangles, so the key question is: which regions truly need fine triangulation, and which don't? Large planar faces are geometrically flat — they need only two triangles each to represent them perfectly, regardless of area. When you see hundreds of triangles covering a flat surface, that's wasted data. Small fillets and curves, however, genuinely require denser triangulation to stay within acceptable shape deviation. This distinction is exactly what answer A exploits. By applying a coarser or custom mesh tolerance globally and then verifying that the two small fillets remain within acceptable deviation, you dramatically reduce triangle count on the flat regions while confirming the curved features still look correct. This targeted approach is the best balance of file size and shape fidelity. Answer B is fundamentally backwards — slicers do not automatically merge redundant triangles. Exporting at maximum refinement makes the file larger, not smaller, and no automatic cleanup occurs downstream. Answer C is a misconception: scaling the model changes its physical size but doesn't reduce triangle count per feature; the slicer still processes the same geometry. Answer D reveals a misunderstanding of how STL works — the format only stores triangular mesh data. Converting faces to splines in the CAD model has no effect on STL output, since the exporter still tessellates everything into triangles regardless of the underlying surface type. As a study tip, remember that STL optimization is always about matching triangle density to geometric need — flat regions need almost none, curves need more. Let that principle guide any mesh tolerance question.

Question 6

A STEP file imported into Fusion appears at the correct size, but one region is listed as several surface bodies instead of a closed solid. Edge inspection indicates small translation gaps between otherwise adjacent faces.

What is the most appropriate troubleshooting sequence?

  1. Stitch the related surfaces using the smallest tolerance that closes valid gaps, then verify that a solid results. (correct answer)
  2. Scale the surfaces slightly larger until they overlap, then combine them into a new component.
  3. Convert the surfaces to a coarse mesh, smooth the mesh, and convert it back to a solid.
  4. Apply an unrestricted stitch tolerance so all nearby edges merge regardless of geometric mismatch.
Explanation: When you import STEP files into Fusion 360, translation gaps between adjacent faces are a common artifact of the conversion process. These gaps prevent Fusion from recognizing the region as a closed solid, leaving you with disconnected surface bodies instead. The right mental model here is: diagnose the gap → close it minimally → confirm solid integrity. The correct approach, A, uses the Stitch tool with the smallest tolerance that successfully closes the gaps. This is precise and reversible — you're bridging only legitimate translation gaps without distorting geometry. After stitching, Fusion validates whether the result is a watertight solid, giving you immediate confirmation the repair worked. B is flawed because scaling surfaces to force overlap introduces geometric inaccuracies across the entire body — you're not fixing the gap, you're warping the design. Combine operations won't fix underlying topological mismatches either. C converts to a mesh unnecessarily. Mesh workflows are appropriate for organic sculpting or scan data, not for repairing precise STEP geometry. You'd lose dimensional accuracy and parametric editability in the process. D is the most dangerous option. Applying an unrestricted stitch tolerance merges edges that may not actually belong together, potentially collapsing faces, bridging distant unrelated edges, or producing invalid geometry that looks closed but fails downstream operations like simulation or CAM. Study tip: On Fusion 360 exam questions involving imported geometry repair, always favor the most conservative, geometry-preserving fix first. If a question mentions "gaps" between surfaces, Stitch with minimal tolerance is almost always the correct starting point — avoid any option that forces or approximates geometry rather than closing actual gaps.

Question 7

A designer adds an embossed part number and two chamfers near the end of a Fusion timeline. The Fusion canvas previously showed those details, but immediately before export the timeline marker was moved backward to inspect an earlier state. The exported mesh contains the main body but not the emboss or chamfers.

What should the designer do before changing mesh-quality settings?

  1. Convert the current rolled-back body to a B-rep so later timeline features become included.
  2. Increase tessellation refinement because coarse meshes always omit the final timeline features entirely.
  3. Change the export units because mismatched units selectively suppress small downstream features.
  4. Move the timeline marker to the end, recompute the design, confirm the details, and export again. (correct answer)
Explanation: Whenever you see a question about missing features in a Fusion 360 export, your first instinct should be to check the timeline marker position before assuming any setting is broken. Fusion 360's parametric timeline controls exactly which features are computed and visible — rolling the marker backward suppresses everything downstream of it, intentionally showing an earlier design state. In this scenario, the emboss and chamfers are absent not because of any export flaw, but because the timeline marker was moved backward to inspect an earlier state and never returned. The correct fix — answer D — is to drag the marker back to the end of the timeline, allow Fusion to recompute all features, visually confirm the emboss and chamfers appear on the canvas, and then export. This resolves the root cause directly. Answer A is a trap because converting a rolled-back body to a B-rep would simply bake in the incomplete geometry — it doesn't restore suppressed downstream features, it permanently discards them. Answer B misunderstands tessellation: mesh refinement controls surface smoothness and polygon density, not which timeline features are included in the geometry. A coarse mesh of a complete body still includes all features. Answer C is similarly off-base — unit mismatches affect scale, not feature suppression. Small features won't silently disappear just because export units differ. The key study tip here: always verify the timeline marker is at the end before troubleshooting an export. In Fusion 360, a rolled-back timeline is the most common and overlooked cause of "missing" geometry, and fixing it costs nothing before diving into complex setting changes.

Question 8

An assembly contains several native Fusion solid components and one component imported earlier as a mesh body. When the assembly is exported to STEP and opened in another CAD application, all native solid components appear, but the mesh-only component is missing.

Which workflow most directly addresses the missing component?

  1. Refine the mesh display, then export STEP again with the same mesh-only component structure.
  2. Change the assembly document units to match the mesh units, then repeat the STEP export.
  3. Convert or remodel the mesh as a suitable B-rep body, then repeat the STEP export. (correct answer)
  4. Suppress every native solid component so STEP exports only the remaining mesh component.
Explanation: Whenever you see a question about file format compatibility in Fusion 360, focus on what data types each format can actually carry. STEP is a boundary representation (B-rep) exchange format — it encodes geometry as mathematically defined surfaces and solids. Mesh bodies, by contrast, are collections of triangular facets with no B-rep definition, and STEP simply has no container for that data structure. This is why the mesh component silently disappears during export. The fix, as answer C correctly identifies, is to convert the mesh into a proper B-rep body before exporting. In Fusion 360, you can do this using the Mesh workspace tools — either by using "Convert Mesh" to create a solid/surface body (for simpler geometry) or by remodeling the component using the mesh as a reference. Once the body exists as a B-rep, STEP can carry it faithfully into any receiving CAD application. Answer A is a trap: refining mesh display only changes visual tessellation quality on screen. It does nothing to change the underlying data type, so the export problem remains. Answer B confuses unit scaling with format compatibility — mismatched units might cause size errors, but they don't explain a component going missing entirely; the issue is data type, not scale. Answer D works backwards entirely: suppressing the native solids would export nothing useful, and the mesh still wouldn't appear in the STEP file because the format limitation hasn't been addressed. For exam strategy, remember this rule of thumb: whenever a component vanishes during export, suspect a data type mismatch between the source geometry and the target format — then identify the conversion step that bridges the gap.

Question 9

A Fusion model displays helical threads on several holes. After the model is exported to STEP and opened in another CAD system, the holes are present and correctly sized, but their walls are smooth. Other modeled details transfer correctly.

What should be checked before exporting the file again?

  1. Confirm that the thread features use modeled geometry rather than cosmetic thread representation. (correct answer)
  2. Increase STEP tessellation quality so the receiving system can reconstruct the thread helices.
  3. Change the holes to surface bodies because STEP cannot transfer threaded solid geometry.
  4. Disable design history so the cosmetic thread symbols become permanent body geometry.
Explanation: When you see a question about features not transferring correctly between CAD systems, ask yourself: is this a display/representation issue or a geometry issue? Fusion 360 distinguishes between cosmetic threads (a visual symbol applied to a surface) and modeled threads (actual helical geometry cut into the solid body). STEP files transfer solid geometry faithfully — but cosmetic threads aren't geometry at all. They're annotations telling Fusion how to display the hole, so when the file is exported, there's nothing physical for STEP to carry over. The receiving system sees a plain cylindrical hole because that's all that exists in the model data. The fix, as answer A correctly identifies, is to ensure thread features are modeled — meaning Fusion actually cuts the helix into the body before export. You can verify this in the timeline or the Hole dialog; modeled threads create visible geometry in the 3D body, not just a thread callout. Answer B is wrong because tessellation quality affects curved surface smoothness (faceting), not whether thread geometry exists in the first place — you can't tessellate something that was never modeled. Answer C is wrong because converting to surface bodies would make the geometry less transferable, not more; STEP handles solid bodies well. Answer D is wrong because disabling design history doesn't convert cosmetic annotations into real geometry — those thread symbols are metadata, not suppressed solid features. A useful rule of thumb: if a detail looks correct in Fusion but disappears after export, suspect it was never real geometry to begin with. Cosmetic threads are the classic example on this exam.

Question 10

A service bureau repeatedly imports a customer's STL files at the wrong scale because its software assumes different units. The bureau also accepts 3MF files, and the customer still needs a tessellated file suitable for additive manufacturing.

Which change most directly reduces future unit ambiguity without switching to a solid-exchange workflow?

  1. Export OBJ because polygonal formats always embed standardized physical unit definitions.
  2. Export a finer STL because additional triangles allow the receiving software to infer units.
  3. Export STEP because all additive-manufacturing software treats STEP as a sliced mesh.
  4. Export 3MF with the intended units and verify the dimensions when the bureau imports it. (correct answer)
Explanation: When a question involves file format selection for additive manufacturing workflows, focus on which format actually encodes unit metadata — not which format produces more geometry or is theoretically "universal." The 3MF format was specifically designed to solve the unit ambiguity problem that has long plagued STL files. When you export 3MF from Fusion 360, the file embeds explicit unit definitions (millimeters, inches, etc.) in its XML structure, so the receiving software knows exactly how to interpret the model's dimensions. This makes D the correct answer — exporting 3MF with intended units and verifying on import is a direct, format-level solution that keeps the workflow tessellated (suitable for additive manufacturing) while eliminating the guessing game about scale. A is false on a fundamental level: OBJ files do not embed standardized physical unit definitions. The format has no native unit specification, meaning the same import problem would persist. B misunderstands how mesh data works — triangle count carries shape information, not scale metadata. A receiving program cannot infer whether a model is in millimeters or inches from polygon density. C introduces a workflow contradiction: STEP is a boundary-representation (BREP) solid format, not a tessellated mesh, and additive-manufacturing slicers do not treat STEP files as pre-sliced geometry. Choosing STEP abandons the tessellated requirement stated in the problem. A useful rule of thumb: when you see a question about unit ambiguity in mesh-based workflows, STL is the classic culprit because it stores only geometry with no unit tag, while 3MF was purpose-built to fill that gap for modern manufacturing pipelines.