Question 510
Developers inject plaintext database passwords into pipeline YAML variables for convenience. Which result would demonstrate that the intended security outcome was achieved?
Explanation
Correct Answer
A correct test must show that a pipeline executes without printing or committing database credentials. The underlying reason is DevSecOps requires secret isolation from editable source and logs.
Incorrect Answers
The proposed evidence relates to another situation: A new API is tested for functionality but not for authorization bypass before production release. Application security validation must cover malicious interactions as well as feature tests. The architect needs verification that a pipeline executes without printing or committing database credentials.
That test would support a different case: A container deployment starts despite a known critical image finding from its registry scan. Risk-based deployment policies prevent bypassing significant image weaknesses. The present control must instead show that a pipeline executes without printing or committing database credentials.
This observation evaluates A microservice repository changes dependencies but security finds no audit trail of deployed versions. Build provenance supports rapid supply-chain investigation and rollback. It does not establish the required result: a pipeline executes without printing or committing database credentials.