Exin EPI Certified Information Technology Manager CITM Exam Questions

Answer : C

In risk management, the Annual Loss Expectancy (ALE) is calculated as:

ALE = Single Loss Expectancy (SLE) Annualized Rate of Occurrence (ARO), where SLE = Asset Value Exposure Factor (EF).

Given:

Asset Value = $200,000

Exposure Factor (EF) = 25% = 0.25

ALE = $100,000

Calculate SLE:

SLE = Asset Value EF = $200,000 0.25 = $50,000

Calculate ARO:

ALE = SLE ARO

$100,000 = $50,000 ARO

ARO = $100,000 $50,000 = 2

Thus, the Annualized Rate of Occurrence (ARO) is 2 (C), meaning the incident is expected to occur twice per year.

0.4 (A): Incorrect; implies a lower frequency (0.4 times per year).

1 (B): Incorrect; would yield an ALE of $50,000, not $100,000.

Answer : A

In ITIL's service catalog management, data points required for IT services are used to measure the performance of IT services delivered (A). These data points (e.g., uptime, response times, incident resolution rates) enable the IT provider to monitor and report on service quality, ensuring alignment with service level agreements (SLAs) and customer expectations. A needs analysis identifies key performance indicators (KPIs) to track service effectiveness.

Identify data used by the customer (B): Focuses on customer data usage, not service performance.

Determine life expectancy (C): Relates to service lifecycle planning, not data points.

Establish operating hours (D): Operating hours are a service attribute, not the primary purpose of data points.

Answer : A

A use case or user story describes interactions between a user (role) and the system to achieve a specific goal, defining what the system must do. This corresponds to a functional requirement (A), which specifies the system's features or capabilities (e.g., ''the system shall allow users to submit a return request''). According to SDLC and requirements engineering, functional requirements focus on specific functionalities, as captured in use cases.

Behavioral requirement (B): Not a standard term; it may refer to system behavior but is less specific than functional requirements.

Non-functional requirement (C): Covers performance, scalability, or usability (e.g., response time), not specific user interactions.

Security requirement (D): A subset of non-functional requirements focused on security, not general use case interactions.

Answer : A

SMART (Specific, Measurable, Achievable, Relevant, Time-bound) is a goal-setting framework commonly associated with Management By Objectives (MBO). MBO involves setting clear, measurable objectives for employees, aligning individual performance with organizational goals. In appraisal meetings, using SMART conditions ensures that performance goals are clearly defined and trackable, which is a hallmark of MBO.

Graphic rating scales (B) involve rating employees on a scale for various traits, not necessarily tied to SMART goals. Ranking (C) and Performance ranking method (D) focus on comparing employees, which doesn't align with SMART's emphasis on individual, objective-based performance evaluation.

Answer : A

In ITIL's problem management process, poor registration of problems (A) is the most likely cause of low-quality problem resolution. Effective problem management requires accurate logging of incidents and problems, including detailed descriptions, to enable proper root cause analysis and resolution. If problems are poorly registered (e.g., incomplete or inaccurate data), it hinders diagnosis and resolution, leading to customer dissatisfaction.

Wrong allocation of problems (B): Incorrect assignment to teams can delay resolution but is less fundamental than poor registration, which affects the entire process.

Errors in priority (C): Incorrect prioritization may delay urgent issues, but poor registration impacts resolution quality more directly.

Lack of budget (D): May limit resources, but the scenario points to process quality, not resource constraints.

Answer : C

To deliver knowledge supporting cross-functional business units, both information management (A) and data management (B) are required (C). Data management ensures raw data is collected, stored, and organized (e.g., databases, data quality), while information management transforms data into meaningful knowledge (e.g., through analytics, reporting, or knowledge bases) accessible to business units. According to COBIT or IT strategy frameworks, integrating data and information management enables cross-functional collaboration by providing actionable insights and knowledge sharing.

Information management alone (A): Focuses on knowledge delivery but relies on well-managed data.

Data management alone (B): Provides raw data but lacks the processes to turn it into usable knowledge.

Answer : C

The main objective of vendor management meetings is to verify if the vendor continues to meet the requirements of the contract, supporting the business processes (C). These meetings, as part of vendor 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.