EXIN CDCE common mistakes
EXIN CDCE · Understand the traps and how to avoid them.
Treating availability tier levels as a simple ladder (Tier I lowest, Tier IV highest) and assuming a Tier III design automatically delivers Tier III performance, instead of separating topology/concurrently maintainable design from actual operational capability.
Candidates memorise tier numbers and redundancy labels (N, N+1, 2N) from marketing material and never learn that the standard distinguishes design documents from demonstrated operation, so they answer definitional questions by rank rather than by the specific criterion being tested.
What to do instead
Build a two-column comparison for each tier: design attributes (distribution paths, concurrent maintainability, fault tolerance) versus operational evidence (documented processes, training, maintenance procedures). Practise questions by first identifying whether the stem asks about design or operation, then answer from that column only.
Answering cooling questions with a single metric such as room temperature, ignoring the interaction of supply air temperature, airflow volume, humidity and rack inlet conditions when evaluating a scenario.
Candidates study cooling as a list of equipment types (CRAC, CRAH, in-row, rear-door) and memorise one or two setpoints, so they miss scenario stems that describe hot spots, bypass airflow or containment problems where the correct answer depends on airflow management rather than equipment selection.
What to do instead
Learn to reason from the heat-load path: heat generated at the rack, air delivered to the inlet, air returned, and where mixing or bypass occurs. For each practice scenario, write down which of the four variables is being changed and what it does to inlet temperature before looking at the options.
Confusing power capacity terms - installed UPS rating, usable IT load, power usage effectiveness and redundancy configuration - and selecting an answer that quotes the wrong quantity.
The numbers appear similar and candidates memorise formulas without tracking units and boundaries (facility total versus IT load), so they compute correctly but apply the result to the wrong question.
What to do instead
Write out each definition with its numerator and denominator or boundary explicitly, and unit-test yourself with a small worked example: given a facility drawing 500 kW with 250 kW of IT load, compute PUE and state what a value of 1.0 would mean. Label every answer option with the quantity it represents before choosing.
Treating standards and codes as interchangeable and citing the wrong instrument - for example answering a question about design requirements with a management-system standard, or a question about certification with a code requirement.
Candidates group all standards into one mental bucket labelled 'compliance' and never map each document to its actual scope, so they pick the most familiar name rather than the one that governs the situation described.
What to do instead
Create a scope map listing each standard or framework you study, one line on what it covers and one line on what it does not. For every practice question, name the governing document and its purpose before evaluating options; if you cannot, mark the item for review rather than guessing.
Assuming a certificate or completed audit means an operation is compliant, rather than recognising that compliance depends on continuing evidence, corrective action and management review.
Candidates equate certification with a permanent state and overlook the audit cycle, nonconformity handling and continual improvement elements that exam stems probe with 'what should be done next' phrasing.
What to do instead
Learn the audit and corrective-action cycle as a sequence: finding, root-cause analysis, corrective action, verification, management review. Practise 'next step' questions by locating the scenario on that sequence and choosing the action that follows the described stage.
Ignoring change management and maintenance-window discipline in operations scenarios, choosing the technically fastest fix instead of the controlled one.
Candidates with a technical background default to engineering instinct - swap the component, restart the system - and underestimate how heavily operations questions weight procedure, risk assessment, approval and rollback planning.
What to do instead
For every operations scenario, apply a fixed checklist: what is the risk, who must approve, what is the rollback, what is the communication plan, what evidence is recorded. Answer with the option that satisfies the checklist even when a quicker technical fix is offered.
Mixing up preventive, predictive and corrective maintenance and selecting the wrong strategy for a described failure pattern or criticality.
The terms are learned as vocabulary rather than as decision tools, so candidates cannot connect a scenario (intermittent degradation, condition monitoring data, a failed unit) to the maintenance approach that fits it.
What to do instead
For each maintenance type, note the trigger (calendar, condition, failure) and the type of asset it suits. Work through short scenarios and state the trigger before choosing; if the stem mentions sensor readings or trend data, predictive is usually indicated, and if it mentions a completed failure, corrective.
Treating capacity planning as a one-off exercise at commissioning rather than a continuing process linked to business demand and refresh cycles.
Candidates associate capacity with design documents and forget the management domain's emphasis on forecasting, monitoring actual utilisation and planning for growth or consolidation, so they miss questions about when to act on utilisation trends.
What to do instead
Learn the capacity cycle: forecast demand, measure actual utilisation, compare against thresholds, plan remediation, review. Practise questions that give utilisation percentages or growth rates and ask what the manager should do; the answer is usually the step that closes the gap between forecast and measurement.
Answering risk questions by listing threats only, without assessing likelihood, impact, mitigation and residual risk, or without assigning ownership.
Candidates treat risk as a vocabulary topic and produce threat lists, which fails stems asking for the next step in risk treatment or the purpose of a specific control.
What to do instead
Use a fixed four-part structure for every risk scenario: identify the asset and threat, estimate likelihood and impact, select a treatment (avoid, reduce, transfer, accept), then state the residual risk and owner. Answer with the option that completes the structure rather than the one that names the most threats.
Choosing the most technically sophisticated option in management and strategy questions, ignoring cost, business alignment and total cost of ownership.
Candidates prepare heavily on technical content and carry that bias into management items, where the expected answer is usually the option balancing service level, cost and business need rather than maximum redundancy or newest technology.
What to do instead
For management-domain questions, screen options against three filters before answering: does it meet the stated service level, is the cost proportionate, and does it align with the business requirement in the stem. Eliminate any option that adds capability the stem did not ask for.