Question 730
At Whitepine Rail Logistics, while reviewing least-privilege accounts, the data center fabric team observes: A newly racked SR Linux switch boots but does not begin its automated first-time configuration. What observation should be required before this case is closed?
Explanation
Correct Answer
At Whitepine Rail Logistics, while reviewing least-privilege accounts, for Whitepine Rail Logistics, accept the repair only after this observation: The device retrieves the intended bootstrap data and begins the documented autoboot sequence. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Whitepine Rail Logistics, while reviewing least-privilege accounts, this option proposes: The account performs the approved task while unrelated privileged actions remain blocked. The option describes a different failure mode: A user assigned to the correct team still cannot perform an approved CLI task. It would address The effective SR Linux role lacks the required supported authorization for that operation, but here the case reports A newly racked SR Linux switch boots but does not begin its automated first-time configuration. The current required evidence is: The device retrieves the intended bootstrap data and begins the documented autoboot sequence.
At Whitepine Rail Logistics, while reviewing least-privilege accounts, this option proposes: A verified gNMI TLS session connects to the intended device while wrong identities fail. This is a valid category of fabric maintenance for another scenario (An automation client rejects gNMI connections despite IP reachability), not the targeted action for Whitepine Rail Logistics. The distinction is the actual cause: The zero-touch provisioning conditions or discovery information are missing.
At Whitepine Rail Logistics, while reviewing least-privilege accounts, this option proposes: A scoped API write succeeds while an unrelated protected edit remains denied. Although related to Users, APIs, TLS and zero-touch provisioning, the proposed change fits another mechanism: The authenticated identity has no sufficient role permission for the attempted configuration path. The evidence in the current case requires a different result: The device retrieves the intended bootstrap data and begins the documented autoboot sequence.