Autodesk Revit Quiz: Ifc Export
10 questions · exam conditions
0:00
Ifc ExportQuestion 1 of 10

A structural consultant requires an IFC file for model coordination. The project delivery requirements explicitly specify IFC 2x3 Coordination View 2.0. The architect's Revit exporter also offers newer IFC4 configurations.

Which export approach best satisfies the interoperability requirement?

Select the newest IFC4 configuration because newer schemas automatically satisfy all earlier delivery requirements.
Select IFC 2x3 Reference View because the schema version matters more than the specified model view.
Select IFC 2x3 Coordination View 2.0 because both the requested schema and model view must match.
Send the native Revit model because an IFC configuration is unnecessary when both teams use BIM software.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Ifc Export

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

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 structural consultant requires an IFC file for model coordination. The project delivery requirements explicitly specify IFC 2x3 Coordination View 2.0. The architect's Revit exporter also offers newer IFC4 configurations.

Which export approach best satisfies the interoperability requirement?

  1. Select the newest IFC4 configuration because newer schemas automatically satisfy all earlier delivery requirements.
  2. Select IFC 2x3 Reference View because the schema version matters more than the specified model view.
  3. Select IFC 2x3 Coordination View 2.0 because both the requested schema and model view must match. (correct answer)
  4. Send the native Revit model because an IFC configuration is unnecessary when both teams use BIM software.
Explanation: When exporting IFC files from Revit, you must satisfy two distinct requirements simultaneously: the IFC schema version (e.g., IFC 2x3 vs. IFC4) and the model view definition (MVD), such as Coordination View 2.0 or Reference View. These are independent specifications, and project delivery requirements typically mandate both explicitly for a reason — different MVDs define what data gets exported and how it's structured for downstream use. C is correct because it honors both the specified schema (IFC 2x3) and the required MVD (Coordination View 2.0). When a structural consultant's workflow or coordination platform is configured around IFC 2x3 Coordination View 2.0, delivering exactly that ensures full compatibility — no guesswork, no data loss from schema mismatches. A is wrong because newer schemas do not automatically satisfy older delivery requirements. IFC4 introduces structural and geometric changes that may be incompatible with the consultant's receiving software or workflow. "Newer is better" is a common trap — here, precision matters more than recency. B is wrong because it correctly identifies the schema version (IFC 2x3) but selects the wrong MVD. Reference View is a read-only, geometry-focused export intended for visualization, not coordination. Swapping the MVD changes what data is included, which defeats the purpose of interoperability. D is wrong because native Revit files require the recipient to use compatible Revit software and licensing. IFC exists precisely to enable open, software-agnostic coordination — assuming shared BIM software is a common but risky assumption in multi-discipline projects. Study tip: On IFC export questions, always treat schema version and model view definition as a pair — both must match the specification, never just one.

Question 2

An architectural host model contains linked structural and mechanical Revit models. The receiving coordination platform needs separate discipline IFC files that retain their coordinated placement.

Which IFC export strategy is most appropriate?

  1. Bind both linked models into the host, then export one combined IFC file from the resulting project.
  2. Unload the linked models and export only the architectural host using the host model's internal origin.
  3. Export one host IFC and expect the IFC file to maintain live references to the linked Revit files.
  4. Enable linked-file export as separate IFC files and use the established coordinated positioning for the outputs. (correct answer)
Explanation: When working with multi-discipline BIM coordination in Revit, the core challenge is preserving each discipline's spatial relationship during export. IFC is a static exchange format — it captures geometry and metadata at a point in time, so your export strategy must deliberately maintain the shared coordinate system that keeps all files aligned in the receiving platform. The correct approach, D, leverages Revit's built-in capability to export linked models as separate IFC files in a single operation while applying the same coordinated positioning (typically Shared Coordinates) to each output. This means the structural IFC, mechanical IFC, and architectural IFC all share a common origin, so they stack correctly when loaded into any IFC viewer or coordination platform without manual repositioning. A is tempting but problematic: binding linked models merges them into the host, destroying discipline separation. The receiving platform gets one monolithic file instead of the separate discipline files explicitly required. B is even worse — unloading the linked models simply omits them entirely, exporting only the architecture. The structural and mechanical content disappears from the deliverable completely, which directly violates the project requirement. C reflects a fundamental misunderstanding of IFC's nature. IFC has no concept of live references or dynamic links back to Revit files; once exported, it is a self-contained static dataset. Expecting it to "maintain live references" is not a feature that exists. A useful rule of thumb: whenever a question asks about exporting a Revit project with links into IFC, always ask yourself two things — are the disciplines separated? and is the coordinate system shared? Option D is the only choice that satisfies both conditions simultaneously.

Question 3

Several discipline models have been aligned in Revit using published survey control and shared coordinates. When the first IFC files are combined, the geometry must retain this established site relationship rather than move to each model's internal origin.

Which positioning choice should be used for the IFC exports?

  1. Use shared-coordinate site placement consistently for every discipline model being exchanged. (correct answer)
  2. Use each model's internal origin because IFC viewers automatically reconstruct Revit shared coordinates.
  3. Use the project base point independently in each model without confirming that the values agree.
  4. Move the modeled geometry near the internal origin before every export and restore it afterward.
Explanation: When multiple discipline models (architectural, structural, MEP, civil) are coordinated using shared coordinates and survey control in Revit, the entire point is that every model agrees on a common real-world position. When you export to IFC for federated review, you must preserve that spatial agreement — otherwise models that were perfectly aligned in Revit will appear offset or scattered in the IFC viewer. Choosing shared-coordinate site placement (answer A) instructs Revit to export each model's geometry relative to the shared coordinate system — the same survey-based origin every discipline agreed upon. When those IFC files are combined in any BIM coordination tool, the geometry lands in the correct real-world relationship automatically, because every file references the same anchor point. Answer B is dangerously wrong because IFC viewers have no knowledge of Revit's internal shared coordinate data — there is no automatic reconstruction of that relationship. Once you export from Revit, the viewer only sees what the IFC file contains. Answer C fails because each model's project base point can have completely different local values; using them independently without verifying they match guarantees misalignment when files are federated. Answer D is a workflow anti-pattern: manually moving geometry introduces human error, breaks design intent, and risks permanent data loss if a restore step is missed or applied incorrectly — it also defeats the entire purpose of establishing shared coordinates in the first place. A useful rule of thumb: in any Revit interoperability question involving multiple discipline models and a shared site, shared coordinates must travel with the export. If an answer suggests each model can do something "independently" without coordination, treat it with immediate suspicion.

Question 4

A project contains Existing, New Construction, and Future phases. The contractor requests an IFC representing the completed New Construction condition, excluding elements created only in the Future phase.

Which action most directly controls the intended IFC model state?

  1. Rename the New Construction phase so it sorts last in the Project Browser before exporting.
  2. Export every phase and rely on the contractor's IFC viewer to remove future elements automatically.
  3. Set New Construction as the phase to export and verify the export view shows the required condition. (correct answer)
  4. Place the New Construction views on sheets because sheet placement determines the IFC phase scope.
Explanation: When exporting to IFC from Revit, the critical concept is phase mapping: the IFC export reads the phase assigned to the export view, not the project's phase list order or sheet organization. The view's phase setting determines which elements appear, how they are categorized, and what construction status they carry in the exported file. Setting the export view's phase to New Construction — as option C describes — is the direct, reliable mechanism. Revit evaluates each element's phase created and phase demolished against that view phase, so only elements that exist in the completed New Construction condition appear. You should also verify the phase filter on that view is set to "Show Complete" or equivalent so demolished and future elements are properly excluded before the export runs. Option A is a trap: phase sort order in the Project Browser is purely a display preference and has absolutely no effect on what data gets written to an IFC file. Option B offloads responsibility to the contractor's viewer, which may not handle phase filtering at all — this is unreliable and not a Revit workflow. Option D confuses sheet placement with data scope; placing a view on a sheet affects printing and documentation organization, but IFC export scope is controlled by the view's own phase and filter settings, not its sheet assignment. The study tip to remember: in Revit IFC workflows, phase control lives on the view, not on the sheet or the phase list. Whenever an exam question involves coordinating phase-specific IFC exports, always look for the answer that references the view's phase setting directly.

Question 5

A custom reception desk must remain in its current Revit category for office standards. In a test IFC, however, it is classified as a generic proxy, preventing the receiving application from filtering it with other furniture.

What is the best correction before the final IFC export?

  1. Assign the desk to a furniture workset because IFC entities are determined primarily by workset membership.
  2. Add a furniture material because the object's IFC class is inferred from its rendered material name.
  3. Create a furniture subcategory because every Revit subcategory automatically becomes an IFC entity class.
  4. Assign an appropriate IFC export class and type mapping while preserving the required Revit category. (correct answer)
Explanation: When preparing Revit models for IFC export, it's important to understand that Revit categories and IFC entity classes are two separate classification systems. Revit organizes objects for internal project management; IFC organizes objects so receiving applications — structural analysis tools, clash detection software, FM platforms — can filter and use them correctly. A mismatch between the two is exactly what this question describes. The best solution is D: assigning an explicit IFC export class and type mapping directly to the element. Revit allows you to override the default IFC entity mapping (which caused the generic proxy classification) through element properties or a custom IFC export mapping table, all without touching the element's Revit category. This preserves your office standards while giving the receiving application the correct IfcFurnishingElement or equivalent classification it needs to filter furniture properly. Choice A is a common misconception — worksets are a collaboration and visibility tool in Revit and have absolutely no influence on how elements are classified in an IFC export. Choice B is similarly wrong; IFC class assignment has nothing to do with material names or rendering properties. Materials control appearance, not data classification. Choice C sounds logical but is incorrect because Revit subcategories map to graphical override purposes within Revit, not to IFC entity classes — creating a furniture subcategory would not automatically produce a different IFC output. As a study tip, remember the key principle: Revit category ≠ IFC entity class. On exam questions about IFC export problems, always look for the answer that addresses the IFC mapping layer directly rather than changing unrelated Revit organizational settings.

Question 6

A project team must issue IFC files at several milestones. The first two exports used different schema, coordinate, and property settings because users relied on whichever options were last active.

What is the most reliable way to improve consistency for later issues?

  1. Use the default exporter configuration each time, because default settings are guaranteed to remain identical across all Revit versions and project files.
  2. Create a named IFC export setup, document its intended scope, and verify issue-specific phase or view settings before each milestone export. (correct answer)
  3. Use the temporary in-session setup without saving it, because Revit automatically retains all unsaved export options for future project sessions.
  4. Copy the previous IFC file and rename it with the new milestone date, because renaming an IFC regenerates its model data from the current project state.
Explanation: When managing repeated IFC exports across project milestones, the core challenge is reproducibility — ensuring every export uses exactly the same schema, coordinate system, and property mappings unless deliberately changed. This is fundamentally a workflow and settings-management question, not a technical IFC question. The most reliable solution is B: creating a named IFC export setup. In Revit's IFC Export dialog, you can save a configuration with a specific name, locking in your schema version (e.g., IFC2x3 or IFC4), coordinate settings, property sets, and other parameters. Before each milestone, you load that named setup, verify any issue-specific adjustments like phase or view scope, and export. This eliminates the "last active settings" problem the team experienced — everyone uses the same documented baseline. Answer A is wrong because Revit's default export settings are not guaranteed to be identical across versions or even project files. Defaults can shift between Revit releases, making them an unreliable baseline for coordinated deliverables. Answer C is a trap: Revit does not automatically retain unsaved in-session export options between project sessions. When you close and reopen the project, unsaved settings are lost — which is exactly what caused the team's inconsistency problem. Answer D describes something technically impossible. Renaming an IFC file simply changes the filename on disk. It does not re-export or regenerate any model data from the current Revit project state. For the exam, remember: named setups = repeatable exports. Any question about IFC consistency, coordination across milestones, or multi-user workflows should point you toward saved, documented configurations rather than ad hoc or default settings.

Question 7

A coordination model must include only the building core and shell. A dedicated 3D view already hides furniture, casework, and other excluded categories, while the full Revit model must remain unchanged.

What should the user do before exporting the IFC file?

  1. Apply the coordination view template, then export the entire model without using any view-based export option.
  2. Activate the dedicated 3D view and enable the option to export only elements visible in that view. (correct answer)
  3. Select the visible elements manually and assume the IFC exporter always limits output to the current selection.
  4. Temporarily delete the excluded model categories, export the IFC file, and undo the deletion afterward.
Explanation: When exporting an IFC file from Revit, the key concept being tested is how to control scope — specifically, how to ensure only the intended elements are exported without altering the underlying model. Revit's IFC exporter gives you precise control over this through view-based export settings. The correct approach, choice B, is to activate the dedicated 3D view and enable the "Export only elements visible in view" option in the IFC Export Settings dialog. Because that 3D view already has visibility/graphics overrides hiding furniture, casework, and other excluded categories, enabling this option means only the visible (core and shell) elements are written to the IFC file — exactly what the coordination model requires. The original Revit model stays completely untouched. Choice A is flawed because applying a view template but then exporting the entire model ignores the view-based filter entirely. The IFC exporter will output all model elements regardless of what the active view shows, defeating the purpose. Choice C reflects a common misconception — the IFC exporter does not automatically limit output to whatever you have manually selected. Selection sets in Revit don't carry over to the IFC export scope unless you explicitly configure the exporter to respect them, and even then, this isn't the standard workflow. Choice D is dangerous and unnecessary. Temporarily deleting categories risks data loss or workflow errors, and using destructive edits as a workaround is never a best practice when non-destructive view-based options exist. As a study tip: whenever a Revit question involves exporting a subset of the model, think "view-based export." Revit's view visibility controls are the intended, non-destructive mechanism for scoping exports.

Question 8

A wall extends continuously through three building levels. The receiving estimating system organizes quantities by IFC building storey and requires separate wall objects for each storey.

Which export setting best supports this requirement without remodeling the wall?

  1. Enable the option to split walls and columns by building storey during IFC export. (correct answer)
  2. Enable room-bounding behavior so the wall is divided wherever a level intersects its geometry.
  3. Increase the IFC geometric detail so the estimator can infer three separate wall objects.
  4. Export only the active level plan because one plan export automatically creates all storey segments.
Explanation: When exporting to IFC from Revit, you need to understand how Revit handles multi-storey elements and how downstream systems consume that data. Estimating platforms that organize by IFC building storey expect discrete wall objects per floor — but that doesn't mean you have to rebuild your model. Revit's IFC export dialog includes a dedicated option to split walls and columns by building storey. When enabled, a wall spanning three levels is automatically exported as three separate IFC wall entities, each assigned to its corresponding storey, without any changes to the Revit model itself. This is exactly what option A describes, making it the correct choice. Option B is a common trap. Room-bounding is a property that controls whether a wall contributes to room area calculations — it has no effect on how the wall is segmented during IFC export. Enabling it won't split anything by level. Option C misunderstands what geometric detail (Level of Detail) controls. Increasing it affects mesh resolution and surface accuracy, not how objects are divided or classified by storey. The estimator would still receive one wall object, just with more geometry. Option D is simply incorrect. Exporting from an active level plan view does not automatically segment multi-storey walls into storey-level objects. IFC export scope can be controlled by view, but that doesn't create the per-storey splits the downstream system needs. Your study tip: whenever a question asks how to satisfy an IFC data requirement without remodeling, look first at export settings. Revit's IFC exporter has purpose-built options — like the storey-split toggle — designed precisely for these interoperability scenarios.

Question 9

A quantity-surveying application can read IFC objects, but a test export lacks expected standard properties and measurable quantities such as areas and volumes. The geometry itself appears correctly.

Which change most directly addresses both missing data types?

  1. Enable only internal Revit property export because internal parameters automatically generate every IFC quantity.
  2. Enable appropriate IFC property-set export and base-quantity export in the selected IFC configuration. (correct answer)
  3. Increase geometric detail and tessellation because quantities and properties are derived only from mesh density.
  4. Export the model as IFCZIP because compression adds quantity definitions and standard property sets.
Explanation: When exporting to IFC from Revit, it helps to understand that an IFC file carries two distinct data layers beyond geometry: property sets (which store descriptive attributes like material, fire rating, and type information) and base quantities (which store measurable values like area, volume, and length). These are separate export toggles in Revit's IFC Export Settings, and both must be deliberately enabled — they don't come along automatically just because geometry exports correctly. Since your scenario shows correct geometry but missing properties and quantities, the fix requires addressing both data layers simultaneously. Option B is correct because enabling IFC property-set export restores the standard descriptive attributes, while enabling base-quantity export restores the measurable values — a single configuration change that resolves both gaps at once. Option A is wrong because internal Revit parameters are not automatically mapped to IFC quantity definitions. Revit's native parameters and IFC base quantities (defined by the IFC schema's Qto_ classes) are separate systems; exporting internal parameters doesn't generate standardized IFC quantities that a quantity-surveying application can reliably parse. Option C is wrong because geometry tessellation controls mesh resolution for visual fidelity, not data content. Properties and quantities are schema-level metadata — they have nothing to do with how finely a surface is triangulated. Option D is wrong because IFCZIP is simply a compressed container format. Compression changes the file packaging, not the data inside — it cannot add property sets or quantity definitions that weren't included during export. Study tip: On IFC export questions, always distinguish between three independent layers — geometry, property sets, and base quantities — and remember each requires its own export setting to be active.

Question 10

A client requests an IFC coordination model and a formal drawing issue containing title blocks, dimensions, sheet numbers, and revision clouds. The project manager proposes delivering only one IFC file.

Which publishing approach best meets the client's complete request?

  1. Export only IFC and assume the recipient can reconstruct the issued sheets from model geometry.
  2. Enable 2D plan-element export and assume it reproduces every sheet, title block, and revision record.
  3. Deliver the IFC model for interoperability and publish the drawing sheets separately as PDF or DWF. (correct answer)
  4. Convert all title blocks and dimensions into model families so they become coordination objects in IFC.
Explanation: When a client makes a compound request — asking for both a coordination model and formal issued drawings — you need to recognize that these are two fundamentally different deliverables serving two different purposes. IFC files are built for interoperability between software platforms, carrying 3D geometry and object data. Issued drawing sheets carry contractual and communication content: title blocks, revision clouds, sheet numbers, and dimensions formatted for human review and record-keeping. No single file format handles both jobs equally well. Option C is correct because it respects that distinction. You deliver the IFC model so consultants can import geometry into their own BIM authoring tools, and you separately publish the sheets as PDF or DWF so the client receives the formal, annotated drawings they need for approval, coordination, and archiving. This is standard professional practice on BIM projects. Option A fails because IFC files do not preserve sheet layout, title block data, or revision records — the recipient cannot reconstruct formal drawing sets from raw model geometry alone. Option B is a trap: while Revit's IFC export does include a 2D plan-element option, it captures basic linework, not the full sheet environment with title blocks, legends, and revision clouds. Assuming it reproduces everything a formal issue requires is incorrect. Option D is impractical and misguided — converting title blocks and dimensions into model families corrupts their purpose and produces unusable coordination objects that don't meaningfully represent building components. As a study tip, watch for questions where a single-format solution is proposed for a multi-requirement deliverable. On Revit exams, the correct answer almost always separates BIM coordination outputs from documentation outputs rather than forcing one to substitute for the other.