Intermediate
Certification Prep
#pmp
#project-management
#pmbok
#vocabulary
PMP Vocabulary — Project Management Certification Language
5 exercises — critical path & float, earned value management (PV/EV/AC/CPI/SPI), risk response strategies, RACI matrices, and contingency vs. management reserve. The precise English vocabulary the PMP exam tests.
Why precise PMP vocabulary matters
- Critical path / float — which tasks can slip without delaying the project
- CPI / SPI — numeric, objective language for cost and schedule health
- Avoid / mitigate / transfer / accept / escalate — five distinct risk response strategies, often confused
- RACI — exactly one Accountable owner per task, distinct from Responsible
- Contingency reserve vs. management reserve — known unknowns vs. unknown unknowns
0 / 35 completed
1 / 35
A project schedule shows Task A (5 days) → Task B (3 days) → Task D (2 days) as one path, and Task A (5 days) → Task C (7 days) → Task D (2 days) as another path. Both paths converge at Task D. What is the critical path?
The critical path is the longest sequence of dependent activities through the project network — it determines the minimum time the project can take. Here, A→C→D totals 14 days versus A→B→D at 10 days, so A→C→D is critical.
Key related terms:
Key related terms:
- Float (or slack) — the amount of time a task can be delayed without delaying the project finish date. Critical path tasks have zero float by definition.
- Critical Chain Method — a related scheduling technique that also accounts for resource constraints, not just task dependencies.
2 / 35
A project has Planned Value (PV) = $50,000, Earned Value (EV) = $40,000, and Actual Cost (AC) = $55,000 at the reporting date. What do the Cost Performance Index (CPI) and Schedule Performance Index (SPI) tell the project manager?
Earned Value Management (EVM) formulas: CPI = EV / AC (cost efficiency) and SPI = EV / PV (schedule efficiency). A value below 1.0 for either index signals underperformance; above 1.0 signals overperformance.
Here: CPI = 40,000 / 55,000 ≈ 0.73 — for every dollar spent, only $0.73 of planned work value was earned (over budget). SPI = 40,000 / 50,000 = 0.80 — only 80% of the planned work has been completed by this point (behind schedule).
Other core EVM terms tested on the exam:
Here: CPI = 40,000 / 55,000 ≈ 0.73 — for every dollar spent, only $0.73 of planned work value was earned (over budget). SPI = 40,000 / 50,000 = 0.80 — only 80% of the planned work has been completed by this point (behind schedule).
Other core EVM terms tested on the exam:
- PV (Planned Value) — the budgeted cost of work scheduled to be done by this point
- EV (Earned Value) — the budgeted cost of work actually completed
- AC (Actual Cost) — the real cost incurred for the work completed
- EAC (Estimate at Completion) — the forecasted total cost of the project given current performance
- ETC (Estimate to Complete) — the forecasted cost of the remaining work
- VAC (Variance at Completion) — BAC minus EAC
3 / 35
A risk register lists a risk with the response "Purchase insurance to cover the financial impact if this risk occurs." Which risk response strategy does this represent, and how is it different from mitigation?
Transfer shifts the ownership and/or financial consequence of a risk to a third party, most commonly through insurance, warranties, performance bonds, or outsourcing/contracts. Crucially, transfer does not reduce the probability of the risk occurring or its non-financial impact — it only shifts who bears the cost.
The five negative risk response strategies (PMBOK):
The five negative risk response strategies (PMBOK):
- Avoid — change the project plan to eliminate the threat entirely (e.g. remove a risky scope item)
- Mitigate — take action to reduce the probability and/or impact of the risk (e.g. add extra testing, use a proven technology instead of a new one)
- Transfer — shift the financial impact to a third party (insurance, contract clauses) — the risk event can still happen
- Accept — acknowledge the risk and take no proactive action (passive acceptance), or set aside a contingency reserve for it (active acceptance)
- Escalate — the risk is outside the project manager's authority or the project's scope, so it is raised to programme or portfolio level
4 / 35
In a RACI matrix, the "Marketing Manager" is marked as "C" (Consulted) for the task "Finalise product launch date," while the "Product Owner" is marked as "A" (Accountable). What does this distinction mean in practice?
RACI = Responsible (does the work), Accountable (owns the outcome and has final sign-off — there should be exactly one "A" per task), Consulted (provides input, two-way communication, before or during the work), Informed (receives updates, one-way communication, typically after a decision or milestone).
Here, the Product Owner (Accountable) makes the final call and answers for the outcome, while the Marketing Manager (Consulted) is asked for input — e.g. campaign readiness — before the decision is finalised, but does not have decision authority.
Common exam trap: confusing Responsible and Accountable. Multiple people can be Responsible for pieces of work, but PMI stresses that each task should have exactly one Accountable person to avoid diffusion of ownership. A stakeholder engagement or communications plan will often reference RACI to clarify exactly who needs to sign off versus who just needs updates — precise use of this vocabulary avoids the common workplace confusion of "I thought you were deciding this."
Here, the Product Owner (Accountable) makes the final call and answers for the outcome, while the Marketing Manager (Consulted) is asked for input — e.g. campaign readiness — before the decision is finalised, but does not have decision authority.
Common exam trap: confusing Responsible and Accountable. Multiple people can be Responsible for pieces of work, but PMI stresses that each task should have exactly one Accountable person to avoid diffusion of ownership. A stakeholder engagement or communications plan will often reference RACI to clarify exactly who needs to sign off versus who just needs updates — precise use of this vocabulary avoids the common workplace confusion of "I thought you were deciding this."
5 / 35
A project budget includes $20,000 set aside for "known unknowns" — identified risks with quantified potential cost impact, calculated using quantitative risk analysis — separate from $15,000 held by senior management for "unknown unknowns" that cannot be identified in advance. The first amount is the _____, and the second is the _____.
The contingency reserve ($20,000) covers known unknowns — specific, identified risks in the risk register with an estimated probability and impact, calculated through quantitative risk analysis (e.g. Expected Monetary Value). It is typically part of the cost baseline and can be used at the project manager's discretion for those identified risks.
The management reserve ($15,000) covers unknown unknowns — risks that were not, and could not have been, identified in advance. It sits outside the cost baseline and typically requires approval from management/sponsor before it can be tapped, since it represents budget beyond the performance measurement baseline.
Why this distinction matters on the exam: "cost baseline" or "total project budget" questions often hinge on whether a reserve is included in the baseline (contingency, yes) or added on top of it (management reserve, no). In workplace terms: "we've got contingency for the risks we already know about, but if something totally unexpected happens, that comes out of management reserve and needs sponsor sign-off."
The management reserve ($15,000) covers unknown unknowns — risks that were not, and could not have been, identified in advance. It sits outside the cost baseline and typically requires approval from management/sponsor before it can be tapped, since it represents budget beyond the performance measurement baseline.
Why this distinction matters on the exam: "cost baseline" or "total project budget" questions often hinge on whether a reserve is included in the baseline (contingency, yes) or added on top of it (management reserve, no). In workplace terms: "we've got contingency for the risks we already know about, but if something totally unexpected happens, that comes out of management reserve and needs sponsor sign-off."
6 / 35
git commit -m "Fix: Resolved issue with API endpoint response formatting"
While ensuring the code functions correctly is paramount, this comment goes beyond a simple technical fix. The team lead is emphasizing the need for traceability – documenting changes is critical in project management for understanding decisions made and their impact on the project's overall goals, especially when dealing with API responses. Adding context to the commit message aligns with practices like change control and provides valuable information for future reference during troubleshooting or audits.
7 / 35
PR Description:
"Implemented a new feature to enhance user onboarding. This includes updating the welcome modal and adding a short tutorial video. The API endpoint for user data retrieval has been modified to return JSON formatted results, ensuring compatibility with our mobile application."The question is framed within the context of a Pull Request description. While all options touch on elements of the PR's content, option 3 best captures the project management implication – that documenting the API change demonstrates proactive consideration for future compatibility and integration. Options 1 and 2 minimize the importance of the technical update, while failing to acknowledge its strategic value; documentation is key in PMP vocabulary.
8 / 35
Sarah: 'Okay team, let's quickly review the latest sprint burndown. We're currently at 70% completion and looking good – but I want to flag that our 'Technical Debt' task is significantly behind schedule. It seems we underestimated the complexity of refactoring the legacy codebase. We need to discuss how this impacts our upcoming deliverables and potentially adjust scope.'
As a Project Manager, what specific PMP vocabulary term should Sarah be using to frame this discussion effectively?The correct answer is 'scope creep'.
Sarah is identifying a deviation from the original plan (the technical debt task being behind) and its impact on future deliverables. 'Scope creep' accurately describes this situation – it's the uncontrolled expansion of project requirements which is causing the delay. Options A & B are incorrect because they relate to budget or performance metrics, not the *reason* for the deviation; C is a general term, but doesn't pinpoint the root cause and D refers to the final output, not the underlying problem.9 / 35
Sarah's comment highlights a potential issue impacting the project's schedule. Considering the context of her discussion and the need for clear communication within a PMP framework, what specific term should she use to accurately describe the situation?
During a sprint burndown review, Sarah observes that a key task is significantly behind schedule due to unforeseen complexity, potentially jeopardizing upcoming deliverables. She needs to frame this issue effectively for her team and stakeholders.
Which of the following terms best captures the essence of this situation?
The correct answer is 'Schedule Variance'. Schedule variance directly addresses the difference between planned and actual schedule performance – precisely what Sarah is observing. The other options are related but less specific; 'Scope Creep' refers to uncontrolled changes to the *scope*, not necessarily schedule delays due to complexity; 'Technical Debt' describes a backlog of rework, not the immediate delay itself; and 'Risk Exposure' relates to potential future negative impacts, not the current situation.
10 / 35
git commit -m "Fix: Resolved issue with API endpoint response formatting"
While ensuring the code functions correctly is paramount, this comment goes beyond a simple technical fix. The team lead is emphasizing the need for traceability – documenting changes is critical in project management for understanding decisions made and their impact on the project's overall goals, especially when dealing with API responses. Adding context to the commit message aligns with practices like change control and provides valuable information for future reference during troubleshooting or audits.
11 / 35
PR Description:
"Implemented a new feature to enhance user onboarding. This includes updating the welcome modal and adding a short tutorial video. The API endpoint for user data retrieval has been modified to return JSON formatted results, ensuring compatibility with our mobile application."The question is framed within the context of a Pull Request description. While all options touch on elements of the PR's content, option 3 best captures the project management implication – that documenting the API change demonstrates proactive consideration for future compatibility and integration. Options 1 and 2 minimize the importance of the technical update, while failing to acknowledge its strategic value; documentation is key in PMP vocabulary.
12 / 35
Sarah: 'Okay team, let's quickly review the latest sprint burndown. We're currently at 70% completion and looking good – but I want to flag that our 'Technical Debt' task is significantly behind schedule. It seems we underestimated the complexity of refactoring the legacy codebase. We need to discuss how this impacts our upcoming deliverables and potentially adjust scope.'
As a Project Manager, what specific PMP vocabulary term should Sarah be using to frame this discussion effectively?The correct answer is 'scope creep'.
Sarah is identifying a deviation from the original plan (the technical debt task being behind) and its impact on future deliverables. 'Scope creep' accurately describes this situation – it's the uncontrolled expansion of project requirements which is causing the delay. Options A & B are incorrect because they relate to budget or performance metrics, not the *reason* for the deviation; C is a general term, but doesn't pinpoint the root cause and D refers to the final output, not the underlying problem.13 / 35
Sarah's comment highlights a potential issue impacting the project's schedule. Considering the context of her discussion and the need for clear communication within a PMP framework, what specific term should she use to accurately describe the situation?
During a sprint burndown review, Sarah observes that a key task is significantly behind schedule due to unforeseen complexity, potentially jeopardizing upcoming deliverables. She needs to frame this issue effectively for her team and stakeholders.
Which of the following terms best captures the essence of this situation?
The correct answer is 'Schedule Variance'. Schedule variance directly addresses the difference between planned and actual schedule performance – precisely what Sarah is observing. The other options are related but less specific; 'Scope Creep' refers to uncontrolled changes to the *scope*, not necessarily schedule delays due to complexity; 'Technical Debt' describes a backlog of rework, not the immediate delay itself; and 'Risk Exposure' relates to potential future negative impacts, not the current situation.
14 / 35
git commit -m "Fix: Resolved issue with API endpoint response formatting"
While ensuring the code functions correctly is paramount, this comment goes beyond a simple technical fix. The team lead is emphasizing the need for traceability – documenting changes is critical in project management for understanding decisions made and their impact on the project's overall goals, especially when dealing with API responses. Adding context to the commit message aligns with practices like change control and provides valuable information for future reference during troubleshooting or audits.
15 / 35
PR Description:
"Implemented a new feature to enhance user onboarding. This includes updating the welcome modal and adding a short tutorial video. The API endpoint for user data retrieval has been modified to return JSON formatted results, ensuring compatibility with our mobile application."The question is framed within the context of a Pull Request description. While all options touch on elements of the PR's content, option 3 best captures the project management implication – that documenting the API change demonstrates proactive consideration for future compatibility and integration. Options 1 and 2 minimize the importance of the technical update, while failing to acknowledge its strategic value; documentation is key in PMP vocabulary.
16 / 35
Sarah: 'Okay team, let's quickly review the latest sprint burndown. We're currently at 70% completion and looking good – but I want to flag that our 'Technical Debt' task is significantly behind schedule. It seems we underestimated the complexity of refactoring the legacy codebase. We need to discuss how this impacts our upcoming deliverables and potentially adjust scope.'
As a Project Manager, what specific PMP vocabulary term should Sarah be using to frame this discussion effectively?The correct answer is 'scope creep'.
Sarah is identifying a deviation from the original plan (the technical debt task being behind) and its impact on future deliverables. 'Scope creep' accurately describes this situation – it's the uncontrolled expansion of project requirements which is causing the delay. Options A & B are incorrect because they relate to budget or performance metrics, not the *reason* for the deviation; C is a general term, but doesn't pinpoint the root cause and D refers to the final output, not the underlying problem.17 / 35
Sarah's comment highlights a potential issue impacting the project's schedule. Considering the context of her discussion and the need for clear communication within a PMP framework, what specific term should she use to accurately describe the situation?
During a sprint burndown review, Sarah observes that a key task is significantly behind schedule due to unforeseen complexity, potentially jeopardizing upcoming deliverables. She needs to frame this issue effectively for her team and stakeholders.
Which of the following terms best captures the essence of this situation?
The correct answer is 'Schedule Variance'. Schedule variance directly addresses the difference between planned and actual schedule performance – precisely what Sarah is observing. The other options are related but less specific; 'Scope Creep' refers to uncontrolled changes to the *scope*, not necessarily schedule delays due to complexity; 'Technical Debt' describes a backlog of rework, not the immediate delay itself; and 'Risk Exposure' relates to potential future negative impacts, not the current situation.
18 / 35
git commit -m "Fix: Resolved issue with API endpoint response formatting"
While ensuring the code functions correctly is paramount, this comment goes beyond a simple technical fix. The team lead is emphasizing the need for traceability – documenting changes is critical in project management for understanding decisions made and their impact on the project's overall goals, especially when dealing with API responses. Adding context to the commit message aligns with practices like change control and provides valuable information for future reference during troubleshooting or audits.
19 / 35
PR Description:
"Implemented a new feature to enhance user onboarding. This includes updating the welcome modal and adding a short tutorial video. The API endpoint for user data retrieval has been modified to return JSON formatted results, ensuring compatibility with our mobile application."The question is framed within the context of a Pull Request description. While all options touch on elements of the PR's content, option 3 best captures the project management implication – that documenting the API change demonstrates proactive consideration for future compatibility and integration. Options 1 and 2 minimize the importance of the technical update, while failing to acknowledge its strategic value; documentation is key in PMP vocabulary.
20 / 35
Sarah: 'Okay team, let's quickly review the latest sprint burndown. We're currently at 70% completion and looking good – but I want to flag that our 'Technical Debt' task is significantly behind schedule. It seems we underestimated the complexity of refactoring the legacy codebase. We need to discuss how this impacts our upcoming deliverables and potentially adjust scope.'
As a Project Manager, what specific PMP vocabulary term should Sarah be using to frame this discussion effectively?The correct answer is 'scope creep'.
Sarah is identifying a deviation from the original plan (the technical debt task being behind) and its impact on future deliverables. 'Scope creep' accurately describes this situation – it's the uncontrolled expansion of project requirements which is causing the delay. Options A & B are incorrect because they relate to budget or performance metrics, not the *reason* for the deviation; C is a general term, but doesn't pinpoint the root cause and D refers to the final output, not the underlying problem.21 / 35
Sarah's comment highlights a potential issue impacting the project's schedule. Considering the context of her discussion and the need for clear communication within a PMP framework, what specific term should she use to accurately describe the situation?
During a sprint burndown review, Sarah observes that a key task is significantly behind schedule due to unforeseen complexity, potentially jeopardizing upcoming deliverables. She needs to frame this issue effectively for her team and stakeholders.
Which of the following terms best captures the essence of this situation?
The correct answer is 'Schedule Variance'. Schedule variance directly addresses the difference between planned and actual schedule performance – precisely what Sarah is observing. The other options are related but less specific; 'Scope Creep' refers to uncontrolled changes to the *scope*, not necessarily schedule delays due to complexity; 'Technical Debt' describes a backlog of rework, not the immediate delay itself; and 'Risk Exposure' relates to potential future negative impacts, not the current situation.
22 / 35
Alex (via Slack): 'Just finished implementing the new payment gateway integration. All tests passed!'. Your team lead, John, replies: 'Great, Alex! Can you add a comment to the PR describing the testing process and any potential security considerations?'
This question assesses the importance of detailed documentation in a PMP context. A project manager would expect Alex to clearly articulate the testing methodology and any relevant security aspects – demonstrating thoroughness and risk mitigation. The other options represent insufficient or negligent communication.
It highlights the need for traceability and accountability, key elements within formal project management frameworks.
23 / 35
During a daily standup meeting, Mark states: 'I spent yesterday working on the user authentication module. I hit some unexpected roadblocks with the OAuth flow and had to spend extra time debugging.'
A core principle of PMP communication is proactive risk management. Mark's statement highlights a potential problem that could impact the project timeline. It's crucial for team members to raise issues early, allowing the project manager to assess and mitigate the risks appropriately – this is about transparency and escalation when needed.
This example demonstrates how timely information sharing contributes to effective decision-making and prevents schedule delays.
24 / 35
A PR is submitted with the commit message: 'Fix: Resolved API response timeout issue'. During a code review, you notice the solution was implemented without any associated documentation or justification for the timeout value. What should you recommend to the developer?
This question assesses understanding of documenting decisions. In PMP, every change must be justified and documented to ensure traceability and knowledge transfer. Simply fixing a bug isn't enough; the developer needs to explain why they chose that specific timeout value – demonstrating adherence to quality standards.
This reinforces the importance of 'as-built' documentation as part of project closure and future maintenance.
25 / 35
Emily: 'The stakeholder just requested a completely new feature – adding dark mode to the app! – which wasn't in the original scope. How should I respond as the project manager?
A key aspect of PMP is managing scope changes effectively. Emily must acknowledge the stakeholder's request and formally incorporate it into the project plan. This involves estimating the effort, updating the schedule, and communicating clearly with all stakeholders about the impact.
This scenario demonstrates how a PM handles change requests while maintaining control over the project's objectives.
26 / 35
Maria, the team lead, is discussing a recent delay with the development team during a standup. She states, 'We're experiencing some slippage on the 'Reporting Dashboard' task. It seems we haven't adequately accounted for the complexity of integrating with the legacy data system. What term should Maria use to accurately describe this situation within a PMP context?',
Maria is describing a situation where the plan wasn't sufficiently considered. 'Issue' correctly identifies this as a deviation from the initial plan and necessitates corrective action. 'Risk' implies an unknown future event; 'Constraint' limits options, and 'Dependency' describes a relationship between tasks – none of these fully capture the current scenario. This is a classic example of scope creep impacting schedule.
27 / 35
Alex submits a PR with the commit message: 'Refactor: Improved performance of database queries.' During code review, your manager asks, 'Can you provide some context around this refactoring? What metrics did you use to determine that improvement was needed and how significant is the change?' Which statement best reflects the appropriate response from Alex in a PMP-aligned communication style?
Alex needs to provide quantifiable data and justification for the change. 'The database queries were slow, and I optimized them. The performance increased by 15%.' demonstrates this through concrete metrics, aligning with PMP's emphasis on measurable results. The other options lack specifics and don't demonstrate accountability or transparency – crucial elements in project management communication.
28 / 35
During a Sprint Review meeting, the Product Owner presents a change request: 'We need to add a new field to the user profile that collects dietary preferences.' You, as the Project Manager, should respond by:
This scenario tests understanding of change control within a PMP framework. 'Acknowledging the request and stating it needs further assessment…' demonstrates a structured approach. The Product Owner's request requires evaluation regarding its impact before being incorporated into the project plan – this is standard practice in change management. Accepting immediately or bypassing the process would violate PMP principles.
29 / 35
Sarah sends a Slack message to the team: 'We're behind on delivering features for the new mobile app. The initial estimates were overly optimistic and didn't account for the complexity of integrating with the legacy backend.' Which term best describes Sarah's situation from a PMP perspective?
This question tests understanding of schedule management within PMP's scope. 'Schedule Variance…' accurately reflects the situation – a discrepancy between planned and actual timelines, driven by underestimated effort. While 'Scope Creep' is related, it describes uncontrolled requirements changes; 'Poor Estimation' identifies the root cause, and 'Resource Allocation' refers to distribution of resources.
30 / 35
John is leading a daily standup. David reports: 'I've been working on the data migration script, and I'm encountering some issues with data validation – it's taking longer than anticipated.' Considering John's role as a Project Manager and the need for proactive risk management within a PMP framework, what term should he immediately use to address David's situation?
John should use 'High Priority Risk' because David's report indicates a potential impact on the project schedule and critical path. This aligns with PMP principles of identifying and managing risks proactively. The other options misrepresent the severity or appropriate response to a delay impacting dependent tasks.
31 / 35
Maria is reviewing a PR submitted by Ben. The commit message reads: 'Refactor: Optimized database queries for improved performance.' During the code review, she asks Ben to provide more context. Which of the following responses would demonstrate Maria's understanding of a key PMP concept – specifically, traceability?
Maria needs Ben to articulate how the changes relate back to project requirements and objectives. Option 2 demonstrates traceability by referencing a measurable metric (response time) and explicitly connecting it to the original performance goals. The other options lack this critical link.
32 / 35
Emily is managing a project with a stakeholder requesting a significant change – adding a new feature to the user interface. She needs to formally document this request. Which of the following statements best reflects Emily's approach to managing scope changes within a PMP context?
Emily must initiate a structured change management process. A formal Change Request ensures proper assessment of the impact (schedule, cost, resources) before committing to any modifications. This aligns with PMP's emphasis on controlled changes and minimizing scope creep.
33 / 35
Sarah is updating a PR description: 'Implemented a new feature to enhance user onboarding.' She realizes she needs to be more precise. Which of the following additions would best demonstrate Sarah's understanding of a crucial aspect of PMP documentation?
Sarah's updated description should explicitly link the change to its intended outcome – the 'onboarding process goals'. This demonstrates traceability and provides context for future reference. The other options are too vague or lack specific connection to project objectives.
34 / 35
John needs to update the project's risk register. A new risk has emerged: a potential security vulnerability in a third-party library. Which of the following actions best reflects his understanding of a Project Management Professional (PMP) approach?
The PMP methodology emphasizes proactive risk management. Option 0 reflects this by prioritizing remediation – preventing the vulnerability from becoming a problem. Options 1 and 2 demonstrate reactive, not proactive, approaches. Option 3 is delegating responsibility without proper assessment.
35 / 35
Maria, the team lead, needs to communicate a change in priorities to the development team. Considering the need for transparency and alignment within a PMP framework, what's the most effective way to frame this update?
Option 1 clearly communicates the shift in priorities while acknowledging external factors. It maintains transparency and justifies the change. Options 2, 3 and 4 are dismissive or lack context, which is not aligned with PMP principles of clear communication.
Frequently Asked Questions
What will I practice in "PMP Vocabulary — Project Management Certification Language"?
This is a Certification Prep exercise set. It walks through 35 scenario-based multiple-choice questions built around real usage of Certification Prep terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 35 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Certification Prep vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Certification Prep exercises?
See the Certification Prep exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Certification Prep vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.