Free Practice Questions for Exin CITM Exam

SMART(Specific, Measurable, Achievable, Relevant, Time-bound) is a goal-setting framework commonly associated withManagement 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.

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.

In corporate hiring protocols,additional screeningtypically refers to background checks beyond basic qualifications, such as verifying a candidate’scriminal record. This is critical for IT roles, where employees may have access to sensitive systems and data, ensuring trustworthiness and compliance with security policies.

Salary demands (A) are negotiated during the hiring process, not screened. Number of years of experience (B) and educational level (D) are verified through resumes and standard checks, not typically classified as “additional screening,” which focuses on security-related checks like criminal records.

The correct sequence for arisk assessment, as perISO 31000andISO/IEC 27001, is:Establish context — identify — analyse — evaluate — treatment(C).

Establish context:Define the scope, objectives, and criteria for the risk assessment (e.g., organizational goals, assets, and risk appetite).

Identify:Identify potential risks (e.g., threats and vulnerabilities) that could impact objectives.

Analyse:Assess the likelihood and impact of identified risks to determine their severity.

Evaluate:Compare risks against risk criteria to prioritize them for treatment.

Treatment:Implement controls or strategies to mitigate, avoid, transfer, or accept risks.

Option A:Incorrect, as “monitor and review” is a post-treatment step, not the starting point.

Option B:Incorrect, as “communication” is not a distinct step in risk assessment; it’s embedded throughout.

Option D:Incorrect, as it skips “establish context,” which is essential for defining the assessment’s scope.

This sequence ensures a structured, systematic approach to risk assessment, aligning with organizational objectives.

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.