Question 750
At Cedarview Health Systems, while testing a ZTP bootstrap path, the data center fabric team observes: A ZTP process fails halfway through and a device is marked successfully provisioned. Which evidence directly validates the intended repair?
Explanation
Correct Answer
At Cedarview Health Systems, while testing a ZTP bootstrap path, this result is the relevant closure evidence: The switch reports the required interfaces, configuration and management reachability after provisioning. It checks the effect of: Investigate the failed ZTP phase and rerun the supported recovery or bootstrap workflow. The underlying issue was: Provisioning completion is inferred from network boot rather than verified configuration and management state.
Incorrect Answers
At Cedarview Health Systems, while testing a ZTP bootstrap path, this option proposes: Both API methods establish verified sessions after rotation without insecure fallback. This is a valid category of fabric maintenance for another scenario (A management certificate rotation breaks both gNMI and JSON-RPC consumers), not the targeted action for Cedarview Health Systems. The distinction is the actual cause: Provisioning completion is inferred from network boot rather than verified configuration and management state.
At Cedarview Health Systems, while testing a ZTP bootstrap path, this option proposes: The account performs the approved task while unrelated privileged actions remain blocked. Although related to Users, APIs, TLS and zero-touch provisioning, the proposed change fits another mechanism: The effective SR Linux role lacks the required supported authorization for that operation. The evidence in the current case requires a different result: The switch reports the required interfaces, configuration and management reachability after provisioning.
At Cedarview Health Systems, while testing a ZTP bootstrap path, this option proposes: The account retains monitoring access but cannot perform a configuration write. Using that approach would investigate A support account retains elevated configuration privileges after a maintenance window instead. No evidence for that separate failure is supplied here; the reported case is consistent with: Provisioning completion is inferred from network boot rather than verified configuration and management state.