Autodesk Updated BIM_MGT_101 Exam Questions and Answers by nela

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 timing of the performance degradation strongly indicates that one or more recently distributed links, or their access paths, should be isolated before undertaking invasive model changes. Opening the project through Specify Worksets allows the BIM manager to control which worksets are loaded. Where Revit links are assigned to dedicated worksets, the manager can initially close those worksets, assess baseline performance, and then load them selectively. If the model performs normally with linked-model worksets closed, the investigation has established a defensible connection between the slowdown and the updated external references.

The Manage Links dialog should then be reviewed for link status, saved paths, path type, file availability, and unexpected network or cloud locations. A valid link may still degrade access when it resolves through an inaccessible, high-latency, or inconsistent location.

Flattening linked geometry is not a standard Revit troubleshooting operation. Removing and recreating every link is unnecessarily destructive and can compromise positioning, visibility overrides, and coordination settings. Consultant warnings may warrant separate health reviews, but indiscriminately fixing every warning is neither an efficient first diagnostic step nor normally within the host team’s model authority.

Reference topics: Linked-model troubleshooting; workset loading; Manage Links; model-performance isolation; distributed-file validation; Revit model health.

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

Exhibit 1 correctly assigns a red dashed line pattern to the Demolished phase status for both Projection/Surface Lines and Cut Lines. This is required because demolished elements may appear either in projection or in section, depending on the view orientation and whether the element is intersected by the view’s cut plane.

Configuring only Projection/Surface Lines would leave demolished elements displayed differently when cut. Conversely, changing only Cut Lines would not produce the required standard in elevations, plans, or other views where the elements are viewed in projection. The phase graphic override must therefore consistently define the colour and line pattern in both graphical conditions.

This setting belongs in the firm’s Revit project template so that future projects inherit the standard. The corresponding phase filters must also be configured to apply the Demolished override in relevant demolition and construction views. A graphic override does not operate independently; the active phase and phase filter determine whether an element is classified and displayed as existing, demolished, new, or temporary.

Reference topics: Revit phasing; Phase Graphic Overrides; demolished-element standards; phase filters; projection and cut graphics; corporate project templates.

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

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.

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