Question 450
At Juniper Media, the cloud operations team maintains publishing pipelines and Linux build runners under requirements for fast delivery and correct access permissions. The acceptance reviewer must validate: A CI deployment pipeline promotes unreviewed configuration changes directly to production without verifying infrastructure drift or tests. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
A deliberately invalid configuration stops in CI and an approved change has a traceable reviewed deployment record. This measurable outcome verifies correction of: A CI deployment pipeline promotes unreviewed configuration changes directly to production without verifying infrastructure drift or tests. The associated technical action is: Add version-control review, automated lint or validation and an explicit release approval gate before production execution. The Juniper Media review checks actual behavior rather than an untested change claim.
Incorrect Answers
Only explicitly matching test account names are selected and a confusing partial-match account is excluded. This evidence pertains to an unrelated remediation: Anchor the intended regex and validate the full account identifier before applying any change, using a dry-run preview. The alternative issue is: A Bash automation uses a broad regular expression that matches unintended account names and acts on production users outside its allowlist. The current Juniper Media problem is: A CI deployment pipeline promotes unreviewed configuration changes directly to production without verifying infrastructure drift or tests. The decisive expected evidence is instead: A deliberately invalid configuration stops in CI and an approved change has a traceable reviewed deployment record.
A simulated failed copy returns a nonzero result and leaves every previous recovery snapshot intact. This evidence pertains to an unrelated remediation: Check the copy operation's exit status and stop destructive follow-up steps unless the backup completes successfully. The alternative issue is: A Bash backup script continues to delete old snapshots even when the preceding copy command failed and no error handling checks its exit status. The current Juniper Media problem is: A CI deployment pipeline promotes unreviewed configuration changes directly to production without verifying infrastructure drift or tests. The decisive expected evidence is instead: A deliberately invalid configuration stops in CI and an approved change has a traceable reviewed deployment record.
Two independent test calls produce isolated results and modifications to one result do not change the other. This evidence pertains to an unrelated remediation: Use a None default and allocate the mutable dictionary inside each function invocation when independent state is required. The alternative issue is: A Python automation stores a mutable dictionary as a shared default argument and unexpectedly carries state between separate invocations. The current Juniper Media problem is: A CI deployment pipeline promotes unreviewed configuration changes directly to production without verifying infrastructure drift or tests. The decisive expected evidence is instead: A deliberately invalid configuration stops in CI and an approved change has a traceable reviewed deployment record.