CDFOM Exam Dumps - Exin EPI Data Centre Questions and Answers

Under EPI’s safety and statutory requirements, all electrical portable equipment must:

Be routinelytested and tagged

Show proof of the last inspection

Be kept in safe working condition

Be removed from service immediately if found unsafe

Loose electrical cabling and missing testing history indicate unsafe equipment.

Equipment that fails visual inspection or lacks test records must be labeled “out of service” and sent for formal inspection/testing.

WhyCis correct:

It follows the required "testing & tagging" compliance process.

It prevents the use of unsafe equipment.

It aligns with EPI’s requirement to isolate defective equipment until verified safe.

It ensures proper record-keeping and re-certification.

Why the other options are incorrect:

A: Urgency does not override safety regulations.

B: Using duct tape is unsafe and violates electrical safety standards.

D: Disposal is not required unless testing confirms the item is beyond repair.

EPI DCFOM-Aligned Reference Concepts (Paraphrased)

Unsafe or untested electrical equipment must be removed from service.

Testing & tagging is mandatory.

Safety takes precedence over urgency.

AnInformation Security Management System (ISMS)is designed to protect information assets through structured controls, policies, and risk management practices.

EPI aligns with globally accepted security frameworks (e.g., ISO/IEC 27001), where the foundation of an ISMS is theCIA triad:

C — Confidentiality

Ensures information is accessible only to authorized persons.

I — Integrity

Ensures information is accurate, complete, protected from unauthorized modification.

A — Availability

Ensures information and systems are accessible when required.

Implementing an ISMS aims to safeguard these three fundamental information security objectives.

Why the other options are incorrect:

A— This focuses only on records retention, not information security as a whole.

B— Omits integrity and availability, which are essential ISMS elements.

D— Too narrow; ISMS covers all information assets, not just customer records.

Thus, the correct answer isC, which fully represents the CIA triad.

EPI DCFOM-Aligned Reference Concepts (Paraphrased)

ISMS is responsible for protecting confidentiality, integrity, and availability of all information assets.

The CIA triad forms the basis of information security objectives.

Qualitative risk analysis is the process of assessing risks usingdescriptive,non-numerical, andcategoricalscales to evaluate:

Probability (likelihood)

Impact (severity)

It often uses terms like:

Low / Medium / High

Minor / Moderate / Severe

Likely / Unlikely

This analysis supports prioritization, but the definition itself is aboutdescribing impact and probability, not financial quantification.

Why other options are incorrect:

Adescribes quantitative risk analysis (monetary values).

Bis incomplete; qualitative analysis assesses both impact AND likelihood.

Dis an outcome of qualitative analysis, not the definition.

Thus,Cis the correct answer.

EPI DCFOM-Aligned Reference Concepts (Paraphrased)

Qualitative analysis assesses likelihood and impact using descriptive scales.

Used when monetary or statistical values are not required.

In the EPI framework for risk management, after the risk identification and risk analysis steps, therisk evaluationstep determines whether the assessed risks areacceptableorrequire treatmentbased on the organization’s risk appetite, criteria, and the potential impact. The evaluation leads to a decision on whether risk treatment needs to take place.

It isnotsimply compiling all risks (so option C is incorrect).

It isnotexclusively about budgeting (so option D is incorrect) though budgeting follows treatment decisions.

It isnotnecessarily advising to accept all risks (so option B is incorrect) but rather it supports decision-making on treatment.

Therefore, option A is correct: the outcome is the decision whether to treat the risk.

EPI DCFOM-Aligned Reference Concepts (Paraphrased, Not Verbatim)

Risk evaluation assesses identified and analysed risks against risk criteria to decide on acceptability or need for treatment.

The outcome is a documented decision-making step in the risk management process.

EPI’s financial management guidance distinguishes between several internal cost transparency models.Chargebackoccurs when costs are formally billed to internal departments or customers. However, in this scenario, management wants visibility of cost distributionwithoutmaking business units financially responsible. This aligns directly with theShow Backmodel.

Show Back is a non-billing mechanism that reports how much each business unit would hypothetically be charged if costs were allocated proportionally. It improves cost awareness, encourages responsible consumption, and helps management understand operational cost drivers without generating friction associated with real billing. Show Back is commonly used in organizations where financial culture, policy constraints, or strategic choices prevent the use of formal chargeback.

Options A (Chargeback) does not meet the requirement because it transfers costs. Options C and D are not recognized cost transparency models within EPI or general IT financial management practices.

Therefore, the most suitable model for cost transparencywithout financial transferisB – Show Back.

Needs Analysis determineswhat the customer or business requiresfrom a service.

This includes:

Required service hours / operating hours

Availability expectations

Business functional requirements

Legal and compliance requirements

Physical infrastructure needs (power, cooling, space)

Performance and capacity needs

Identifying operating hoursis a core part of defining service requirements.

Why other options are incorrect:

B: Current resource usage is part of infrastructure assessment, not needs analysis.

C: Staffing is part of capability assessment.

D: Monitoring requirements come after service definition and design.

Thus,Ais correct.

EPI DCFOM-Aligned Reference Concepts (Paraphrased)

Needs analysis determines service operation hours, business needs, and requirements.

It precedes capability assessment and service design.

KPOs are strategic and operational performance objectives that must support:

Daily operations

Weekly operational control

Monthly service reporting

Quarterly reviews

Annual strategic planning

EPI emphasizes that performance objectives must be measurableacross multiple timeframes, depending on the operational layer:

Weekly→ short-term operational checks

Monthly→ service-level analysis and trend review

Yearly→ strategic improvement and long-term performance planning

Therefore,weekly, monthly, and yearly intervalsare all suitable for KPOs.

Thus,Dis correct.

EPI DCFOM-Aligned Reference Concepts (Paraphrased)

Performance measurement occurs across multiple time horizons.

KPOs must be aligned to operational, tactical, and strategic levels.

EPI’s document management methodology follows a6-step structured life cyclefor all controlled documentation used in a data center (e.g., SOPs, MOPs, EOPs, safety documents, policies, maintenance procedures).

The life cycle ensures all documents remain current, controlled, traceable, and properly retired.

Thesix recognized stagesin the EPI-aligned document management life cycle are typically:

Creation– The document is drafted and developed.

Review– Subject matter experts verify technical correctness.

Approval– Authorized managers approve it for release.

Publication / Release– Document is issued for operational use under control.

Maintenance / Updates– Regular updates and version control.

Archival / Destruction– Retired versions are archived or securely destroyed.

Within this structure,“Provisioning” isnota recognized document life-cycle stepin EPI’s DCFOM framework.

Provisioning is a term used in IT or service management (e.g., server or user provisioning) but not in document control life cycles.

Therefore,Option C (Provisioning)is the correct answer.

EPI DCFOM-Aligned Reference Concepts (Paraphrased, Not Verbatim)

Document management requires strict version control procedures.

The document life cycle includes creation, review, approval, publication, maintenance, and destruction/archival.

“Provisioning” is not part of the document lifecycle in the EPI framework.