Question 10
At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A CI pipeline logs static device admin passwords from environment variables at every run and never rotates them. Which targeted correction best addresses the network automation failure?
Explanation
Correct Answer
Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. This addresses the problem because hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Confirm success using: A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.
Incorrect Answers
The proposed action belongs to the mechanism: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. Here the stated fault follows a different mechanism: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The corrective choice is “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts”.
The offered action targets: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The case facts point instead to: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Implement “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts” to address that specific condition.
This alternative is a response to another technical cause: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The reported case instead depends on: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The action that directly addresses it is “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts”.