During inventory of assets it is identified that a number of items are in a different location compared to what is indicated on the inventory list.
What is the most likely root cause of this?
Accurate asset management relies heavily on clear, enforced procedures for:
Logging asset movement
Updating location records
Recording installations, removals, or relocations
Maintaining accurate configuration and asset databases
If assets are located in different places than recorded, the root cause is typically:
''Lack of procedures'' or failure to follow them.
Without proper procedures:
Staff may move items without documentation.
Asset updates may not be recorded.
Inventory lists become outdated.
Tracking and audit functions fail.
Why other options are incorrect:
A: Training is important but secondary; without procedures, training has no structure.
C: Most modern asset systems can track locations; the issue is usually process-related, not system capability.
D: Financial constraints do not cause incorrect asset locations.
Thus, B is correct.
EPI DCFOM-Aligned Reference Concepts (Paraphrased)
Asset management accuracy depends on well-defined and enforced procedures.
Incorrect asset locations typically indicate process failures, not financial or system issues.
What is defined by the Recovery Time Objective (RTO)?
In organizational resilience and business continuity planning, the Recovery Time Objective (RTO) is a core metric used to determine the acceptable downtime for each business function.
EPI defines RTO as the:
''Targeted duration within which disrupted services or processes must be restored to a minimum acceptable operational level after a disaster.''
Key points:
Timeframe for Recovery
The RTO identifies how quickly a facility, system, or service must be restored before the outage causes unacceptable consequences.
Minimum Service Capacity
The RTO refers to restoring operations at a minimum acceptable level, not full normal operations.
Business Impact Analysis (BIA) Output
RTO is derived during BIA where criticality and dependencies of business processes are assessed and prioritized.
Prioritization of Resources
RTO informs disaster recovery planning, resource allocation, and restoration sequencing.
Therefore, the correct definition matches:
D --- ''The prioritized timeframes for resuming disrupted activities at a specified minimum acceptable capacity.''
Why the other options are incorrect:
A describes the MTPD (Maximum Tolerable Period of Disruption).
B describes elements of the Minimum Business Continuity Objective (MBCO).
C describes the Recovery Point Objective (RPO).
EPI DCFOM-Aligned Reference Concepts (Paraphrased, Not Verbatim)
RTO defines the permitted downtime for a service.
RTO is linked to minimum acceptable capability after recovery.
RTO is determined through BIA.
Which, of the items below, is not part of operational cost (OPEX)?
Operational Expenditure (OPEX) includes all ongoing costs required to operate and maintain the data center on a day-to-day basis. These costs are recurring and necessary to keep the facility functioning effectively. Examples of OPEX include staffing costs, service contracts, maintenance materials, consumables, utilities, and recurring software licensing fees. Within EPI's Facilities Management guidance, maintenance activities---such as replacing fans, belts, filters, and other wear-and-tear components---are classic OPEX items because they occur during normal operational cycles, contribute to sustaining facility uptime, and repeat regularly over the equipment lifetime.
However, acquisition of real estate is a capital-intensive investment made once during facility development and falls under Capital Expenditure (CAPEX), not OPEX. CAPEX involves large, long-term investments such as land purchase, building construction, major equipment procurement, or infrastructure upgrades. These expenditures are depreciated over years and do not represent operational overhead.
Therefore, the only option not belonging to OPEX is C -- Acquisition of real estate. Staffing, maintenance material replacement, and annual software licenses are standard OPEX items essential for continuous operation, service delivery, and compliance with operational practices.
What is the main reason for (senior) management to be scheduled into the 'on-duty' roster?
Senior management is included in the duty roster to support escalation procedures.
In EPI's operational model:
Managers are not part of routine monitoring or incident handling.
Their role is to intervene only when an incident escalates beyond operational authority, such as major outages, SLA-impacting events, or high-risk situations.
Management provides decision-making, authorization, and resource allocation during escalations.
Why other options are incorrect:
A: Managers should not gain ''hands-on'' experience during incidents.
B: Incident reporting already provides insights; no roster needed.
D: Monitoring thresholds are reviewed separately, not via duty rosters.
Thus, C is correct.
EPI DCFOM-Aligned Reference Concepts (Paraphrased)
Management is involved in the escalation layer, not daily operations.
Duty rosters ensure proper escalation handling and governance.
Data center operators complain about receiving too many non-alarm conditions.
What is the best response?
When operators receive excessive non-alarm notifications, this indicates that:
Thresholds are not well-configured
Events are misclassified
Alarm definitions are incorrect
Monitoring profiles require tuning
EPI's monitoring best practices state that the correct response is to:
Review alarm information and adjust definitions, thresholds, and filtering.
This ensures that:
Only relevant alarms reach operators
Noise is minimized
Operators maintain focus on true issues
SLA-related metrics are accurately monitored
Why other options are incorrect:
A: Training is secondary and will not fix incorrect alarm settings.
C: Ignoring notifications is dangerous and violates operational control.
D: Upgrading software may not resolve the underlying configuration problem.
Thus, B is correct.
EPI DCFOM-Aligned Reference Concepts (Paraphrased)
Monitoring systems must generate actionable alarms, not noise.
Alarm thresholds and event filters must be reviewed and optimized regularly.
Heather Flores
1 day agoSandra Evans
15 days agoElizabeth Thomas
1 month agoLaura Flores
2 months agoNathan Rogers
2 months agoWilliam Miller
3 months agoMargaret Perez
3 months agoJohn Edwards
3 months agoHeather Thomas
3 months agoElizabeth Bell
2 months agoPatricia Morgan
3 months agoAnthony Rogers
3 months agoLudivina
4 months agoJade
4 months agoAnnelle
4 months agoHeidy
4 months agoDanica
5 months agoEric
5 months agoLynelle
5 months agoGlynda
5 months agoGertude
6 months agoLeonor
6 months agoLayla
6 months agoJanella
6 months agoGilma
7 months agoVerlene
7 months agoMarlon
7 months agoLashon
7 months agoHerschel
8 months ago