CITM Exam Preparation Material | EXIN EPI Certified Information Technology Manager

Explanation:
For a mission-critical application in a financial institution requiring data to be instantly available at two locations, synchronous replication (B) is recommended. Synchronous replication ensures that data is written to both the primary and secondary locations simultaneously, guaranteeing no data loss and immediate availability at both sites. This is critical for financial applications where data integrity and zero recovery point objective (RPO) are essential, as per business continuity and disaster recovery frameworks like ISO 22301.
Instant replication (A): Not a standard term in replication strategies; likely a distractor. Asynchronous replication (C): Data is replicated with a delay, risking data loss in case of failure, unsuitable for instant availability.
Semi-synchronous replication (D): A compromise where the primary site continues after the secondary acknowledges receipt, but it may not guarantee instant availability. Synchronous replication ensures real-time data consistency, critical for financial systems.
Reference: EPI CITM study guide, under Business Continuity Management, likely discusses data replication strategies for disaster recovery. Check sections on disaster recovery planning or data availability.

Explanation:
To predict future customer purchases, the marketing department requires advanced analytics (B), which involves sophisticated data analysis techniques, such as predictive modeling, machine learning, and data mining. These technologies enable the department to analyze customer behavior, identify patterns, and forecast purchasing trends, supporting targeted advertising campaigns. Records Management System (RMS) (A): Focuses on managing and storing records, not predictive analysis.
Ad hoc analysis (C): Allows for on-demand, one-off queries but lacks the predictive capabilities of advanced analytics.
Business Intelligence (BI) (D): Provides reporting and historical data analysis but is less focused on predictive modeling compared to advanced analytics.
Advanced analytics aligns with IT strategy goals of leveraging data for competitive advantage, as it supports predictive insights critical for marketing decisions.
Reference: EPI CITM study guide, under IT Strategy, likely discusses data-driven technologies like advanced analytics for business decision-making. Refer to sections on emerging technologies or data analytics.

Explanation:
When implementing a new system, the customer’s concern about a large impact on the user base suggests the need for a low-risk, controlled adoption strategy. In application management, the parallel adoption approach (B) involves running both the old and new systems simultaneously for a period, allowing users to transition gradually while ensuring the new system functions correctly. This minimizes disruption, as the old system remains operational as a fallback if issues arise with the new system.
Big bang (A): This approach involves switching entirely to the new system at once, which is high-risk and likely to cause significant disruption, especially for a concerned user base. It’s unsuitable here due to the potential for widespread impact.
Coordinated (C): This is not a standard term in application deployment strategies. It may imply a managed transition but lacks the specificity of parallel or phased approaches.
Phased (D): This involves rolling out the new system incrementally (e.g., by department or module), which reduces risk but doesn’t provide the same level of safety as parallel, where both systems run concurrently to ensure continuity.
The parallel approach is ideal for mitigating risks during a critical system transition, as it allows validation of the new system’s performance while maintaining business continuity. According to ITIL or SDLC frameworks, parallel adoption is often recommended for mission-critical systems to ensure stability and user acceptance.
Reference: EPI CITM study guide, under Application Management, likely discusses system implementation strategies within the Software Development Life Cycle (SDLC) or ITIL’s service asset and configuration management. Refer to sections on application deployment, transition planning, or change management for details on parallel adoption.

Explanation:
A high-level assessment to list risks in order of priority for treatment is best conducted using qualitative analysis (D). According to ISO 31000, qualitative risk analysis assesses risks based on their likelihood and impact using non-numerical methods (e.g., risk matrices, high/medium/low ratings). This approach is suitable for high-level assessments, as it quickly prioritizes risks without requiring detailed quantitative data, aligning with senior management’s needs for a prioritized risk list. Quantitative analysis (A): Uses numerical data (e.g., cost estimates, probabilities) for detailed analysis, not ideal for high-level overviews.
Semi-quantitative analysis (B): Combines qualitative and quantitative methods, but is more detailed than needed for a high-level assessment.
Ad hoc analysis (C): Not a standard risk analysis method; implies informal analysis, unsuitable for structured prioritization.
Reference: EPI CITM study guide, under Risk Management, likely references ISO 31000’s qualitative risk analysis for high-level assessments. Check sections on risk assessment or prioritization.

Explanation:
A white box test involves testing the internal structure and code of an application, requiring access to its source code. The stakeholders’ demand for an independent white box test indicates their primary concern is the quality of the source code (C). This type of testing, conducted by an independent party, ensures the code is well-structured, secure, and free of defects that could lead to vulnerabilities or inefficiencies.
Capacity (A): Refers to the system’s ability to handle load, typically tested via performance or stress testing, not white box testing.
Performance (B): Focuses on speed and responsiveness, evaluated through performance testing, not white box testing.
Functionality (D): Is tested via black box testing, which focuses on inputs and outputs without examining the code.
White box testing is a technical process often aligned with SDLC quality assurance practices, ensuring code reliability and maintainability, which is critical for stakeholders concerned about long-term system integrity.
Reference: EPI CITM study guide, under Application Management, likely covers testing methodologies in the SDLC, emphasizing white box testing for code quality. Check sections on application testing or quality assurance.