- Which action should the user take?
Answer: Change View Scale directly in the view Properties palette and leave the assigned template in place.
When working with view templates in Revit, the key concept to understand is the Include column: only parameters with a checkmark in the Include column are controlled — and locked — by the template. Parameters that are not included remain freely editable on a per-view basis, even while the template is still assigned.
In this scenario, View Scale is not selected in the template's Include column. That means Revit does not override or lock that parameter through the template. You can simply open the view's Properties palette and change the scale from 1:100 to 1:50 directly — the template remains assigned and continues enforcing Visibility/Graphics Overrides and Detail Level as intended. Option A is exactly this approach, and it's the cleanest, safest solution.
Option B is unnecessarily destructive. Removing the template breaks the link to office standards, and "Apply Template Properties" is a one-time snapshot — it won't maintain a live connection for future updates. Option C would change the scale for every view that uses the "MEP Coordination" template, violating the requirement to change only this one plan — a classic over-reach mistake. Option D is also overkill; duplicating the template and disabling Visibility/Graphics Overrides would undermine the office graphics standards you're specifically trying to preserve, and it still doesn't address the actual problem cleanly.
Study tip: On Revit exam questions involving view templates, always check what is — and isn't — in the Include column before deciding on an action. If a parameter isn't included, you can edit it freely on individual views without touching the template at all.
- What is the most appropriate way to permit a view-specific filter configuration while retaining the template's other standards?
Answer: Clear the Include setting for V/G Overrides Filters in the template, then configure filters in the individual view.
When working with view templates in Revit, you need to understand that each template parameter has an Include checkbox. When that checkbox is enabled for a category like V/G Overrides Filters, the template controls that setting across all assigned views — which is exactly why the filter controls appear grayed out and unavailable to the user in this scenario.
The solution described in A is correct: by clearing the Include checkbox for V/G Overrides Filters in the view template, you "release" that specific parameter back to view-level control. The template continues to govern every other included setting (line weights, model categories, annotation categories, etc.), so your project standards remain intact. The individual view then becomes free to have its own filter configuration.
B is a destructive approach — deleting a filter from the project removes it from every view and filter list that references it, which could break standards across the entire model. This is disproportionate and unnecessary.
C is a red herring. The Discipline property controls which categories are visible by default (Architectural, Structural, etc.), but it has no effect on whether a view template's filter overrides are editable. Changing Discipline won't unlock the filter controls.
D misunderstands how templates work. Re-applying a template doesn't grant view-level independence, and removing a template from the Project Browser deletes it entirely, affecting every view it was assigned to — a serious unintended consequence.
The key study tip here: Include checkboxes are the "on/off switch" for template control per parameter. Anytime a view setting is locked, ask yourself which template parameter's Include checkbox needs to be cleared.
- Which workflow best meets this requirement?
Answer: Enable Temporary View Properties, select "Coordination Review," and later restore the view properties.
Whenever you see a Revit question about temporarily changing how a view looks without permanently altering its settings, think about the Temporary View Properties feature — it's specifically designed for exactly this use case.
Temporary View Properties allows you to override a view's template settings on a short-term basis. When you enable it and select a different view template (like "Coordination Review"), Revit applies those display settings only for your current working session or until you explicitly restore the original. The key button — Restore View Properties — resets everything back to the originally assigned template ("Construction Plan") with a single click, leaving the view permanently unchanged. This makes option D the correct workflow: it's non-destructive, reversible, and purpose-built for temporary display changes.
Option A avoids touching the original view, which is good thinking, but duplicating and deleting a view is unnecessary overhead. It also risks forgetting to delete the copy, cluttering the project browser. Option B is the most dangerous choice — reassigning the template permanently changes the view's configuration, and manually reassigning it afterward introduces room for error. If you forget or reassign incorrectly, the original appearance is compromised. Option C seems clever, but Undo is unreliable here because it depends on an unbroken action history. Any saves, synchronizations, or intervening edits between applying the template and finishing coordination could make Undo unavailable or cause unintended reversals of legitimate work.
As a study tip: on the Revit exam, whenever a question emphasizes temporary or without permanent changes, your first instinct should be Temporary View Properties — it's Revit's built-in solution for non-destructive view adjustments.
- Which views update automatically as a direct result of editing the original template?
Answer: Plan A only, because it is the only view still assigned to the edited original template.
When working with view templates in Revit, the critical distinction is between assignment and application. A view template can relate to a view in two fundamentally different ways, and this question tests whether you understand that difference.
In Revit, when a template is assigned to a view, that view maintains a live connection to the template. Any edits made to the template propagate automatically to all views currently assigned to it. This is the active, ongoing relationship. Plan A holds this relationship with "Permit Plan," so it updates automatically when the manager hides demolition categories — making A the correct answer.
Choice B is tempting but represents a common misconception. "Apply Template Properties" is a one-time action that copies the template's settings into the view at that moment, like a paste operation. Plan B received those settings historically, but no live link remains. Editing the original template afterward has zero effect on Plan B.
Choice C misunderstands how duplicating a template works. When you duplicate a view template in Revit, you create a completely independent copy. "Permit Plan - Copy" shares no dynamic link with the original "Permit Plan." Changes to one do not affect the other, so Plan C is unaffected.
Choice D invents a synchronization behavior that does not exist in Revit. Templates do not stay synchronized based on matching initial settings — that would require an explicit assignment relationship, which none of these views share except Plan A.
Your study tip: always ask yourself whether a view is assigned to a template (live link) or merely had a template applied (one-time copy). That distinction drives almost every template-related question you'll encounter.
- Which result should the architect expect without additional manual work?
Answer: The scale, detail level, category visibility, and filters can be standardized, but the crop boundary extents are not copied.
When working with Revit view templates, it helps to understand exactly what they control — and what they intentionally leave out. View templates are designed to standardize the appearance and display settings of views, not their spatial boundaries.
A view template captures settings like scale, detail level, model-category visibility/graphics overrides, annotation category visibility, and filters — all the properties that govern how elements are displayed. When you assign a template to multiple floor plans, those properties propagate consistently across every assigned view. This makes D the correct answer: scale, detail level, category visibility, and filters are all standardized, but the crop boundary extents are deliberately excluded. Crop regions define what portion of the model a view shows, which varies depending on the floor plan's purpose — cropping one view the same as another would make little sense architecturally.
Answer A is wrong because scale is absolutely stored in and applied by view templates — it's one of the most common reasons architects use them. Answer B sounds appealing because it promises complete standardization, but the crop boundary is a spatial property tied to each view individually, not a display setting, so it is never copied by the template. Answer C gets it backwards — visibility settings are very much part of what view templates store and apply; the misconception here is exactly the kind of trap Revit questions often set.
For your exam, remember this rule: view templates control how a view looks, not where it looks. If a setting defines the region of the model being shown (crop boundary), the template won't touch it.
- Which configuration should be made?
Answer: Set "Office Working Plan" as the default view template on the "Working Plan" view type so that each new view is automatically assigned and associated with the template.
When you see a question about automating view settings in Revit, focus on the distinction between assigning a template (a one-time copy of settings) and associating a view with a template (a live link that updates when the template changes). This question tests exactly that distinction, plus where in Revit you configure default behavior for an entire view type.
The correct approach is C: setting "Office Working Plan" as the default view template directly on the "Working Plan" view type. In Revit, you can open View Types (via the View Template settings on the type properties) and designate a default template. Every new view created from that type is automatically assigned and linked to that template, meaning future edits to the template propagate to those views automatically — precisely what the scenario requires.
Answer A is wrong because assigning the template to a starting view only affects that one view's initial display; it does nothing to automate template assignment for future views of the type. Answer B creates unnecessary duplication and still doesn't establish an automatic link — duplicating a view type doesn't configure a default template on it, so new views still won't receive it automatically. Answer D describes applying template settings to the view type definition so views inherit settings once but lose the ongoing link — this breaks the requirement that future template edits should update new views.
As a study tip, remember the key phrase: default view template on the view type = automatic assignment + live association. If a question asks for automation and ongoing updates, you need the view-type-level default setting, not a manual one-time application.
- How should this proposal be evaluated?
Answer: The template can standardize category visibility, but the missing tags must still be placed or generated separately.
When you see a question about view templates in Revit, anchor your thinking to one fundamental rule: view templates control visibility and graphics settings, not content creation. They govern what you can see in a view, not what exists in the model or on the sheet.
This distinction makes C the correct evaluation. A view template can absolutely standardize category visibility — ensuring Lighting Fixtures, Lighting Fixture Tags, and other annotation categories display consistently across all reflected ceiling plans. However, if light-fixture tags are simply absent from those views, no template setting will generate them. Tags must be placed manually (using the Tag All or individual Tag commands) or through other workflows like tag propagation. The template has no mechanism to create annotations that don't yet exist.
Choice A is a red herring — view scale can affect tag size and legibility, but template assignment is not gated by whether the template scale matches the view scale. Choice B describes a plausible-sounding condition, but making a category visible only reveals existing tags; it cannot summon tags into existence. Many students confuse "visibility enabled" with "tags present," which is exactly the trap B sets. Choice D introduces Annotation Crop, which controls whether annotations outside the crop boundary are shown — enabling it still cannot place tags that were never added to the view.
A useful study tip: on Revit exam questions, always distinguish between visibility settings (what the template controls) and model/annotation content (what must be placed independently). If a question implies a template can create elements, that answer is almost certainly wrong.
- What happens to the assigned plans?
Answer: Their Detail Level changes to Fine, while each plan retains its existing Model Display setting.
Whenever you see a question about View Templates in Revit, focus on one critical distinction: included properties versus excluded properties. When a property is included in a template, the template owns that value — it controls it and pushes updates to every assigned view. When a property is excluded, the template releases control of it, meaning each view manages that setting independently.
In this scenario, Detail Level is included, so the template has authority over it. When the manager updates Detail Level from Medium to Fine, every view assigned to "Presentation Plan" immediately inherits the new value — that's the whole point of included properties. Model Display, however, is excluded, meaning the template has no control over it. Changing Model Display within the template's definition has no effect on assigned views, because those views are free to maintain their own independent Model Display settings. This confirms answer B as correct.
Answer A is wrong because it assumes all template values propagate equally — but only included properties are enforced across assigned views. Answer C reverses the logic: it credits Model Display (the excluded property) with propagating and ignores Detail Level (the included property), which is backwards. Answer D is wrong because Revit applies included-property changes automatically and live — you don't need to manually reapply a template for updates to take effect on already-assigned views.
Study tip: On Revit exam questions about View Templates, always identify which properties are included vs. excluded before predicting behavior. Included = template controls it; excluded = view controls it independently.
- Which approach is most appropriate?
Answer: Duplicate the general template, adjust the enlarged-plan settings, and assign the duplicate to enlarged plans.
When managing view templates in Revit, the core question is always: how do you balance consistency with flexibility while keeping future maintenance manageable? View templates work by pushing a defined set of properties onto views, so the architecture of your templates directly determines how much work a future standard change creates.
Duplicating the general template and adjusting only the scale and crop-region visibility — answer B — is the correct approach. The duplicate inherits all category visibility, filters, and detail level settings, so enlarged plans stay visually consistent with general plans. Critically, when the office updates shared graphics standards, only the parent template needs changing; the duplicate simply needs the same targeted update, keeping maintenance predictable and scoped.
Answer A is a trap: Revit allows only one view template assigned per view. You cannot stack templates the way the answer implies, so this workflow doesn't exist in the software.
Answer C sounds efficient but is dangerous. Removing the template from enlarged plans means those views are no longer governed — any future standard update won't propagate to them automatically, which directly violates the office's maintainability goal.
Answer D describes a manual, error-prone process. Temporarily editing a shared template, assigning it, then restoring original settings risks corrupting every other view that template controls. It also scales poorly and is the opposite of a sustainable workflow.
The study tip here: on Revit exam questions involving templates, always ask "does this approach survive a future change gracefully?" If the workflow requires manual cleanup or doesn't leverage template inheritance, it's almost certainly wrong.
- Which workflow satisfies both requirements?
Answer: Assign the template to Elevation 1, and use Apply Template Properties once on Elevation 2.
When working with view templates in Revit, you need to understand the critical difference between two methods of applying them: assigning a template (creating a live link) versus using Apply Template Properties (a one-time snapshot).
Assigning a view template to a view creates a persistent connection — whenever the template is updated, the view automatically inherits those changes. This is exactly what Elevation 1 needs. Apply Template Properties, by contrast, copies the template's current settings into the view at that moment, then severs the connection entirely. The view becomes fully independent, free to be modified property by property afterward. This is precisely what Elevation 2 requires: match the template initially, then remain editable without any ongoing link.
Option A correctly pairs each method to the right elevation — Elevation 1 gets the live assignment, Elevation 2 gets the one-time application — satisfying both conditions perfectly.
Option B reverses the assignments, so Elevation 2 would stay locked to the template's future changes while Elevation 1 would be frozen at the initial snapshot. This is the opposite of what's needed.
Option C assigns the template to both views but only renames the copy used by Elevation 2 — it doesn't break the live link for Elevation 2. Both views would still update when their respective templates change, leaving Elevation 2 without true independence.
Option D applies a one-time snapshot to both views, so neither elevation would receive future template changes. Elevation 1's requirement is unmet from the start.
Remember this pattern: assigned = live link, Apply Template Properties = one-time copy. Exam questions often test whether you can match each method to the correct use case.
