RVT_ELEC_01101 Exam Dumps - Autodesk Certified Professional in Revit for Electrical Design

In the exhibit, the Label Parameters for the electrical device tag are configured as follows:

A white background with black text AI-generated content may be incorrect.

This setup determines how the tag will display in Revit when applied to any device. Specifically:

The Panel parameter (P203 in this case) will be shown first.

A “/” separator follows because it’s assigned as the suffix for the Panel parameter.

The Circuit Number (2,4) is displayed immediately after the slash, with no extra spaces or line breaks.

Since the Break column is unchecked, the values will appear on one continuous line, not split across lines.

Revit documentation for tag creation confirms this behavior:

“When defining label parameters in a tag family, the Prefix and Suffix fields control text that appears before or after the parameter value, while the Break checkbox controls whether the text wraps to a new line.”

Therefore, when the tag is applied to a receptacle on panel P203 and circuit 2,4, the final formatted text will be:

P203/2,4

This corresponds exactly to option B, where the panel and circuit appear on the same line separated by a slash, with no spaces or line breaks.

The exhibit shown displays the Type Properties dialog box for a System Family: Floor Plan view type. Within the “Identity Data” group, there are two critical parameters that govern the behavior of new views created from this view type:

“View Template applied to new views”

“New views are dependent on template”

According to Autodesk Revit’s documentation in the Revit MEP User’s Guide (Chapter 48 “Views and View Templates” and Chapter 49 “Preparing Construction Documents”):

“When a view template is assigned to a view type through the Type Properties dialog, any new view created from that view type automatically receives the defined view template. This ensures consistent visibility, graphics, and discipline settings for all new views.”

In this image, the parameter “View Template applied to new views” is set to Electrical Plan, and “New views are dependent on template” is checked. This means that any new floor plan created using this type will automatically have the Electrical Plan template applied, and the view will be dependent on that template, meaning it inherits all its visibility and annotation control settings.

This ensures that all electrical floor plan views generated are standardized and visually consistent, a fundamental practice in Revit Electrical Design workflows, as described in the Smithsonian Facilities Revit Template User’s Guide:

“Assigning a default view template to a view type (e.g., Electrical Plan) ensures every new view created follows organizational and graphical standards without manual setup.”

Option A matches this behavior exactly.

Option B is incorrect** because Revit does not create a new template automatically.

Option C is incorrect** because duplication of an existing view does not reassign templates by type.

Option D is incorrect** because dependent view creation requires a specific “Duplicate as Dependent” command, not this setting.

The warning message — “Can’t create this kind of element in this view in the current mode” — appears when an electrical designer attempts to place a Generic Annotation family inside a model family (e.g., a data device or electrical fixture) that is not configured to host annotation elements.

According to the Revit Electrical Design documentation, Generic Annotation families are 2D annotation elements, and therefore, cannot be created or viewed in 3D model views unless configured as “Shared.” The official guide clarifies:

“You can create generic annotation families and nest them inside host model families so that the annotations display in the project.”

However, this only functions correctly if the annotation is enabled to act independently within the host:

“To allow a nested annotation to be visible and editable when placed in a host model family, the nested annotation must be set to Shared before loading it into the host.”

If the nested annotation is not set to Shared, Revit cannot create or display it in the host’s model view, triggering this exact warning.

Thus, the correct workflow is:

Open the Generic Annotation family in the Family Editor.

Go to Family Category and Parameters.

Check the box “Shared” under Family Parameters.

Save and reload the family into the host electrical device family.

Other options—changing view level, detail level, or annotation orientation—do not resolve this placement restriction.

In Autodesk Revit Electrical Design, revisions are managed using the Sheet Issues/Revisions dialog to track changes and document issuance phases, such as “Issued for Bid” or “Issued for Construction.” The revision schedule on the title block automatically reflects this data when configured correctly.

According to the Revit MEP User’s Guide (Chapter 48 “Construction Documentation – Managing Sheets and Revisions”):

“Revisions define a record of changes issued with sheets. To display a revision in the title block, it must first be created in the Sheet Issues/Revisions dialog, assigned a description, and set to be shown in the revision schedule.”

Here’s how the process works step-by-step:

1️⃣ Add a new revision in the Sheet Issues/Revisions dialog.

Navigate to View tab → Sheet Composition panel → Revisions.

Add a new revision line entry (this creates a new revision record).

2️⃣ Change the Description to “Issued for Bid”.

In the same dialog, edit the Description field to reflect the issuance purpose.

3️⃣ Select Shown in Revision Schedule next to “Issued for Bid”.

Check “Show” in the Revision Schedule column so it will appear in the title block’s revision schedule table.

4️⃣ For each sheet to be issued, click Edit next to Revisions on Sheet in the Properties palette.

In the Properties palette, under Identity Data, click Revisions on Sheet → Edit and assign the “Issued for Bid” revision only to the sheets being released.

This ensures only the selected sheets display the “Issued for Bid” entry, maintaining proper control over which drawings are issued while others remain unaffected.

As described in the Smithsonian Facilities Revit Template User’s Guide:

“Revision schedules are dynamically linked to sheet issue data. Designers can show or hide revisions on a per-sheet basis by editing ‘Revisions on Sheet’ from the Properties palette.”

In Revit, when editing a family in the Family Editor and reloading it into a project, Revit handles type changes using specific update rules. Types that are renamed overwrite their earlier version in the project because they retain the same internal type ID. Types that are added to the family also appear in the project once reloaded.

Initially, the family contains two types:

Above Counter

Plain

The changes made in the Family Editor are:

1️⃣ Rename Plain → Standard

2️⃣ Add a new type named GFCI

According to documented Revit behavior for type updates:

“When a family is reloaded into the project, any renamed family type replaces its previous version while maintaining its parameter assignments. Newly created types are added as additional family types available for placement within the project.”

Therefore:

Plain no longer exists because it was renamed

Standard now exists in its place

GFCI is added as a new family type

Above Counter remains unchanged

Thus, the family in the project now contains:

✅ Above Counter

✅ GFCI

✅ Standard

📘 This matches answer choice:

B. Above Counter, GFCI, Standard

In Autodesk Revit MEP Electrical Design, the System Browser is used to analyze and verify electrical systems, including panelboard connections, circuit hierarchies, and connected loads.

From the exhibit, the Properties palette shows that the selected equipment is a Lighting and Appliance Panelboard (208V MLO, 100A), named P4. To determine the parent panel that feeds Panel P4, we refer to the System Browser, which organizes the entire electrical distribution network hierarchically under the Electrical discipline.

In the System Browser on the right, under the Electrical category, we can observe that Panel P4 is nested directly under Panel P2. This organization indicates that P4 is circuited to (or fed from) Panel P2.

According to the Revit MEP 2011 User’s Guide, Chapter 4, “Electrical Systems—Using the System Browser,” it states:

“The System Browser displays electrical systems in a tree structure. Each subpanel or device listed beneath a main panel is connected to that panel through an electrical circuit. When a panelboard appears under another, it indicates the subpanel is fed from that parent panel.”

This is further reinforced in Smithsonian Facilities Revit Electrical Template Documentation (April 2021), Section 8.3 “Documentation Views,” which describes:

“Panel schedules and browser hierarchies show the distribution sequence. Subpanels appear indented beneath their source panel, indicating electrical dependency and circuit assignment.”

Therefore, by interpreting both the Revit interface and Autodesk’s documentation, Panel P4 is a subpanel connected to Panel P2, confirming that its electrical feed is assigned from Panel P2.

Final Verified Answer: B. Panel P2

Reference Sources:

Autodesk Revit MEP 2011 User’s Guide, Chapter 4 — Electrical Systems and the System Browser

Smithsonian Facilities Revit Template User’s Guide, Section 8.3 — Electrical and Fire Alarm Templates: Documentation Views

When working on linked architectural and electrical Revit models, the Copy/Monitor tool enables electrical designers to copy selected elements (such as lighting or electrical fixtures) from the architectural model into their electrical model. This workflow ensures that any subsequent modifications to these elements in the architectural file are automatically detected and flagged for coordination review.

According to the Revit MEP User’s Guide (Chapter 46 “Copy/Monitor and Coordination Review”):

“Use Copy/Monitor to copy elements from a linked model so that changes to the original elements are tracked. When copying multiple similar elements, select Allow batch copy to automatically copy all instances of that category.”

The Coordination Settings dialog provides two primary behavioral controls for each category (such as Electrical Fixtures):

1️⃣ Copy Behavior

Allow batch copy: Automatically copies all elements of the selected category from the linked architectural model to the host electrical model.

This option is ideal for electrical fixtures because it ensures all instances are copied efficiently without manual selection and allows future synchronization.

2️⃣ Mapping Behavior

Copy original: Creates an exact duplicate of the architectural family in the electrical model without substituting family types or parameters.

This ensures full fidelity with the architect’s fixtures and enables Revit to automatically detect newly added or modified elements in the linked model for coordination review.

The Smithsonian Facilities Revit Template User’s Guide also confirms this workflow:

“Set Copy Behavior to Allow batch copy and Mapping Behavior to Copy original when monitoring shared architectural elements like lighting fixtures, ensuring accurate duplication and automatic update tracking.”

These settings allow Revit to issue coordination warnings such as “Instance of link needs Coordination Review” whenever the architectural model is updated, maintaining synchronization across disciplines.

In Autodesk Revit Electrical Design, lighting control systems such as single-pole, three-way, and four-way switches are managed using Switch Systems. These systems logically connect lighting devices (switches) to the lighting fixtures they control. For multiple switches (like three-way configurations) to be part of the same control circuit, they must share the same Switch ID value.

In the exhibit, the electrical designer is attempting to add a three-way switch to the existing switch system labeled “b”, but Revit does not allow it. The reason is that the Switch ID parameter of the new switch does not match the Switch ID of the system it is intended to join.

The Switch ID acts as the unique identifier that links all switches controlling the same group of fixtures. If the IDs differ (for example, “b3” versus “b”), Revit interprets them as belonging to separate systems and prevents them from being grouped together.

The Autodesk Revit MEP User’s Guide – Electrical Systems: Lighting and Switch Systems explains this clearly:

“Switch systems are organized by Switch ID. All switches controlling the same lighting circuit must have identical Switch ID values. Revit will not allow a switch to be added to an existing system if its Switch ID does not match that system’s identifier.”

To fix this, the designer must:

1️⃣ Select the three-way switch.

2️⃣ In the Properties palette, locate the Switch ID parameter.

3️⃣ Change its value to match the target switch system’s ID (in this case, “b”).

Once both switches share the same Switch ID, Revit will successfully include them in the same Switch System.