All questions
Question 1
A supplier can deliver the same machined housing as STEP, IGES, STL, or DXF. In Fusion, the housing must retain solid faces so that an engineer can move a mounting face and resize existing holes using direct-modeling tools. Native feature history is not required.
Which file type is the most appropriate starting point?
- STEP, because it commonly transfers solid B-rep geometry suitable for direct face editing (correct answer)
- IGES, because it always transfers a watertight solid with editable manufacturing features
- STL, because its triangular facets behave as native analytic faces after import
- DXF, because its planar entities reconstruct the complete three-dimensional housing automatically
Explanation: When selecting a file format for importing third-party geometry into Fusion 360 for direct modeling, the key question is: does the format preserve solid B-rep (boundary representation) geometry? B-rep solids store faces as true analytic surfaces (planes, cylinders, etc.), which Fusion's direct-modeling tools — like Press/Pull and Move Face — can recognize and manipulate cleanly.
STEP (Standard for the Exchange of Product Data) is the correct choice here. It is the industry-standard format for transferring solid B-rep geometry between CAD systems. When you import a STEP file, Fusion reconstructs the solid with intact analytic faces, meaning you can select a mounting face, push/pull holes, and resize features without needing parametric history. That's exactly what the scenario requires, making A the correct answer.
Choice B is tempting but contains a critical falsehood: IGES does not always transfer a watertight solid. IGES often imports as a collection of surfaces that may have gaps or tolerancing issues, requiring repair before direct editing. It also carries no "editable manufacturing features" — that's a native CAD concept, not something any neutral format preserves.
Choice C is fundamentally wrong because STL stores geometry as a triangular mesh, not analytic faces. After import, Fusion treats it as a mesh body, not a solid. You cannot use face-editing tools on triangle facets the way you can on true B-rep faces.
Choice D is incorrect because DXF is primarily a 2D (or limited 3D wireframe) format. It cannot reconstruct a complete 3D solid housing automatically — that would require full solid modeling from scratch.
Study tip: On format-selection questions, always ask yourself whether the format carries solid B-rep data. STEP = yes; STL = mesh; DXF = 2D/wireframe; IGES = surfaces (often unreliable).
Question 2
A DXF supplied for laser cutting inserts successfully into a Fusion sketch. The outline appears closed at normal zoom, but selecting the region for an extrusion or profile operation fails. The supplier confirms that the drawing was created from many independently trimmed segments.
Which action best addresses the likely import limitation?
- Convert the sketch directly to a mesh so Fusion can ignore all endpoint gaps
- Inspect the sketch for small gaps or overlaps, then trim or constrain the geometry (correct answer)
- Change the DXF layer colors so Fusion recognizes which entities form the profile
- Upload the same DXF as a STEP file so its sketch constraints are restored
Explanation: When a DXF imports into Fusion 360 but fails to form a selectable profile, the root cause almost always lives at the geometry level — specifically at the endpoints of individual sketch segments. DXF files don't carry parametric constraints; they store raw coordinate data. When a drawing is built from many independently trimmed segments, tiny gaps or overlaps between endpoints are common. Fusion requires a perfectly closed loop to define a valid profile for extrusion or other solid operations, so even a 0.01mm gap is enough to break the selection.
The right approach, choice B, is to inspect the sketch using Fusion's Sketch tools (such as Sketch > Fix/Make Constraints or simply zooming in on suspected trouble spots) to locate gaps and overlaps, then close them by trimming excess geometry or adding coincident constraints. This directly solves the underlying problem.
A is a workaround that converts to mesh geometry, which abandons the clean sketch-to-solid workflow entirely. Meshes carry their own limitations for precision manufacturing operations and don't resolve the profile issue — they sidestep it poorly.
C is wrong because DXF layer colors are irrelevant to profile detection in Fusion. Fusion identifies closed loops through endpoint connectivity, not color or layer metadata.
D confuses file formats. DXF and STEP serve different purposes — STEP carries solid body data, not sketch constraints. You cannot re-save a DXF as a STEP file to restore parametric relationships that never existed in the first place.
As a study tip: whenever a Fusion profile selection fails after import, always suspect endpoint gaps before anything else. Zoom in aggressively or use Sketch Palette diagnostics to find them.
Question 3
An IGES model of a molded cover imports into Fusion as several surface bodies. The surfaces visually enclose the part, but Fusion does not identify the result as a solid body.
What is the most appropriate next step before attempting solid operations?
- Stitch the surfaces and repair gaps within a suitable tolerance to form a closed volume (correct answer)
- Increase the mesh display refinement until the surfaces are recognized as a solid
- Project every surface edge into one sketch and extrude the sketch through the cover
- Assign a physical material so Fusion can calculate the enclosed volume as a solid
Explanation: When working with imported surface geometry in Fusion 360, the key concept to understand is the difference between a surface body and a solid body. A solid body requires a completely closed, watertight volume — every edge must be shared by exactly two surfaces with no gaps or overlaps. IGES files frequently import as disconnected surface patches because the format doesn't enforce watertight geometry, so knowing how to recover a solid from surfaces is an essential workflow skill.
The correct path is A: using the Stitch command (found in the Surface workspace) to merge adjacent surface bodies into a single shell. Stitch allows you to specify a tolerance, so small gaps caused by translation errors can be bridged automatically. Once all gaps are closed and the volume is sealed, Fusion promotes the result to a solid body automatically, enabling all downstream solid operations like shelling, filleting, and Boolean tools.
B is wrong because mesh display refinement only affects how the geometry looks on screen — it has no effect on the underlying mathematical topology or whether Fusion recognizes a closed volume. C is impractical and destructive: projecting all edges into a sketch ignores the existing surface geometry entirely and would lose any complex curvature the original model contains. D confuses material assignment with geometry definition — applying a physical material is a downstream property that describes what a body is made of, not whether the body exists as a solid in the first place.
As a study tip: whenever you see imported surface bodies that "look solid" but aren't recognized as one, think Stitch first, then repair. That sequence is the standard Fusion 360 surface-to-solid recovery workflow.
Question 4
A customer imports a STEP model and can select its bodies and faces. However, the customer expects the Fusion timeline to contain the original sketches, extrusions, fillets, and hole features used by the supplier.
Which explanation most accurately describes the result?
- STEP preserves every feature, but Fusion hides the timeline until the model is grounded
- STEP preserves geometric topology, but it normally does not preserve Fusion's native feature history (correct answer)
- STEP contains only triangular facets, so all parametric features become separate mesh groups
- STEP preserves sketches only, so Fusion must regenerate the solid from those sketches
Explanation: When working with file interoperability in Fusion 360, it helps to understand the difference between geometry and feature history. CAD formats fall into two broad categories: native formats (like Fusion's own .f3d) that store the parametric timeline, and neutral exchange formats (like STEP, IGES, or SAT) that store only the final, resolved geometry.
STEP (Standard for the Exchange of Product model data) captures the boundary representation (B-rep) of a solid — its faces, edges, vertices, and surface topology — but it has no mechanism to encode how that geometry was built. The supplier's sketches, extrusions, fillets, and hole features exist in their native CAD software's database, not inside the STEP file itself. When Fusion imports the STEP, it faithfully reconstructs selectable bodies and faces, but the timeline remains empty because that procedural history was never included. This makes B correct: STEP preserves geometric topology but not Fusion's native feature history.
Choice A is wrong because grounding a model is a joint/constraint concept in assemblies — it has nothing to do with unlocking the timeline after import. Choice C describes a mesh or STL-style format (triangular facets), which is entirely different from STEP's B-rep structure; STEP does not produce mesh groups. Choice D is incorrect because STEP does not selectively preserve sketches — sketches are 2D construction data that B-rep formats discard entirely along with everything else in the history.
As a study strategy, remember the phrase "STEP transfers shape, not story." Whenever an exam question contrasts native formats with neutral exchange formats, ask yourself whether the format stores process (parametric history) or result (final geometry). STEP always stores the result only.
Question 5
A scanned STL contains several million triangles. An engineer inserts it into Fusion and needs to create a few parametric mounting features referenced from the scan. Mesh selection is slow, and direct conversion of the entire scan is impractical.
Which workflow best accounts for the limitations of the imported file?
- Reduce or simplify the mesh appropriately, then convert only the required geometry if needed (correct answer)
- Export the unchanged STL as DXF, then recover all curved surfaces from its layers
- Change the document units, which automatically replaces dense facets with analytic faces
- Assign the mesh a steel material, which enables native solid-feature operations on every facet
Explanation: When working with dense mesh files in Fusion 360, your guiding principle should be: work with only what you need, and simplify before you convert. Imported STL files are made of facets — flat triangles — not parametric geometry, and millions of them will strain selection, computation, and conversion tools alike.
The smartest approach, captured in A, is to first reduce the mesh using Fusion's Mesh Simplify or Remesh tools, bringing the triangle count to a manageable level. Then, if you need to create parametric features, you convert only the relevant portions of geometry — not the entire scan. This keeps performance reasonable while still letting you reference the scan for mounting feature placement.
B is a fabricated workflow. STL files don't store layer data, and DXF export doesn't recover curved surfaces from triangle meshes — this conflates CAD formats in a way that doesn't exist in Fusion 360 or in general practice.
C is a common misconception trap. Changing document units rescales geometry but has absolutely no effect on mesh topology or face type. Dense facets remain facets regardless of units — no analytic surfaces are generated.
D misunderstands what material assignments do. Applying a material like steel changes physical simulation properties (density, thermal conductivity, etc.), but it does not unlock solid-feature operations on mesh bodies. Mesh and solid modeling environments remain distinct in Fusion 360.
For this exam, remember: mesh ≠ solid. Any question describing a heavy imported scan is testing whether you know to simplify first and convert selectively — never assume a non-geometric setting magically resolves mesh limitations.
Question 6
A designer receives a DXF containing a flat gasket outline and two construction layers. The gasket must be positioned on an angled face of an existing Fusion component and then extruded normal to that face.
Which import approach provides the most controlled result?
- Upload the DXF as an IGES surface so it aligns automatically with the angled face
- Open the DXF as a solid component and let Fusion infer the angled placement
- Insert the DXF as a mesh body and convert its layer colors into sketch planes
- Insert the DXF into a sketch on the angled face, verifying units and required layers (correct answer)
Explanation: When working with external 2D files in Fusion 360, the key question is always: where does the geometry land, and how much control do you have over it? DXF files are inherently 2D sketch data, so the most natural and controllable workflow keeps them in that format rather than forcing them into a 3D file type they weren't designed for.
Option D is correct because inserting a DXF directly into a sketch placed on the angled face is exactly how Fusion 360 is designed to handle this scenario. When you create a sketch on an angled face and use Insert > Insert DXF, Fusion imports the geometry into that sketch's local coordinate system, meaning it lies flat on the face automatically. You can then verify units (a critical step since DXF files frequently arrive in millimeters when your model is in inches, or vice versa), toggle which layers to import, and extrude normal to the face using a standard sketch extrusion — giving you precise, predictable results.
Option A fails because DXF is not an IGES format, and converting it to a surface body eliminates the sketch-level control you need for layer filtering and unit verification. Option B is a fabricated workflow — Fusion cannot open a DXF as a solid component, and there is no "infer angled placement" feature. Option C misrepresents how mesh bodies work; DXF geometry cannot be imported as a mesh, and layer colors do not convert into sketch planes.
Your study tip: on Fusion 360 exam questions involving external 2D files, always favor the workflow that uses Insert DXF into a sketch — it preserves editability, unit control, and layer selection, which are the three things that make real-world imports reliable.
Question 7
A machine designer must import a vendor's gearbox assembly. The designer wants the best chance of retaining separate solid parts and meaningful assembly organization, while accepting that the vendor's original parametric features will not be available.
Which available file should the designer request?
- A flattened DXF containing projected outlines from the gearbox drawing sheets
- A single STL containing all parts as one tessellated manufacturing reference
- A STEP assembly containing solid bodies and component or product-structure information (correct answer)
- An IGES file containing only independent surface patches for every gearbox part
Explanation: When importing third-party geometry into Fusion 360, the key question is: which format preserves solid body integrity and assembly hierarchy without requiring the original parametric history? That tradeoff — geometry fidelity vs. feature editability — is exactly what this question tests.
STEP (Standard for the Exchange of Product model data) is the right format to request here, making C correct. A STEP assembly file encodes precise boundary-representation (B-rep) solid geometry, meaning each gearbox part arrives as a true solid body rather than a mesh or surface collection. Critically, STEP also carries product-structure data — the component hierarchy that tells Fusion 360 which bodies belong to which sub-assemblies. You won't get parametric features like sketches or timelines, but you will get clean, editable solids organized as separate components.
Choice A is wrong because a DXF contains only flat 2D projected outlines from drawing sheets — there is no 3D solid information at all, so you cannot reconstruct or work with individual parts volumetrically. Choice B is wrong because a single STL merges all geometry into one faceted mesh with no part boundaries or hierarchy; you'd receive one undivided triangle soup with no way to isolate individual gears or housings. Choice D is wrong because IGES surface patches are untrimmed or independent surfaces — they do not form closed solids automatically, and IGES carries no assembly structure, so you'd face significant cleanup work with no organizational benefit.
A useful rule of thumb: STEP for solids and assemblies, IGES for surfaces only. When a question mentions retaining separate parts and assembly organization, STEP is almost always the answer.
Question 8
A legacy STL contains a bracket that should be approximately 50 mm wide. After insertion into Fusion, it measures approximately 1270 mm wide. The geometry is otherwise proportionally correct.
What is the most likely cause, and what is the most appropriate correction?
- The source coordinates were interpreted as inches; reinsert the mesh using millimeters (correct answer)
- The source coordinates were interpreted as centimeters; reinsert the mesh using meters
- The mesh normals were reversed; recalculate the normals before measuring the width
- The mesh was automatically refined; reduce its facet count before measuring the width
Explanation: Whenever Fusion 360 imports a mesh file, it must interpret the raw coordinate values using a specific unit. STL files store only unitless numbers — they carry no embedded unit metadata — so Fusion makes an assumption based on your document settings or a prompt at import time.
Here's the key insight: 1 inch equals exactly 25.4 mm. If a bracket is truly 50 mm wide, its coordinate value in inches would be approximately 1.97. If Fusion misreads those millimeter values as inches, it scales them up by a factor of 25.4, producing 50×25.4=1270 mm. That's precisely the measurement described in the passage — a smoking-gun ratio of 25.4×. The fix is to reinsert the mesh and explicitly tell Fusion the source unit is millimeters, making answer A correct.
Answer B is wrong because a centimeter-to-meter misinterpretation would produce a 100× scale error, not 25.4×. A 50 mm bracket would balloon to 5,000 mm, not 1,270 mm.
Answer C is a red herring. Reversed mesh normals affect how surfaces are shaded or rendered — they can cause faces to appear inside-out — but they have absolutely no effect on measured geometry dimensions.
Answer D is similarly off-track. Mesh refinement (subdividing facets) changes surface smoothness and polygon count, not the physical size of the model. Reducing facets won't alter a width measurement.
Study tip: Memorize the 25.4 multiplier. On import-related questions, if you see a ~25× size discrepancy, immediately think "inch/millimeter confusion." That ratio is your diagnostic clue. Question 9
A reverse-engineering technician receives only an STL of a precision shaft. After import, the shaft's cylindrical areas consist of many flat facets. The downstream drawing requires an exact cylinder axis and diameter rather than an approximation fitted to triangles.
Which conclusion is most appropriate?
- Convert the STL directly to B-rep because every faceted region automatically becomes one exact analytic face
- Increase visual smoothness because display refinement restores the original analytic cylinder geometry
- Request STEP or another precise CAD format because the STL no longer contains the exact cylinder definition (correct answer)
- Export the STL as IGES because changing the file format reconstructs the original design surfaces precisely
Explanation: When working with mesh files in Fusion 360, the critical concept is data fidelity — understanding what geometric information a file format actually contains. STL files store geometry as a mesh of triangles. They approximate curved surfaces by subdividing them into flat facets, and in doing so, they permanently discard the original mathematical definitions of those curves. A cylinder that once existed as a precise analytic surface (defined by a center axis, radius, and height) becomes nothing more than a collection of triangles — there is no hidden cylinder waiting to be recovered.
This is exactly why C is the right conclusion. When a precision drawing demands an exact cylinder axis and diameter, you need the original parametric or analytic geometry. A STEP file, for example, stores true B-rep geometry with exact analytic surfaces. Requesting that format from the source is the only way to guarantee the exact definition is preserved.
A is wrong because converting an STL to B-rep in Fusion 360 does not automatically produce exact analytic faces. The software may fit geometric primitives to facet groups, but this is an approximation — not a recovery of the original design intent. A is a common trap because the conversion sounds precise.
B is wrong because display refinement only changes how Fusion 360 renders the mesh visually. Smoothing the appearance of facets does nothing to restore underlying geometry that was never stored in the file.
D is wrong because exporting to IGES (or any other format) cannot reconstruct geometry the STL never contained. Format conversion only repackages existing data — it cannot create missing information.
Study tip: Remember that mesh formats (STL, OBJ) are geometry approximations — no downstream conversion recovers what was discarded at export.
Question 10
A supplier's STEP file is uploaded and translated into a Fusion design. Two weeks later, the supplier sends a revised STEP file under the same filename. The engineer expects the previously imported Fusion design to update without further action.
Which statement best describes the expected data-management behavior?
- The imported design updates automatically if both STEP files use the same physical units
- The imported design remains linked by filename; opening it downloads the supplier's latest file
- The imported design updates only its sketches; solid bodies remain fixed at the first version
- The imported design is a translated snapshot; the revision must be imported or replaced deliberately (correct answer)
Explanation: When working with imported files in Fusion 360, the critical concept to understand is the difference between a live link and a translated snapshot. When you upload a STEP file, Fusion 360 runs a translation process that converts the geometry into a native Fusion design. That translated result is a standalone copy — it has no persistent connection back to the original source file.
This is why D is correct. Once the STEP file is translated, the resulting Fusion design lives independently in your data panel. If the supplier sends a revised file, Fusion has no mechanism to detect or pull that change automatically. You must deliberately import the new STEP file or use the "Replace" workflow to update the design. The revision doesn't propagate on its own.
A is wrong because unit matching has nothing to do with automatic updates — there simply is no automatic update mechanism for imported STEP files regardless of units. B describes behavior similar to a cloud-linked reference or a live URL, which isn't how STEP imports work; Fusion doesn't maintain a filename-based subscription to external files. C invents a behavior that doesn't exist — Fusion doesn't selectively update sketches while freezing solid bodies. Translation is an all-or-nothing operation that produces a static result.
A useful rule of thumb: if data came in through a translation (STEP, IGES, SAT), treat it as frozen. Only native Fusion references (like xrefs through Insert > Insert into Current Design with linked components) maintain update relationships. On exam questions about imported file formats, always ask yourself whether a live link was ever established — if it wasn't, the answer involves manual action.