AutoDesk BIM_MGT_101 Exam Questions

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.

The BIM manager should generate an access or permissions report directly from the Autodesk cloud platform. The platform is the authoritative source for project members, folder access levels, assigned roles, and permission configurations. Exporting the report preserves the relationship between the reported information and the actual project configuration while providing the project manager with a format that can be reviewed without navigating the cloud administration interface.

A manually created Word document or spreadsheet would only be a secondary transcription of the permissions. Such records can become inaccurate when users are added, removed, or reassigned, and they provide weaker traceability than a system-generated report. A Revit Show History report records model synchronization activity and user interactions with a workshared model; it does not report cloud-folder permissions.

The exported report should be reviewed for unnecessary access, inconsistent folder inheritance, external-user permissions, and whether each team member has only the level of access required by their role. The BIM manager should also retain the report as part of the project's information-governance and audit records.

Reference topics: Common Data Environment permissions; cloud-user administration; access reporting; information security; role-based access; project audits.

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.

The designer should inspect the view's Visibility/Graphics settings. Area Lines, also referred to as Area Boundary Lines, are view-specific elements whose visibility can be controlled by the active view, an applied view template, or category-level visibility settings. If the applicable line category is disabled, Revit can create the boundaries successfully while warning that the newly created elements are not visible in the current Area Plan.

The review should include the Model Categories and Annotation Categories tabs, any active view filters, temporary hide/isolate status, and the view template controlling the Area Plan. Where a template governs visibility, the correction should normally be made in the template rather than as an isolated view override, particularly when the same standard must apply to multiple Area Plans.

A Plan Region changes the local view range and does not govern Area Boundary Line visibility. Detail Level affects how certain model geometry is represented but does not normally suppress Area Lines. The Area Scheme determines the type and organizational purpose of an Area Plan, such as Gross Building or Rentable Area, but it is not the direct location for correcting hidden linework.

Reference topics: Area Plans; Area Boundary Lines; Visibility/Graphics; view templates; view-specific elements; graphical troubleshooting.

A custom coordination view should be created using the applicable published mechanical and structural models and limited to the patient-room zones required by the approved clash matrix. The clash results can then be filtered by model pair, location, object category, and active status before the filtered list is exported. This produces a targeted report containing only the coordination conditions requested by the project leads.

The custom-view approach maintains the relationship between the clash records and the coordinated model geometry. It also makes the review repeatable: the BIM manager can return to the saved view during subsequent coordination cycles and evaluate whether the same discipline and location criteria have been resolved.

Asking individual disciplines to prepare independent reports creates inconsistent evaluation criteria and weakens the centralized coordination record. Exporting every clash and manually filtering the spreadsheet introduces unnecessary effort and increases the risk of omitting or misclassifying issues. Assigning clashes through the Issues tool is appropriate after clashes have been reviewed and determined to require action, but assignment does not itself generate the requested filtered clash report.

Reference topics: Autodesk Model Coordination; custom coordination views; clash filtering; clash matrices; published models; active-clash reporting; location-based coordination.