Pass the Exin EPI IT Management CITM Questions and answers with ValidTests

TheRecovery Point Objective (RPO)(D) inbusiness continuity planningdefines the maximum age of data (i.e., the amount of data loss acceptable) that can be tolerated in a disaster before recovery. It represents the time between the last backup and the point of failure, indicating potential data loss. For example, an RPO of 4 hours means up to 4 hours of data could be lost. According toISO 22301, RPO is critical for determining backup and replication strategies.

Maximum Time Allowed (MTA) (A):Not a standard term in business continuity.

Recovery Time Objective (RTO) (B):Defines the maximum downtime before recovery, not data loss.

Maximum Allowable Outage (MAO) (C):Refers to the maximum time a system can be unavailable, similar to RTO, not data loss.

InITIL(Information Technology Infrastructure Library), anemergency changeis implemented to address urgent issues that significantly impact business operations, such as a processing error during financial year closing. Emergency changes are fast-tracked to restore service or prevent further disruption, bypassing some standard change management processes while still requiring approval.

Normal changes (A) follow the full change management process, standard changes (B) are pre-approved and routine, and exceptional (C) is not a standard ITIL term. Emergency change (D) fits the scenario of urgent action to avoid business delays.

The customer’s focus on incorporatingfuture functional requirementsindicates a need forperfective maintenance(B). Inapplication management, perfective maintenance involves enhancing software to add new features or improve functionality to meet evolving business needs, such as adding new modules or capabilities.

Preventive maintenance (A):Focuses on preventing issues by optimizing performance or addressing potential problems, not adding new features.

Corrective maintenance (C):Involves fixing bugs or errors, not incorporating new functionality.

Adaptive maintenance (D):Adapts software to environmental changes (e.g., new operating systems), not specifically for new functional requirements.

Perfective maintenance aligns with theSDLC’s maintenance phase, ensuring the software evolves to support future business requirements.

The main objective ofvendor management meetingsis toverify if the vendor continues to meet the requirements of the contract, supporting the business processes(C). These meetings, as part ofvendor management frameworks, ensure that the vendor’s performance aligns with contractual obligations, service level agreements (SLAs), and business needs. They involve reviewing service delivery, compliance, and any issues affecting business processes.

Explore improvement programs (A):A secondary goal, as improvements may arise from performance reviews.

Identify possible price increases (B):Price discussions may occur, but they are not the primary focus.

Discuss improvement programs (D):Similar to A, this is a potential outcome but not the main objective.

Given the constraints oflittle to no budgetandlimited time,internet job boardsare the ideal sourcing method. They are cost-effective (often free or low-cost), allow quick posting of job openings, and reach a wide pool of candidates, enabling rapid hiring.

Word of mouth (A) is informal and may not yield qualified candidates quickly. Internal IT staff based on SWOT analysis (B) is not a standard recruitment method and takes time to analyze. Recruitment agencies (D) are expensive and slower due to their processes, making them unsuitable for low-budget, urgent hiring.