Question 270
At fictional Crestview Technology, the network architecture group is preparing a proposal for enterprise technology office during the technical design gate (case HPE7A11-4.2-222). The review identified this issue: a stakeholder claims that an accepted paper topology proves outage targets without deployment testing. Which recurring control most directly reduces the likelihood of this design problem returning?
Explanation
Correct Answer
This recurring control is targeted to the risk that A stakeholder claims that an accepted paper topology proves outage targets without deployment testing. The preventative action is to keep fault-injection outcomes available for technical defense. The underlying design correction remains to demonstrate a traceable failure test plan and bounded acceptance metrics.
Incorrect Answers
The offered evidence “Validate representative client onboarding and roaming after feature changes” relates to defend the solution. The actual question describes this issue: a stakeholder claims that an accepted paper topology proves outage targets without deployment testing. The corresponding response is “Keep fault-injection outcomes available for technical defense.”.
This option — “Require carrier pathway confirmation for the final defense” — checks defend the solution, not whether the design resolves the stated fault: a stakeholder claims that an accepted paper topology proves outage targets without deployment testing. The selected direct criterion is “Keep fault-injection outcomes available for technical defense.”.
“Recalculate lifecycle value if contract scope changes” is a test of defend the solution. That does not establish “Keep fault-injection outcomes available for technical defense.” for the reported issue (a stakeholder claims that an accepted paper topology proves outage targets without deployment testing).