Question 340
During an operational security assessment at a public-sector technology agency, the team documents this issue: A query change raises database connection usage but the performance pipeline ignores saturation. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Run representative load tests before production and enforce agreed latency, throughput and error-rate thresholds in the release process. The action targets the recorded failure (A query change raises database connection usage but the performance pipeline ignores saturation), and is intended to reduce the corresponding risk: Low-volume green tests conceal saturation, tail latency and capacity failures during actual user traffic.
Correct verification. A representative peak workload crosses the agreed threshold and the release gate prevents promotion with measured evidence. The measurement or controlled test provides evidence for the issue (A query change raises database connection usage but the performance pipeline ignores saturation) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Require verified vulnerability, license and change-approval conditions before promotion rather than accepting a successful artifact build alone. The paired controls concern load and performance quality thresholds, not that measure.
A deliberately failing unit test stops the build stage and is visible in the published test report. It is not the complementary risk control for load and performance quality thresholds.
Add integration tests against representative isolated service dependencies before release promotion, with predictable data setup and teardown. The two-part load and performance quality thresholds control remains unsatisfied.