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?
Explanation
Correct Answer
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
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”.
“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”.
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”.