Isaca Certification CGEIT Release Date

Thebest strategic responseis todevelop and enforce IT asset life cycle policies in consultation with business units. This approach ensures that legacy systems are managed proactively and collaboratively, balancing risk management, regulatory compliance, and operational needs. Policies should define criteria for decommissioning, archival solutions, and acceptable retention practices.

Firewalls and isolation are tactical mitigations, not strategic solutions. Surcharges may discourage usage but do not resolve governance and retention challenges comprehensively.

A due diligence process is the best way to enable a clear understanding of the vendor’s capabilities that will be critical to the enterprise’s strategy. A due diligence process is a systematic and comprehensive investigation and evaluation of the vendor’s background, reputation, performance, quality, reliability, security, compliance, and suitability for the enterprise’s needs and expectations. A due diligence process can help the enterprise:

Verify the vendor’s claims and credentials, and validate the vendor’s references and testimonials

Assess the vendor’s financial stability, legal status, and ethical standards

Identify the vendor’s strengths, weaknesses, opportunities, and threats

Compare the vendor’s offerings, capabilities, and prices with other vendors and market benchmarks

Determine the risks and benefits of engaging with the vendor, and the mitigation and contingency plans

Negotiate the terms and conditions of the contract, service level agreement (SLA), and key performance indicators (KPIs)

When enterprise strategy changes, themost important action for the CIO is to review the portfolio of current and planned IT projectsto ensure alignment with the new strategic direction. This ensures that resources are being allocated to initiatives that support updated goals and that outdated or misaligned projects are reevaluated.

Performance plans and historical budgets offer context butdo not directly enable strategic realignment.

The most important thing for a data steward to verify when a system’s data is edited by an automated tool to fix an incident is that the change maintains consistency among databases and has no other impacts. Data consistency is a dimension of data quality that describes the data’s uniformity as it moves across applications and networks and when it comes from multiple sources1. Data is considered consistent if two or more values in different locations are identical and do not conflict1. Data consistency is related to data integrity and data currency1. To ensure data consistency, some steps include data governance, automated data integration, and regular data audits and quality control checks1. If the automated tool changes the data in one database, but not in others, it can create inconsistencies and errors that affect the reliability and usability of the data. Similarly, if the automated tool changes the data in a way that affects other processes or systems that depend on the data, it can cause disruptions and failures that impact the business operations and performance. Therefore, the data steward should verify that the change is consistent and has no other impacts before approving it.

The other options are not as important as verifying the data consistency and impact of the change. Requesting and approving the change by the business department and the data owner is a good practice, but not a verification step. Documenting the change in preparation for future audits is a necessary step, but not a verification step. Addressing the permanent solution for the incident by problem management is a relevant step, but not a verification step. References := What is Data Quality - Definition, Dimensions … - Simplilearn