Question 290An organization retains three incompatible customer identifiers because each business unit procured its own CRM. Which causal interpretation is the most defensible? Enterprise architecture balances local component optimization with integrated business capability outcomes. Inconsistent shared data models create integrity and reconciliation risk across systems. Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. ExplanationCorrect Answer B:Inconsistent shared data models create integrity and reconciliation risk across systems. The practical correction is to define authoritative data identity and integration architecture with cross-unit governance. Other Answers A:Enterprise architecture balances local component optimization with integrated business capability outcomes. The risk in this scenario follows a different principle: Inconsistent shared data models create integrity and reconciliation risk across systems. C:Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. The risk in this scenario follows a different principle: Inconsistent shared data models create integrity and reconciliation risk across systems. D:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. The risk in this scenario follows a different principle: Inconsistent shared data models create integrity and reconciliation risk across systems.
Question 291An organization retains three incompatible customer identifiers because each business unit procured its own CRM. Which audit procedure most directly verifies the stated requirement? Test identity reconciliation across representative customer records and downstream feeds. Trace data placement, copies and recovery links against approved enterprise boundaries. Run a representative customer transaction across the mapped systems and identify handoff failures. Reconcile application inventories, authentication flows and planned migration waves. ExplanationCorrect Answer A:Inconsistent shared data models create integrity and reconciliation risk across systems. The selected test checks this actual control outcome rather than merely related configuration. Other Answers B:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. This does not establish the required evidence: Test identity reconciliation across representative customer records and downstream feeds. C:Enterprise architecture balances local component optimization with integrated business capability outcomes. This does not establish the required evidence: Test identity reconciliation across representative customer records and downstream feeds. D:Unknown architectural dependencies create hidden common failure modes during transformation. This does not establish the required evidence: Test identity reconciliation across representative customer records and downstream feeds.
Question 292An organization retains three incompatible customer identifiers because each business unit procured its own CRM. Which lifecycle measure would best maintain the corrected condition? Make dependency mapping a prerequisite to major architecture consolidation. Establish enterprise information standards and controlled integration exceptions. Maintain business capability and integration traceability through release change control. Use an architecture decision record with security and continuity signoff. ExplanationCorrect Answer B:Inconsistent shared data models create integrity and reconciliation risk across systems. The safeguard makes this specific requirement part of ongoing governance rather than a one-time fix. Other Answers A:Unknown architectural dependencies create hidden common failure modes during transformation. For this specific failure, the relevant preventive control is: Establish enterprise information standards and controlled integration exceptions. C:Enterprise architecture balances local component optimization with integrated business capability outcomes. For this specific failure, the relevant preventive control is: Establish enterprise information standards and controlled integration exceptions. D:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. For this specific failure, the relevant preventive control is: Establish enterprise information standards and controlled integration exceptions.
Question 293A business case adds a new public-cloud database but ignores existing contractual residency and recovery boundaries. Which audit conclusion most directly drives a practical correction? Introduce an enterprise architecture data and integration map before approving redundant services. Map the application, identity and network dependencies before migration sequencing. Assess the full value stream and inter-system dependencies in architecture governance. Evaluate proposed architecture against enterprise data-location and resilience constraints. ExplanationCorrect Answer D:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. The confirming audit procedure is: Trace data placement, copies and recovery links against approved enterprise boundaries. Other Answers A:Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. For the stated failure, the appropriate corrective action is: Evaluate proposed architecture against enterprise data-location and resilience constraints. B:Unknown architectural dependencies create hidden common failure modes during transformation. For the stated failure, the appropriate corrective action is: Evaluate proposed architecture against enterprise data-location and resilience constraints. C:Enterprise architecture balances local component optimization with integrated business capability outcomes. For the stated failure, the appropriate corrective action is: Evaluate proposed architecture against enterprise data-location and resilience constraints.
Question 294A business case adds a new public-cloud database but ignores existing contractual residency and recovery boundaries. Why does the described condition create the stated control weakness? Enterprise architecture exposes duplicate capabilities and interdependencies that local project reviews miss. Inconsistent shared data models create integrity and reconciliation risk across systems. Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. Unknown architectural dependencies create hidden common failure modes during transformation. ExplanationCorrect Answer C:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. The practical correction is to evaluate proposed architecture against enterprise data-location and resilience constraints. Other Answers A:Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. The risk in this scenario follows a different principle: Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. B:Inconsistent shared data models create integrity and reconciliation risk across systems. The risk in this scenario follows a different principle: Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. D:Unknown architectural dependencies create hidden common failure modes during transformation. The risk in this scenario follows a different principle: Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs.
Question 295A business case adds a new public-cloud database but ignores existing contractual residency and recovery boundaries. Which evidence should a reviewer seek before accepting remediation? Trace authoritative data flows and ownership through the proposed analytics design. Trace data placement, copies and recovery links against approved enterprise boundaries. Test identity reconciliation across representative customer records and downstream feeds. Reconcile application inventories, authentication flows and planned migration waves. ExplanationCorrect Answer B:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. The selected test checks this actual control outcome rather than merely related configuration. Other Answers A:Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. This does not establish the required evidence: Trace data placement, copies and recovery links against approved enterprise boundaries. C:Inconsistent shared data models create integrity and reconciliation risk across systems. This does not establish the required evidence: Trace data placement, copies and recovery links against approved enterprise boundaries. D:Unknown architectural dependencies create hidden common failure modes during transformation. This does not establish the required evidence: Trace data placement, copies and recovery links against approved enterprise boundaries.
Question 296A business case adds a new public-cloud database but ignores existing contractual residency and recovery boundaries. Which standard practice would most specifically protect the result? Maintain business capability and integration traceability through release change control. Require architecture alignment review during project intake. Establish enterprise information standards and controlled integration exceptions. Use an architecture decision record with security and continuity signoff. ExplanationCorrect Answer D:Architecture choices must satisfy cross-cutting policies beyond a project's direct functional needs. The safeguard makes this specific requirement part of ongoing governance rather than a one-time fix. Other Answers A:Enterprise architecture balances local component optimization with integrated business capability outcomes. For this specific failure, the relevant preventive control is: Use an architecture decision record with security and continuity signoff. B:Architecture exposes duplicate capabilities and interdependencies that local project reviews miss. For this specific failure, the relevant preventive control is: Use an architecture decision record with security and continuity signoff. C:Inconsistent shared data models create integrity and reconciliation risk across systems. For this specific failure, the relevant preventive control is: Use an architecture decision record with security and continuity signoff.
Question 297Management ranks risks by how often alerts are observed but never considers potential financial or safety impact. What should management implement to correct this precise deficiency? Reassess residual risk and obtain authorized risk-owner approval after control implementation. Consolidate material dependency risks under enterprise risk governance with assigned owners. Time-limit acceptance and require periodic evidence-based reapproval. Apply a documented likelihood-and-impact methodology with business owner validation. ExplanationCorrect Answer D:Alert frequency alone does not represent exposure severity or enterprise risk appetite. The confirming audit procedure is: Compare scored risk scenarios against agreed impact scales and response priorities. Other Answers A:Control deployment changes likelihood or impact; it does not automatically eliminate risk. For the stated failure, the appropriate corrective action is: Apply a documented likelihood-and-impact methodology with business owner validation. B:Fragmented registers can conceal correlated exposures and prevent coordinated treatment. For the stated failure, the appropriate corrective action is: Apply a documented likelihood-and-impact methodology with business owner validation. C:Open-ended risk exceptions lose accountability when conditions or safeguards change. For the stated failure, the appropriate corrective action is: Apply a documented likelihood-and-impact methodology with business owner validation.
Question 298Management ranks risks by how often alerts are observed but never considers potential financial or safety impact. What makes this configuration or process unreliable? Control deployment changes likelihood or impact; it does not automatically eliminate risk. Alert frequency alone does not represent exposure severity or enterprise risk appetite. Fragmented registers can conceal correlated exposures and prevent coordinated treatment. Open-ended risk exceptions lose accountability when conditions or safeguards change. ExplanationCorrect Answer B:Alert frequency alone does not represent exposure severity or enterprise risk appetite. The practical correction is to apply a documented likelihood-and-impact methodology with business owner validation. Other Answers A:Control deployment changes likelihood or impact; it does not automatically eliminate risk. The risk in this scenario follows a different principle: Alert frequency alone does not represent exposure severity or enterprise risk appetite. C:Fragmented registers can conceal correlated exposures and prevent coordinated treatment. The risk in this scenario follows a different principle: Alert frequency alone does not represent exposure severity or enterprise risk appetite. D:Open-ended risk exceptions lose accountability when conditions or safeguards change. The risk in this scenario follows a different principle: Alert frequency alone does not represent exposure severity or enterprise risk appetite.
Question 299Management ranks risks by how often alerts are observed but never considers potential financial or safety impact. What evidence is strongest for confirming this control now operates? Trace supplier service risks to enterprise rollups, owners and escalation thresholds. Inspect pre/post control assessments and formal residual acceptance records. Compare scored risk scenarios against agreed impact scales and response priorities. Sample aged exceptions for owners, expiries and independent control-test evidence. ExplanationCorrect Answer C:Alert frequency alone does not represent exposure severity or enterprise risk appetite. The selected test checks this actual control outcome rather than merely related configuration. Other Answers A:Fragmented registers can conceal correlated exposures and prevent coordinated treatment. This does not establish the required evidence: Compare scored risk scenarios against agreed impact scales and response priorities. B:Control deployment changes likelihood or impact; it does not automatically eliminate risk. This does not establish the required evidence: Compare scored risk scenarios against agreed impact scales and response priorities. D:Open-ended risk exceptions lose accountability when conditions or safeguards change. This does not establish the required evidence: Compare scored risk scenarios against agreed impact scales and response priorities.
Question 300Management ranks risks by how often alerts are observed but never considers potential financial or safety impact. Which lasting control most effectively reduces the recurring exposure? Configure automated exception expiration and reassessment alerts. Reconcile departmental registers with enterprise risk reporting. Train risk owners on uniform impact, likelihood and residual-risk scoring. Require reassessment and explicit acceptance before risk-register closure. ExplanationCorrect Answer C:Alert frequency alone does not represent exposure severity or enterprise risk appetite. The safeguard makes this specific requirement part of ongoing governance rather than a one-time fix. Other Answers A:Open-ended risk exceptions lose accountability when conditions or safeguards change. For this specific failure, the relevant preventive control is: Train risk owners on uniform impact, likelihood and residual-risk scoring. B:Fragmented registers can conceal correlated exposures and prevent coordinated treatment. For this specific failure, the relevant preventive control is: Train risk owners on uniform impact, likelihood and residual-risk scoring. D:Control deployment changes likelihood or impact; it does not automatically eliminate risk. For this specific failure, the relevant preventive control is: Train risk owners on uniform impact, likelihood and residual-risk scoring.