A blueprint has a configlet that includes a command with a variable for a VLAN ID. The engineer wants the VLAN ID to be different for each leaf switch. How should the engineer configure this?

Hardcode the VLAN ID in the configlet and attach it to all leaf switches.

Use a single property set with one VLAN ID and attach it to all leaf switches.

Create a separate configlet for each leaf switch with the VLAN ID hardcoded.

Create a property set with a VLAN ID variable and attach it to each leaf switch with a different value.

After selecting the rack type, what is the next step in integrating the rack into the blueprint design?

Revert the blueprint to a previous state

Add devices to the rack and configure their connections

Publish the blueprint immediately

What is the first step when adding a rack to a blueprint?

Select the rack type from the available options

Configure the network connections for the rack

A blueprint includes generic systems (firewalls) that need a management IP and a specific configuration snippet. The engineer wants to define the management IPs in a property set and the snippet in a configlet. However, the configlet needs to reference the management IP from the property set. What is the correct way to achieve this?

Attach the property set to the generic system and reference the property in the configlet.

Hardcode the management IP in the configlet and attach it to the generic system.

Attach the configlet to the property set instead of the generic system.

Create a separate property set for each generic system and reference it in the configlet.

An engineer has made several changes to a blueprint, including adding a new leaf switch and modifying a property set. The engineer wants to revert the property set change but keep the leaf switch. What is the best way to do this?

Use the 'Discard Changes' option to revert all uncommitted changes, then reapply the leaf switch.

Revert the entire blueprint to the last committed version, then re-add the leaf switch.

Create a new blueprint from the current one and revert the property set in the new blueprint.

Edit the property set back to its original values manually.

Juniper NetworksCertified Specialist, Data Center (JNCIS-DC)

Domain 5Objective 2

Blueprint Modification and Management JN0-481 Practice Questions (Page 4)

Part of the Blueprint Operations domain, which makes up ~10% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–2 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

6concepts

Questions 16–20

16expert · hard
A blueprint has a configlet that includes a command with a variable for a VLAN ID. The engineer wants the VLAN ID to be different for each leaf switch. How should the engineer configure this?
Select an answer first
17foundation · easy
After selecting the rack type, what is the next step in integrating the rack into the blueprint design?
Select an answer first
18foundation · easy
What is the first step when adding a rack to a blueprint?
Select an answer first
19expert · hard
A blueprint includes generic systems (firewalls) that need a management IP and a specific configuration snippet. The engineer wants to define the management IPs in a property set and the snippet in a configlet. However, the configlet needs to reference the management IP from the property set. What is the correct way to achieve this?
Select an answer first
20expert · hard
An engineer has made several changes to a blueprint, including adding a new leaf switch and modifying a property set. The engineer wants to revert the property set change but keep the leaf switch. What is the best way to do this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-481

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-481” is a trademark of its owner, used for identification only.