Question 690
At fictional Longbridge Insurance, during an architecture phase review, stakeholders identify: A regional utility does not monitor emerging technology and business changes once the implementation finishes. What preventive practice would best preserve the corrected outcome?
Explanation
Correct Answer
Monitor business and technology triggers and classify architecture change requests. This safeguard addresses the recurring risk because architecture change management keeps architecture relevant as the enterprise context evolves. Immediate remediation would be: Use Phase H to manage architecture changes and decide whether further architecture work is needed. Applied here, the relevant facts are: A regional utility does not monitor emerging technology and business changes once the implementation finishes.
Incorrect Answers
“Use decision and requirement links across phase deliverables and revisit broken traces” can be suitable where the ADM relies on iterative information exchange across phases rather than independent linear work packets. It does not resolve this question’s narrower failure, which follows: Architecture change management keeps architecture relevant as the enterprise context evolves. The relevant action is “Monitor business and technology triggers and classify architecture change requests”.
The offered action, “Conduct formal architecture-capability setup reviews before approving the first engagement”, addresses a different dependency: Preliminary phase objectives concern readiness and architecture capability, not detailed target applications. The failure reported here instead follows: Architecture change management keeps architecture relevant as the enterprise context evolves. The targeted response is “Monitor business and technology triggers and classify architecture change requests”.
The alternative focuses on the technical control described by: Phase G focuses on governing implementation against agreed architectural definitions. The present requirement is governed by: Architecture change management keeps architecture relevant as the enterprise context evolves. Apply “Monitor business and technology triggers and classify architecture change requests” to address that particular cause.