Exin EPI Certified Information Technology Manager CITM Exam Questions

Answer : C

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.

Answer : A

The main objective of a job rotation program in an IT organization is to support the long-term continuity of the organization (A). Job rotation ensures that multiple staff members are trained across various roles and tasks, reducing dependency on specific individuals and mitigating risks associated with staff turnover or absences. This approach enhances organizational resilience by creating a flexible, cross-trained workforce capable of maintaining operations, aligning with IT organization principles for workforce planning and business continuity.

Train staff on a range of activities (B): While training is a benefit, it is a means to achieve continuity, not the primary objective.

Increase staff job satisfaction (C): Job satisfaction may be a secondary benefit, but it's not the main goal in an IT context.

Allow staff a diversity in responsibilities (D): Diversity in tasks is a byproduct, not the primary focus, which is organizational continuity.

According to human resource management frameworks, job rotation is a strategic tool for ensuring operational stability, particularly in IT environments where specialized skills are critical.

Answer : D

The Recovery Point Objective (RPO) (D) in business continuity planning defines 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 to ISO 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.

Answer : B

The primary reason for including anonymous feedback in feedback collection is to promote honest feedback while avoiding fear for backfiring on the participant (B). Anonymity encourages participants to provide candid, truthful responses without worrying about repercussions, such as criticism or retaliation, which is critical in service management for gathering accurate insights into service quality or issues. According to ITIL's continual service improvement (CSI), honest feedback is essential for identifying areas for improvement.

Avoidance of non-compliance (A): Anonymity is unrelated to regulatory compliance in this context.

Easier processing of data (C): Anonymity may complicate data processing by removing identifiers, not simplifying it.

Reduced time (D): Anonymity doesn't inherently reduce the time required for feedback.

Answer : D

A lessons learned report in project management is designed to document both positive and negative experiences from a project to improve future projects. According to the Project Management Institute (PMI) and frameworks like PMBOK, the purpose is to capture insights, successes, challenges, and recommendations to enhance processes, avoid repeating mistakes, and replicate successes in future initiatives.

Option A focuses only on reporting achievements, which is too narrow. Option B emphasizes accountability for mistakes, which is not the primary goal, as the report aims to improve rather than blame. Option C is incorrect because identifying risks is part of risk management, not the primary focus of lessons learned. Option D correctly captures the intent to benefit future projects by analyzing both positive and negative aspects.

Answer : A

The project charter (or project brief) is a high-level document created during the initiation phase of a project, as defined by PMBOK (Project Management Body of Knowledge). It outlines the project's purpose, objectives, scope, and key elements but does not include detailed planning (A), which occurs during the planning phase after the charter is approved. The charter typically includes:

High-level risks (B): Identifies major risks to provide early awareness.

Summary budget (C): Provides an initial cost estimate for approval.

Quality expectations (D): Defines high-level quality requirements or standards.

Detailed planning, such as creating a detailed Work Breakdown Structure (WBS) or schedule, is part of the project management plan developed later, not the charter.

Answer : A

For a budget proposal that must be as accurate as possible and supported by a Work Breakdown Structure (WBS) or Product Breakdown Structure (PBS), the bottom-up estimate (A) is preferred. This method involves estimating costs for each task or deliverable in the WBS/PBS, then aggregating them to calculate the total budget. According to PMBOK, bottom-up estimation leverages detailed data, ensuring high accuracy, especially when a WBS is available.

Rough Order of Magnitude (ROM) (B): A high-level estimate with low accuracy (50%), used early in projects, not suitable for detailed budgeting.

Analogous estimate (C): Relies on historical data from similar projects, less accurate than bottom-up when detailed WBS data exists.

Budget estimate (D): A general term, not a specific technique, and less precise than bottom-up.