AutoDesk BIM_MGT_101 Exam Questions

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.

The project requires a structured delivery plan that assigns responsibility and timing for each information exchange. The plan must define what information is required, which task team produces it, who verifies and authorizes it, the required format, the delivery milestone, and the receiving party. This is particularly important where design packages overlap and asset-data requirements must develop alongside spatial coordination rather than being added retrospectively.

A task information-delivery plan provides detailed commitments at the team level, while the consolidated information-delivery plan coordinates those commitments across the project. Together they align model production, structured data, coordination submissions, review periods, and final handover requirements.

Allowing each discipline to determine its own formats independently would produce inconsistent data structures and make late consolidation expensive and unreliable. Naming conventions are necessary but represent only one small component of information management. Postponing asset information until construction creates a high risk of missing parameters, unassigned responsibilities, incomplete records, and extensive rework.

The delivery strategy must therefore be established early and integrated with the design programme, BIM Execution Plan, client information requirements, and quality-assurance process.

Reference topics: Task Information Delivery Plans; Master Information Delivery Planning; information-exchange requirements; asset-data handover; structured data; responsibility matrices; delivery milestones.

The existing project levels should be retained because the preset floor plans, reflected ceiling plans, and other level-associated views already placed on sheets depend on them. The BIM manager should align those levels with the authoritative as-built levels and then establish monitoring where appropriate. The linked grids can be created in the host through Copy/Monitor, providing native project grids that correspond to the resource model.

Deleting the template levels would also delete or disrupt dependent views, resulting in precisely the extensive sheet and view reconstruction the question requires the BIM manager to avoid. A Scope Box controls datum extents and view cropping; it does not reconcile level elevations or create coordinated grid elements. Hiding the host levels and displaying only linked datums would leave the host project without properly coordinated native reference elements and would not support reliable modelling or documentation.

After alignment and copying, the team should review Copy/Monitor warnings whenever the linked as-built model changes. This preserves the firm's established documentation infrastructure while integrating authoritative project-specific datum information.

Reference topics: Copy/Monitor; level-associated views; linked as-built models; grid coordination; Revit template reuse; datum management.