Free Autodesk BIM_MGT_101 Practice Exam with Questions & Answers | Set: 2

A prospective fabricator who is not a project member should receive information through a controlled external-sharing process rather than being granted ordinary project-folder access. Enabling public sharing permits authorized files to be distributed externally, while a transmittal creates a formal record of what was issued, when it was issued, and to whom.

The BIM manager should select only the documents required for the bidding process, confirm that external sharing is permitted by the project’s information-governance procedures, and establish any applicable expiration, download, or access controls. A transmittal also provides a traceable issue package and reduces ambiguity regarding which file versions formed the basis of the recipient’s bid.

Setting folder permissions to Everyone generally applies to eligible users within the project environment; it does not provide a properly controlled method for distributing information to unknown external parties. Audit and Compact is a Revit model-maintenance operation unrelated to access. Centralizing a model and creating local files concerns traditional worksharing and would be inappropriate for bidders who are not authorized project contributors.

External sharing must remain limited, deliberate, and auditable.

Reference topics: Public file sharing; transmittals; non-member access; external bidding packages; Common Data Environment security; controlled information exchange.

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

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.

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

A model checker or structured data-validation tool provides the repeatable, rules-based assessment required for this scenario. The BIM manager can configure checks against the project’s naming standard, required COBie fields, shared-parameter bindings, permissible values, and Model Element Table requirements. The resulting report identifies missing, invalid, or inconsistent information by category and element, creating an auditable basis for corrective action before coordination or information delivery.

Manual element-by-element inspection is slow, difficult to reproduce, and vulnerable to omissions, particularly in large models. It also provides weak evidence that the complete model was evaluated consistently. Verbal clarification is not an acceptable substitute for documented information requirements, and asking for another export without first identifying the specific failures is inefficient. Hiding incomplete elements does not correct their data and may conceal deficiencies from coordination participants.

Systematic validation also allows the BIM manager to compare successive submissions, monitor closure rates, and distinguish modelling defects from information-quality failures. This is especially important where downstream COBie or asset-data deliverables depend on consistent parameter structures rather than visual model appearance alone.

Reference topics: Automated model checking; COBie; Model Element Tables; shared-parameter validation; naming standards; quality assurance; information-completeness assessment.

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

Models approaching 1 GB represent a significant operational risk, particularly when the project has already missed a major documentation milestone. The BIM manager should coordinate a controlled health-improvement programme with the project team rather than make unilateral changes. This includes reviewing and purging genuinely unused content, removing redundant views, evaluating imported files and excessive families, and prioritizing warnings that affect performance, accuracy, or documentation reliability.

Purging must be performed carefully because apparently unused content may still be required for future deliverables or corporate standards. The team should preserve backups and validate the model after each significant cleanup operation.

Creating a separate sheet model is a major restructuring decision and should not be imposed merely because of file size. Daily auditing and compacting can add unnecessary disruption and does not correct poor authoring practices. Ignoring the problem because users have not formally complained is unacceptable; the missed deadline and excessive model size are objective warning signs. Assigning several BIM managers to eliminate every warning is also disproportionate because not all warnings carry equal risk.

Reference topics: Model-health management; Revit file-size control; Purge Unused; view management; warning prioritization; project-team coordination; performance risk.

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

The Show function is the appropriate diagnostic action because it locates and highlights the elements associated with the selected warning in the active graphical view. The design team can then inspect each affected Room Tag, confirm the relationship between the tag and its room boundary, and determine whether the tag should be repositioned inside the room or displayed outside the room with a leader.

The warning does not necessarily indicate invalid room data. It identifies an annotation condition in which the Room Tag’s insertion point is outside the room it references. This commonly occurs where the room is narrow, irregularly shaped, crowded with documentation, or too small to contain the complete tag symbol. Each occurrence must therefore be visually assessed rather than handled through a blanket deletion or suppression process.

Export produces an external warning report for review; it does not move warnings out of the model or identify the affected annotation graphically. Close exits the dialog without investigating the condition. Delete Checked risks deleting associated model elements and is not an appropriate method for correcting annotation placement.

Using Show supports controlled warning resolution, preserves the room and tag data, and allows the team to apply a leader only where required.

Reference topics: Revit model-health review; warning management; annotation quality control; Room Tags; graphical element identification; model auditing procedures.

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

The BIM manager should first create a controlled package containing only the models, documents, and supporting information required for the interior-partition scope. A package establishes a defined information exchange and prevents subcontractors from relying on unrelated or uncontrolled project content.

Role-based permissions and folder-level access must then be configured according to the principle of least privilege. The subcontractors should receive only the minimum viewing, downloading, uploading, or editing rights necessary to perform their contractual tasks. Structural, MEP, scheduling, commercial, and other restricted folders should remain inaccessible rather than merely hidden within a broader model set.

Watermarking does not prevent unauthorized viewing or access. Granting full project access and relying on verbal instructions provides no enforceable technical control and creates an unacceptable information-security risk. Hiding coordination issues is unrelated to controlling access to model files and may obstruct legitimate issue resolution within the subcontractors’ assigned scope.

The BIM manager should test the permissions using an equivalent user role, confirm that inherited folder permissions do not expose restricted information, and document the approved access configuration as part of the onboarding record.

Reference topics: Common Data Environment security; role-based access; folder permissions; information packages; least-privilege access; subcontractor onboarding.

The project should retain a common View Template for consistent graphics, visibility, filters, discipline settings, detail level, and other documentation standards, while excluding View Range from the parameters controlled by that template. Deselecting the corresponding Include checkbox allows each floor-plan view to maintain a level-specific View Range without losing the other standardized template settings.

Plan Regions are intended for localized conditions within a plan, such as a raised platform, clerestory, split level, or isolated area requiring a different cut plane. They are not an efficient substitute when the entire floor requires a different View Range because its floor-to-floor height differs from other levels.

Removing the View Template would weaken graphical and documentation consistency. Visibility/Graphics also does not control the View Range; it controls the visibility and appearance of categories and elements. Creating a separate template for every floor would produce unnecessary template proliferation and increase maintenance risk because future standard changes would need to be repeated across numerous nearly identical templates.

Excluding only the variable parameter provides the correct balance between corporate standardization and project-specific view configuration.

Reference topics: View Templates; View Range; template-controlled parameters; Plan Regions; floor-plan standards; graphical consistency.

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