mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-481

Exam Name: Data Center, Specialist (JNCIS-DC)

Certification Provider: Juniper

Juniper JN0-481 Questions & Answers

Reliable & Actual Study Materials for JN0-481 Exam Success

65 Questions & Answers with Testing Engine

"JN0-481: Data Center, Specialist (JNCIS-DC)" Testing Engine covers all the knowledge points of the real Juniper JN0-481 exam.

The latest actual JN0-481 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-481 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-481 Practice Test 5

Question 40

A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Which design or operational principle best explains this behavior?

  1. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles.
  2. Total spine capacity includes available physical ports and supported link-speed and topology constraints.
  3. Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint.
  4. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required.

Explanation

Correct Answer

D:

physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. Here, a data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. A useful discriminating check is to inspect the rack type's expected spine attachment graph and actual cable endpoints.

Incorrect Answers

A:

The option “Rack type and leaf selection must support the intended redundant attachment topology and host interface roles” is useful in a different setting: A rack designer wants a redundant host attachment pattern for critical appliances. The case being tested is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

B:

“Total spine capacity includes available physical ports and supported link-speed and topology constraints” is relevant to a different condition: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. The stated question instead concerns: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

C:

That choice—“Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint”—addresses this other problem: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Here the scenario is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

Question 41

A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Which initial check would most directly distinguish the likely cause?

  1. Inspect the route export/import policy and observed advertised routes for the affected VRF.
  2. Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template.
  3. Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy.
  4. Inspect the proposed external or shared-services routing path, import policy and required security controls.

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy. The underlying concept is that connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. After confirming the finding, a controlled remediation is to create or correct a scoped connectivity template and routing policy for the authorized VRF.

Incorrect Answers

A:

“Inspect the route export/import policy and observed advertised routes for the affected VRF” is associated with a distinct issue: A route export template applied to a border device advertises all tenant prefixes beyond the data center. By contrast, the actual problem is: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. The relevant inspection is: Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy. The most discriminating first check is “Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy”.

B:

The option “Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template” is useful in a different setting: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. The case being tested is: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. The relevant inspection is: Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy. The most discriminating first check is “Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy”.

D:

That choice—“Inspect the proposed external or shared-services routing path, import policy and required security controls”—addresses this other problem: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Here the scenario is: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. The relevant inspection is: Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy. The most discriminating first check is “Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy”.

Question 42

A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. Which design or operational principle best explains this behavior?

  1. Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity.
  2. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity.
  3. Unique accurate managed device identities are required for safe inventory and blueprint allocation.
  4. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.

Explanation

Correct Answer

A:

Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity. Here, a switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. A useful discriminating check is to inspect the device-agent state, management authentication and discovered system ID before allocation.

Incorrect Answers

B:

“Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity” is associated with a distinct issue: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. By contrast, the actual problem is: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity. The controlling principle is “Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity”.

C:

The option “Unique accurate managed device identities are required for safe inventory and blueprint allocation” is useful in a different setting: A deployment team duplicates a device-system ID when registering two new leaf switches. The case being tested is: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity. The controlling principle is “Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity”.

D:

“Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly” is relevant to a different condition: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. The stated question instead concerns: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity. The controlling principle is “Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity”.

Question 43

A team wants to locate every virtual network owned by a particular application during a migration. Which controlled change best addresses the described requirement?

  1. Use a scoped blueprint query or tag selector that follows the approved object relationship.
  2. Apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory.
  3. Update the approved property set and stage dependent configurations through normal blueprint review.
  4. Create or update the authorized generic system and its connectivity template within the staged blueprint.

Explanation

Correct Answer

B:

This action addresses the stated defect: apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory. The underlying constraint is that blueprint object tags and query filters support targeted discovery and operational reporting. Verify rather than assume success: verify the inventory's object IDs, tenant ownership and linked endpoints before making changes.

Incorrect Answers

A:

“Use a scoped blueprint query or tag selector that follows the approved object relationship” is relevant to a different condition: An operator wants to identify managed nodes by rack and role in the blueprint graph. The stated question instead concerns: A team wants to locate every virtual network owned by a particular application during a migration. The governing requirement is to apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory. The most relevant correction is “Apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory”.

C:

“Update the approved property set and stage dependent configurations through normal blueprint review” is associated with a distinct issue: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. By contrast, the actual problem is: A team wants to locate every virtual network owned by a particular application during a migration. The governing requirement is to apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory. The most relevant correction is “Apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory”.

D:

The option “Create or update the authorized generic system and its connectivity template within the staged blueprint” is useful in a different setting: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The case being tested is: A team wants to locate every virtual network owned by a particular application during a migration. The governing requirement is to apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory. The most relevant correction is “Apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory”.

Question 44

A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Which design or operational principle best explains this behavior?

  1. EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path.
  2. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices.
  3. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements.
  4. Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability.

Explanation

Correct Answer

D:

edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability. Here, a leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. A useful discriminating check is to inspect the tenant's SVI, gateway placement, host routes and effective Type 2 or Type 5 EVPN advertisements.

Incorrect Answers

A:

The option “EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path” is useful in a different setting: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. The case being tested is: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability. The controlling principle is “Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability”.

B:

“A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices” is relevant to a different condition: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. The stated question instead concerns: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability. The controlling principle is “Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability”.

C:

That choice—“EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability. The controlling principle is “Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability”.

Question 45

An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Which initial check would most directly distinguish the likely cause?

  1. Inspect and preserve or commit required pending modifications before initiating a revision jump.
  2. Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices.
  3. Inspect historical identifiers, resource assignments, device availability and supported rollback constraints.
  4. Determine whether the unwanted modification exists only in Staged or in the Active revision.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices. The underlying concept is that Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. After confirming the finding, a controlled remediation is to select the approved prior revision, review resulting uncommitted differences and commit the rollback following change control.

Incorrect Answers

A:

“Inspect and preserve or commit required pending modifications before initiating a revision jump” is associated with a distinct issue: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. By contrast, the actual problem is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. The relevant inspection is: Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices. The most discriminating first check is “Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices”.

C:

“Inspect historical identifiers, resource assignments, device availability and supported rollback constraints” is relevant to a different condition: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. The stated question instead concerns: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. The relevant inspection is: Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices. The most discriminating first check is “Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices”.

D:

That choice—“Determine whether the unwanted modification exists only in Staged or in the Active revision”—addresses this other problem: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Here the scenario is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. The relevant inspection is: Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices. The most discriminating first check is “Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices”.

Question 46

A newly staged fabric reports LLDP neighbor mismatches although physical links are up. Which shortcut would be most likely to undermine this objective?

  1. Ignore LLDP mismatches because link LEDs are illuminated.
  2. Mark the whole deployment complete when a single leaf reports success.
  3. Swap arbitrary port assignments in production without reviewing topology role requirements.
  4. Assume an SSH prompt proves the device is fully under Apstra management.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: ignore LLDP mismatches because link LEDs are illuminated. It violates the principle that cabling validation compares observed neighbor links against intended device/interface relationships. An appropriate alternative is to correct physical cabling or update the approved design only after confirming the intended topology.

Incorrect Answers

B:

“Mark the whole deployment complete when a single leaf reports success” is associated with a distinct issue: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. By contrast, the actual problem is: A newly staged fabric reports LLDP neighbor mismatches although physical links are up. Cabling validation compares observed neighbor links against intended device/interface relationships. The directly relevant unsafe shortcut is “Ignore LLDP mismatches because link LEDs are illuminated”.

C:

The option “Swap arbitrary port assignments in production without reviewing topology role requirements” is useful in a different setting: An Apstra blueprint expects a set of spine interfaces but physical inventory maps uplinks to different ports. The case being tested is: A newly staged fabric reports LLDP neighbor mismatches although physical links are up. Cabling validation compares observed neighbor links against intended device/interface relationships. The directly relevant unsafe shortcut is “Ignore LLDP mismatches because link LEDs are illuminated”.

D:

“Assume an SSH prompt proves the device is fully under Apstra management” is relevant to a different condition: A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. The stated question instead concerns: A newly staged fabric reports LLDP neighbor mismatches although physical links are up. Cabling validation compares observed neighbor links against intended device/interface relationships. The directly relevant unsafe shortcut is “Ignore LLDP mismatches because link LEDs are illuminated”.

Question 47

A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Which evidence most directly verifies the intended network outcome?

  1. Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network.
  2. Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested.
  3. Observe each VRF learns only the intended tenant routes despite overlapping address space.
  4. Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested. The decisive investigation is to inspect Ethernet segment identifiers, multihoming state and designated-forwarder election on the relevant leafs. The governing principle is that EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability.

Incorrect Answers

A:

“Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network” is relevant to a different condition: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. The stated question instead concerns: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

C:

“Observe each VRF learns only the intended tenant routes despite overlapping address space” is associated with a distinct issue: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. By contrast, the actual problem is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

D:

The option “Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF” is useful in a different setting: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. The case being tested is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

Question 48

A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Which evidence most directly verifies the intended network outcome?

  1. Confirm the modeled external links and routing connectivity satisfy the acceptance topology.
  2. Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy.
  3. Confirm the blueprint build validation clears and expected rendered configurations are available for review.
  4. Verify syntax validation and successful controlled deployment to representative supported devices.

Explanation

Correct Answer

A:

This directly tests the desired result: confirm the modeled external links and routing connectivity satisfy the acceptance topology. The decisive investigation is to compare required external routing connections with the template topology and leaf roles. The governing principle is that blueprint design intent must model necessary fabric roles and external connectivity before deployment.

Incorrect Answers

B:

“Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy” is relevant to a different condition: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. The stated question instead concerns: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Blueprint design intent must model necessary fabric roles and external connectivity before deployment. The direct acceptance evidence is “Confirm the modeled external links and routing connectivity satisfy the acceptance topology”.

C:

That choice—“Confirm the blueprint build validation clears and expected rendered configurations are available for review”—addresses this other problem: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Here the scenario is: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Blueprint design intent must model necessary fabric roles and external connectivity before deployment. The direct acceptance evidence is “Confirm the modeled external links and routing connectivity satisfy the acceptance topology”.

D:

“Verify syntax validation and successful controlled deployment to representative supported devices” is associated with a distinct issue: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. By contrast, the actual problem is: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Blueprint design intent must model necessary fabric roles and external connectivity before deployment. The direct acceptance evidence is “Confirm the modeled external links and routing connectivity satisfy the acceptance topology”.

Question 49

A design is staged and rendered correctly, but a production switch still uses the previous running configuration. Which controlled change best addresses the described requirement?

  1. Select the approved deployment or diagnostic view before reviewing and applying configuration diffs.
  2. Review the changes, commit the authorized revision and monitor the resulting device deployments.
  3. Review and commit the approved staged change using the documented deployment process.
  4. Assign the replacement supported system to the correct logical role using the documented controlled process.

Explanation

Correct Answer

C:

This action addresses the stated defect: review and commit the approved staged change using the documented deployment process. The underlying constraint is that staging and rendering intended configuration are distinct from committing and deploying the active blueprint. Verify rather than assume success: confirm the active revision and target device running configuration reflect the approved change.

Incorrect Answers

A:

“Select the approved deployment or diagnostic view before reviewing and applying configuration diffs” is associated with a distinct issue: An operations team must compare pristine, incremental and rendered configuration views before a planned device update. By contrast, the actual problem is: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The relevant inspection is: Review and commit the approved staged change using the documented deployment process. The most relevant correction is “Review and commit the approved staged change using the documented deployment process”.

B:

The option “Review the changes, commit the authorized revision and monitor the resulting device deployments” is useful in a different setting: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. The case being tested is: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The relevant inspection is: Review and commit the approved staged change using the documented deployment process. The most relevant correction is “Review and commit the approved staged change using the documented deployment process”.

D:

That choice—“Assign the replacement supported system to the correct logical role using the documented controlled process”—addresses this other problem: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Here the scenario is: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The relevant inspection is: Review and commit the approved staged change using the documented deployment process. The most relevant correction is “Review and commit the approved staged change using the documented deployment process”.

Question 50

A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Which design or operational principle best explains this behavior?

  1. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model.
  2. Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation.
  3. Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership.
  4. Apstra role-based access control separates read visibility from permissions to change managed fabric objects.

Explanation

Correct Answer

D:

Apstra role-based access control separates read visibility from permissions to change managed fabric objects. Here, a fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. A useful discriminating check is to inspect the user's role assignments and denied operation in the Apstra access and audit records.

Incorrect Answers

A:

That choice—“The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model”—addresses this other problem: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. Here the scenario is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

B:

“Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation” is associated with a distinct issue: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. By contrast, the actual problem is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

C:

The option “Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership” is useful in a different setting: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. The case being tested is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

Data Center, Specialist (JNCIS-DC) (JN0-481) Practice Tests