Autodesk BIM_MGT_101 Autodesk Certified Professional in BIM Management for Building Design Exam Practice Test

The lighting team should correct the source CAD file so that it conforms to the project’s approved coordinate framework and then reissue it. External discipline files must be delivered with a predictable origin, orientation, and elevation that correspond to the architectural or designated site-control model. Correcting the source ensures that every recipient can link the file consistently and that subsequent updates retain the same placement.

Manually moving the linked CAD file in Revit creates an unmanaged instance offset. Although the file may appear aligned temporarily, reloading, replacing, or distributing it can reproduce the original problem or create inconsistent positioning among team members. Adding gridlines may help visually diagnose the offset but does not establish a reliable coordinate relationship.

Acquiring coordinates from the misaligned lighting file is particularly inappropriate because it would redefine the host model’s shared-coordinate relationship based on a non-authoritative and incorrectly positioned reference. The architectural or site model should remain the approved source of project positioning.

The BIM manager should provide the lighting team with the agreed coordinate protocol, reference model, control points, units, and required vertical datum, then validate the corrected file before accepting it for coordination.

Reference topics: Consultant file requirements; shared-coordinate governance; CAD-link positioning; authoritative coordinate sources; model exchange; coordination quality control.

===============

Software version and build information is essential because Revit models are not backward-compatible. Opening and saving a model in a newer release upgrades it, potentially preventing teams using an earlier version from accessing the file. Build differences can also matter where hotfixes or updates affect cloud worksharing, interoperability, stability, or specific model functions.

Required add-ins are equally important. A model or workflow may depend on third-party tools for data validation, content placement, exports, parameter management, automation, or specialized object handling. If contributors lack the approved add-in or use incompatible versions, they may be unable to reproduce required processes or may generate inconsistent deliverables.

Project units and shared coordinates are critical for modelling and spatial coordination, but they are project-configuration issues rather than the most direct determinants of digital-tool compatibility. Graphic standards govern presentation and documentation consistency but do not determine whether the model and workflow can be operated within the organization’s technology environment.

The kickoff should therefore confirm the approved software release, build, update policy, required add-ins, licensing, installation procedures, and testing responsibilities before production begins.

Reference topics: Software compatibility; Revit version management; approved builds; add-in governance; technology assessment; project kickoff; fast-track mobilization.

===============

A view filter can be configured to act only on ceilings meeting specific criteria, such as family name, type name, material, height, or another parameter. Because the missing ceiling is a 2x4 type while the visible ceilings are 2x2 types, a filter targeting the 2x4 ceiling could hide it or override its graphics without affecting the other ceilings.

A Plan Region can also impose a localized View Range that differs from the parent Reflected Ceiling Plan. If the hallway contains a Plan Region with a higher cut plane or an otherwise incompatible view range, the ceiling can fall outside the region’s visible range even though it remains present and visible in a 3D view.

The ceiling was not deleted because it is still visible in 3D. Turning off the Ceilings category through a View Template would ordinarily hide all ceilings governed by that category in the view, contradicting the fact that the 2x2 ceilings remain visible. Similarly, Hide in View by Category affects the entire Ceilings category within that view rather than one ceiling type or a single hallway element.

Reference topics: Reflected Ceiling Plans; View Range; Plan Regions; view filters; category visibility; view-template troubleshooting.

===============

The clash matrix is the project’s approved framework for determining which model combinations, object categories, zones, and tolerances require coordination. The BIM manager should configure clash tests to reflect that matrix rather than distribute an unfiltered list of every geometric intersection generated by the software.

Low-value results should be removed through controlled rule selection, object-category filtering, zone-based scoping, and technically justified tolerance settings. Reports can then be organized according to each discipline’s responsibility and focused on clashes that materially affect constructability, design intent, access, maintenance clearances, or code compliance.

Sending all 3,000 results to project teams transfers the BIM manager’s triage responsibility to designers and creates substantial coordination noise. Manual spreadsheet sorting separates the results from model context and is inefficient for repeated review cycles. Arbitrarily relaxing clash rules merely to reduce totals is also unacceptable; tolerances must correspond to documented project requirements rather than a desired numerical result.

Applying the clash matrix creates a repeatable, auditable process and ensures that coordination meetings address consequential issues instead of irrelevant geometric contacts.

Reference topics: Clash matrices; clash-test configuration; tolerance management; discipline-based reporting; coordination prioritization; Model Coordination.

===============

Revit phase mapping is specifically intended to reconcile differences between phase structures in a host model and a linked Revit model. The BIM manager should map Phase 1 in the structural link to Existing in the architectural host and map Phase 2 to New Construction . Revit can then interpret the linked elements’ phase-created and phase-demolished conditions in the context of the host view.

This preserves the structural consultant’s internal phase definitions and avoids altering a model controlled by another discipline. It also produces consistent display behaviour across host views using phase filters such as Show Previous + Demo, Show Complete, or other project-specific configurations.

A Visibility/Graphics override can alter how an entire link or category appears, but it does not correctly translate the underlying phase relationships. Renaming or restructuring the phases directly in the consultant’s model is unnecessary and may disrupt that firm’s documentation. A host view template can control link-display settings, but it cannot substitute for correct phase correspondence where the two files use different phase names or phase structures.

Phase mapping is therefore the controlled, non-destructive coordination mechanism for this scenario.

Reference topics: Revit phase mapping; linked-model display; phase filters; demolition views; host and consultant model coordination; multidisciplinary phase standards.

===============

The BIM manager should first test whether the client’s data definitions and templates can support consistent production across all participating regions and disciplines. Shared-parameter files and naming conventions must be reviewed because inconsistent parameter definitions, duplicate identifiers, regional naming variations, or conflicting classifications can compromise schedules, model checking, data exports, and asset-information delivery.

The project templates must also be evaluated for units, naming structures, view organization, browser conventions, coordinates, and other coordination-critical settings. On a fast-track project, deficiencies in these baseline resources will be replicated rapidly across many models and become expensive to correct after production begins.

Training and software access are valid mobilization concerns, particularly with a new collaboration platform, but they do not establish whether the client’s actual BIM standards and templates are technically coherent. Sample sheets and title blocks primarily reveal graphical preferences rather than digital-delivery capability. Allowing unrestricted discipline customization would weaken standardization and increase coordination risk.

Options A and B directly assess whether the client’s existing resources provide a consistent data and model-authoring foundation for distributed, high-velocity delivery.

Reference topics: Client-standard assessment; template validation; shared-parameter governance; naming conventions; regional consistency; project mobilization.

===============

A project-specific BIM kickoff is required to convert the BEP and client information requirements into operating procedures understood by every contributor. The session should align teams on weekly publication deadlines, approved file formats, model naming, coordinate standards, coordination responsibilities, issue workflows, COBie parameter requirements, validation gates, and final handover expectations.

This is particularly important where consultants use different platforms. The team must agree on interoperability methods, exchange formats, responsibility for data loss during conversion, and the authoritative location for approved information. The kickoff also provides an opportunity to identify training, software, access, and resource gaps before they affect production.

Accepting each firm’s standard workflow would preserve incompatible practices rather than establish a unified project process. Configuring permissions is necessary, but a Common Data Environment cannot compensate for undefined workflows or inconsistent deliverables. Waiting to modify a baseline BEP only after coordination problems occur is reactive and allows preventable errors to enter the project.

The kickoff should conclude with confirmed responsibilities, documented decisions, action owners, and controlled updates to the BEP and delivery plans.

Reference topics: BIM kickoff; multidisciplinary alignment; COBie; interoperability planning; coordination uploads; project-specific workflows; BIM Execution Plan implementation.

Parameters Service

The team member should select Parameters Service on the Manage ribbon. The exhibit specifically shows this tool between Project Information and Project Parameters. The Parameters Service provides a centralized method for accessing and applying approved parameter definitions that have been made available to the organization. Because the BIM manager has already extracted the client’s custom shared parameters into that service, the project team should consume those controlled definitions from the same source.

This workflow supports parameter governance by reducing the risk of users creating duplicate parameters with similar names, selecting outdated shared-parameter definitions, or introducing parameters with incompatible identifiers, data types, disciplines, or grouping. A shared parameter is not defined solely by its displayed name; its underlying definition must remain consistent for reliable scheduling, tagging, filtering, exporting, and cross-project data exchange.

The Project Parameters tool is used to create or bind parameter definitions within a project, but it is not the designated interface for retrieving the organization’s centrally managed definitions in this scenario. The Shared Parameters command manages conventional shared-parameter files, while Global Parameters control design relationships inside a project and do not serve this data-standardization purpose.

Reference topics: Parameters Service; shared-parameter governance; centralized BIM standards; parameter consistency; project data requirements; reusable corporate content.

===============

Exhibit 3 represents the correct multi-building coordination condition. It shows the three building models occupying their intended and separate locations while referencing a common site-coordinate framework. Each building retains the model reference required for its individual internal setup, but all models are related to one consolidated site reference, thereby preserving their geographic placement and orientation when linked into the site model.

Exhibit 1 displays multiple displaced site-reference indicators, suggesting that the building models have not been reconciled to one authoritative shared-coordinate system. This condition creates a risk that models will appear correctly only when manually positioned and will subsequently shift when reloaded or exchanged. Exhibit 2 does not demonstrate the required relationship between the individual building origins and the shared site reference. Exhibit 4 places the building geometries on top of one another, which is characteristic of models linked using a common internal origin without applying their correct site positions.

For a campus or multi-building project, the site model should function as the authoritative spatial reference. Each building model is positioned against that site definition, and the coordinated relationship is retained through shared positioning rather than repeated manual movement. This allows consistent federation, consultant exchange, reload behavior, and downstream coordination.

Reference topics: Shared coordinates; multi-building projects; site-model authority; linked-model positioning; survey and internal reference management; model federation.

===============

The BIM manager should perform a formal compliance review against the BIM Execution Plan, model-content standard, information requirements, and applicable element or classification matrix. Each nonconforming condition should be documented clearly, including incorrect category assignments, inconsistent object styles, excessive geometric detail, missing parameters, invalid naming, and unsuitable data structures.

The subcontractor should then receive a controlled revision request identifying the required corrections and resubmission criteria. Geometry should be simplified to the level needed for coordination and downstream use, but required metadata, classifications, connection points, clearances, and asset information must be retained. Optimization and information compliance are parallel requirements, not competing alternatives.

Approving the model unchanged would introduce performance and data-quality defects into the federation and could cause unreliable clash results, scheduling errors, or handover deficiencies. Hiding excessive detail with view filters changes only its visibility; the underlying geometry and data remain noncompliant and continue to affect model processing. Instructing the subcontractor to reduce file size regardless of information loss also fails the project’s deliverable requirements.

Acceptance should occur only after the revised model passes the defined quality-control checks.

Reference topics: Content standards; subcontractor deliverables; model acceptance criteria; geometry optimization; classification and metadata; BEP compliance; quality-control reporting.

Because the host model itself has not changed, the first investigation should focus on how the external references are being resolved. Relative paths depend on the relationship between the host file and the linked files within the project folder structure. If a folder was renamed, relocated, synchronized differently, or omitted from a distributed package, Revit may no longer locate the linked models even though the links remain correctly configured in the host.

The BIM manager should review the link status and saved paths in Manage Links , confirm that the referenced files still exist, and compare the current folder structure with the approved project structure. Access permissions, cloud synchronization status, and network availability should also be checked where applicable.

Converting all references to absolute paths would make the links dependent on a specific drive or network location and commonly causes failures for other users. Removing and reinserting links risks losing positioning, pinning, display overrides, workset assignments, and coordination history. Rebuilding the host from backup is disproportionate and does not address an external path or access failure.

Reference topics: Manage Links; relative file paths; federated-model folder structures; reference resolution; link-status troubleshooting; Common Data Environment access.

===============

A dedicated coordination group defines the exact collection of models that will participate in the specified coordination review. Assigning only the Architectural and Structural published models to that group limits clash processing to the required discipline pair and produces a clean, controlled result set aligned with the approved clash matrix.

Running clash detection across every model and filtering the results afterward is inefficient and may generate a large volume of irrelevant issues. It also makes reporting less precise because the underlying coordination space still includes trades that were explicitly intended to be excluded. Requesting other disciplines to remove views or models disrupts established publication workflows and may affect other coordination activities. Similarly, merging all models into one file and manually hiding elements eliminates clear model ownership and is not an appropriate cloud-coordination method.

Coordination groups allow the BIM manager to establish discipline-specific or package-specific clash tests without modifying the source models. Separate groups may be maintained for Architectural–Structural, Mechanical–Structural, Architectural–MEP, or other approved combinations.

Reference topics: Model Coordination; coordination groups; clash matrices; published design models; discipline-specific clash testing; federated-model governance.

===============

A project-closeout handover package should contain verified record models populated with the asset information required by the owner’s operational and facilities-management processes. Depending on the defined information requirements, this may include asset identifiers, classification, manufacturer and model data, installation information, warranty details, maintainability fields, commissioning status, spatial relationships, and links to associated documentation.

The record model must represent the accepted project condition rather than an intermediate coordination state. It should undergo final validation for required parameters, naming, file format, model structure, and information completeness before delivery. Where COBie or another structured asset-data format is required, the embedded model information should correspond with the exported dataset.

Federated clash-detection models and temporary 3D coordination views are process artifacts. They may be archived where the contract or organizational retention policy requires them, but they are not normally the principal operational deliverable. Internal coordination notes likewise document project activity but do not provide the owner with a usable digital representation of the completed facility.

The defining characteristic of a BIM handover deliverable is verified, structured information that supports the owner’s specified post-project uses.

Reference topics: BIM closeout; record models; asset-information requirements; COBie; facilities-management handover; data validation; digital deliverables.

===============

The Model Element Table and LOD matrix define the required progression of geometry and information at the element level. They establish which party is responsible for each model element, the stage at which it must be developed, the required geometric maturity, and the associated non-graphical data needed for coordination, procurement, construction, and asset handover.

This element-specific structure is essential when the owner’s facilities-management system requires defined asset fields and consistent information formats. It prevents teams from assuming that visual completeness automatically means data completeness. For example, an equipment object may appear adequately modelled but still lack classification, manufacturer, serial-number, maintainability, warranty, or commissioning information.

A Master Information Delivery Plan is useful for scheduling broader information exchanges, but it normally operates at the deliverable or task-team level rather than defining detailed information requirements for individual model-element categories. Naming protocols and authoring standards govern production consistency but do not specify who develops each asset and to what information level. A quantity-takeoff checklist is too narrow.

The Model Element Table and LOD matrix therefore provide the clearest mechanism for assigning element ownership and defining required geometry and information through handover.

Reference topics: Model Element Table; LOD matrix; level of information need; asset-data requirements; element responsibility; facilities-management handover.

===============

A complete absence of clashes on a large multidisciplinary retail project is more likely to indicate an input or positioning problem than perfect coordination. The BIM manager should first confirm that every published model uses the approved shared-coordinate system and appears in the correct horizontal position, elevation, and orientation. Models exported using unrelated internal or project coordinates may be separated by a substantial distance in the coordination space, preventing the clash engine from detecting intersections.

After correcting the source models, the teams should republish the designated coordination views and verify visually that the architectural, structural, and building-services models overlay correctly before rerunning clash detection. Publication status, model versions, included geometry, and coordination-space assignments should also be checked.

Adding sheets does not affect three-dimensional clash detection because sheets are documentation containers rather than coordinated model geometry. Proceeding on the assumption that zero results means zero issues would bypass essential input validation. A case study would be inappropriate until the unexpected result has been investigated and confirmed.

The governing principle is that clash results are only reliable when the model inputs, coordinate systems, publication settings, and federation are validated first.

Reference topics: Shared coordinates; model publication; coordination-space validation; clash-detection inputs; federated-model positioning; quality assurance.

===============

A mandatory multidisciplinary review session is the strongest method for ensuring that contributors understand the BEP rather than merely receive it. The session allows the BIM manager to explain model ownership, coordination procedures, file structures, software requirements, information exchanges, quality-control responsibilities, naming conventions, issue workflows, and escalation processes. It also enables each discipline to identify ambiguities and confirm acceptance before implementation begins.

Following review and approval, the BEP should be retained as the official controlled project document in the Common Data Environment. This provides an accessible reference and establishes the approved baseline against which later revisions can be tracked.

Uploading a live copy to a shared folder is necessary for accessibility, but distribution alone does not demonstrate that participants understand their obligations. Including the BEP in the contract provides formal status but does not replace operational onboarding. Email signatures confirm receipt or acknowledgment, not comprehension, and can lead to disconnected copies outside the controlled document environment.

The best process combines formal review, multidisciplinary approval, controlled publication, and ongoing accessibility. Among the available choices, option B most completely addresses understanding, agreement, and official document control.

Reference topics: BIM Execution Plan onboarding; multidisciplinary review; roles and responsibilities; controlled documentation; Common Data Environment; approval and revision management.

A BIM Execution Plan establishes the operational framework by which BIM will be implemented on a project. Two core components are the modeling standards that govern how information is authored and the technology ecosystem that enables production, exchange, review, coordination, and delivery. Modeling standards typically address file structure, naming conventions, model segmentation, coordinates, units, worksharing, content requirements, quality-control procedures, and information expectations. The technology ecosystem identifies approved authoring applications, software versions, cloud platforms, coordination tools, interoperability formats, add-ins, and supporting hardware or infrastructure.

An LOD or level-of-information matrix may be attached to or referenced by the BIM Execution Plan, but general project specifications are contract or technical-design documents rather than defining components of the BEP itself. Likewise, collaboration protocols are normally covered by a BEP, but “project playbook” is not the precise paired component represented by the Autodesk curriculum. A conventional project schedule may influence BIM deliverables, yet it is not equivalent to the BIM production and information-delivery plan.

Therefore, option B contains two elements that directly belong to BIM implementation planning and govern consistent execution across disciplines. These provisions prevent incompatible software, inconsistent modeling practices, and uncontrolled information exchanges.

Reference topics: Corporate BIM standards; BIM Execution Plan development; model-authoring requirements; software and technology planning; interoperability; quality-control standards.

===============