Free Practice Questions for Autodesk BIM_MGT_101 Exam

Step 1: Reset the coordinates of the model.

Step 2: Link in by current coordinates.

Step 3: Acquire coordinates from the updated property boundary resource file.

Step 4: Update the Shared Site of each link copy.

The existing shared-coordinate relationship must first be cleared because the authoritative civil background now contains revised GIS positioning. Resetting the model coordinates removes the obsolete relationship and prepares the architectural model to establish a new shared-coordinate system without physically moving its authored building geometry.

The updated property-boundary or civil resource is then linked using its current positioning so that it can serve as the authoritative coordinate source. Once the updated reference is correctly positioned, the architectural model acquires coordinates from that file. Acquiring coordinates transfers the civil model’s survey-coordinate definition into the host while preserving the architectural model’s internal origin and local modelling arrangement.

The final step is to update the Shared Site assigned to each duplicated building-link instance. This is necessary because multiple copies of the same building model may occupy different campus locations or orientations. Each link instance must reference the appropriate named site position so that the copies remain correctly placed after the revised GIS coordinate system is adopted.

Changing link sites before updating the host coordinate framework would apply positions against outdated coordinate data and could displace the campus federation.

Reference topics: Shared coordinates; Acquire Coordinates; named Shared Sites; campus model assembly; GIS and civil-reference updates; duplicated Revit links.

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

The Survey Point represents the shared real-world or site coordinate framework. Placing or defining it consistently at the common site origin allows every building model to relate to the same survey reference for federation, site plans, civil coordination, and geographically consistent exports.

Each building should retain its own Project Base Point because this point supports the building’s local project-coordinate framework. A building may use a convenient internal datum and orientation suited to its grids, geometry, and documentation while still maintaining a transformation to the common survey system. This separation allows the buildings to remain independently manageable without losing site-wide positional accuracy.

Placing every Project Base Point at the shared site origin would eliminate the intended distinction between each building’s local coordinate basis and the common site reference. Likewise, using a single Project Base Point across all separate models is not how Revit coordinate systems operate; each model has its own internal origin, Project Base Point, and Survey Point. Option B is imprecise because the requirement is not to establish unrelated Survey Points, but to align the models to one shared site origin.

The correct arrangement is a common Survey Point reference combined with a locally appropriate Project Base Point for each building.

Reference topics: Survey Point; Project Base Point; multi-building coordination; local versus shared coordinates; site federation; building-specific origins.

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

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.

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

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.

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

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 revised BEP must be distributed to every party whose work or information access is governed by it, including consultants already modelling, late-onboarding participants, and relevant external stakeholders. Formal distribution with confirmation of receipt establishes that each organization has received the current requirements and understands its modelling scope, coordination obligations, information exchanges, approval responsibilities, and communication procedures.

The controlled copy should also be stored in the project’s Common Data Environment. Uploading it to the shared data-management location provides centralized access, version history, revision traceability, and a consistent source of truth. The BIM manager must verify that each stakeholder has appropriate folder permissions rather than assuming that uploading the document automatically makes it accessible.

Issuing the BEP only to newly onboarded consultants would leave existing participants working under obsolete requirements. A contractual addendum may be required when the revision changes contractual obligations, but it is not automatically the correct mechanism for routine distribution management. Delaying access until construction coordination would undermine design-stage coordination and prevent external stakeholders from following the approved procedures.

Reference topics: BEP distribution; document control; Common Data Environment; version management; stakeholder access; receipt confirmation; project onboarding.

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

The question marks indicate that the title block contains labels referencing custom shared parameters, but the project does not contain the corresponding parameter bindings needed to supply their values. The parameters must be added to the project and associated with the appropriate category—principally Project Information when the value must be common to all sheets. Once the same shared-parameter definitions are bound correctly, users can enter the values through Project Information and the title block labels will display them.

Loading a title block family containing shared-parameter labels does not automatically establish every required project-level parameter binding. The family carries the label definition, but the project must also expose the parameter in the correct data context. The shared parameter’s identity must remain consistent so the label and project parameter reference the same underlying definition.

Option B is inconsistent with the scenario because the family already contains functioning parameter labels. If ordinary text had been used instead of labels, the fields would display fixed text rather than unresolved question marks. Overwriting standard Sheet or Project Information fields would not explain why custom parameter labels remain unresolved.

Reference topics: Shared parameters; title block families; Project Information parameters; category binding; label creation; client content standards.

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