5-question quiz on DORA metrics and the key measures platform teams use to track success. Advanced
0 / 10 completed
1 / 10
A platform team reports reducing "team onboarding time from five days to four hours." What does the onboarding time metric measure in a platform engineering context?
Correct: B. Platform onboarding time measures the new-team experience end-to-end: from "I want to use the platform" to "I have a service running in production." Reducing it from five days to four hours represents a fundamental improvement in platform usability and self-service capability — a signal that the golden path and documentation are working.
Metric
What it measures
Team onboarding time
New team: first platform access → first production deployment
Time-to-first-deployment
New service repo → that service running in production
2 / 10
A platform engineer says: "We optimised our golden path so that time-to-first-deployment is now under two hours for new repos." What does time-to-first-deployment measure?
Correct: B. Time-to-first-deployment (sometimes called "T2FD") is a platform-level metric capturing the full onboarding journey for a new service. It includes scaffolding, pipeline setup, configuration, and initial deploy. A sub-two-hour T2FD indicates the platform's golden path is genuinely self-service and well-documented.
What it includes
What it excludes
Service scaffolding, pipeline setup, configuration, first deploy
An engineering director asks about "platform adoption rate" during a quarterly platform review. What does platform adoption rate measure?
Correct: B. Platform adoption rate answers: "Of all the teams that could be using this platform, how many actually are?" It is typically expressed as a percentage of eligible engineering teams or active developers. High adoption validates the platform's value proposition; low adoption signals friction, missing features, or a trust problem that needs investigation.
Adoption rate signal
Possible interpretation
High adoption (>70 %)
Platform delivers clear value; friction is low
Low adoption (<30 %)
Onboarding friction, missing features, or competing alternatives still preferred
4 / 10
The platform's MTTR last quarter was 47 minutes, and an SRE is pushing to reduce it. What does MTTR measure in the context of a platform team?
Correct: B. MTTR (Mean Time to Restore) measures the average duration of incidents — from detection to restoration. For a platform team, reducing MTTR is critical because every minute of platform downtime blocks multiple stream-aligned teams from deploying. MTTR is one of the four DORA metrics used to assess software delivery performance.
DORA metric
What it measures
Deployment frequency
How often code ships
Lead time for changes
Commit → production duration
MTTR
Detection → restoration duration
Change failure rate
% changes that cause incidents
5 / 10
A platform team's change failure rate for Q1 is 8 %, which triggers a reliability review. What does change failure rate measure?
Correct: B. Change failure rate (CFR) is one of the four DORA metrics. It measures the fraction of deployments that cause production problems requiring a hotfix, rollback, or incident response. An 8 % CFR means 1 in 12 platform changes causes a problem — above elite performers (0–15 % is considered medium; elite is under 5 %). A review would look at testing coverage, canary deploy usage, and change management practices.
CFR band
DORA category
0–5 %
Elite performer
5–15 %
High performer
15–30 %
Medium performer
6 / 10
Sarah (Senior Platform Engineer) posted in the #platform-metrics Slack channel: 'Our average API response time has dropped from 300ms to 150ms. This is fantastic!' What key metric is Sarah primarily reporting on?
Sarah is reporting on API response time, which directly measures the latency experienced by users interacting with the platform's APIs. It's crucial to understand that while other metrics like request volume are related, response time itself isolates the performance of individual operations. Focusing solely on latency doesn't account for the overall system health.
7 / 10
Reviewer: 'This PR introduces a new logging statement. Can you add a metric to track the number of times this log is triggered?' What type of metric would be most appropriate in this scenario?
Event count is ideal here because it directly measures the occurrence of a specific log event. This provides insight into potential issues or anomalies within the application and allows you to track its usage over time. Rate-based metrics are useful for fluctuating workloads but don't pinpoint the *cause* of increased logging.
8 / 10
You're writing a PR description for a change that reduces the platform's 'error rate'. Which of the following phrases best describes what you should be measuring?
The 'error rate' is best defined as the percentage of requests that result in an error response. This provides a quantifiable measure of system stability and reliability – a key focus for platform metrics. While other metrics like latency are important, they don't directly capture the core concept of errors.
9 / 10
During your daily stand-up, you're asked about the platform's 'stability score'. What does this metric likely represent?
A 'stability score' is almost certainly a composite metric combining several key indicators – like error rate and MTTR - along with availability. This gives a holistic view of system health rather than relying on any single factor which might be misleading. It's an aggregation designed to quickly assess platform reliability.
10 / 10
David (Platform Manager) mentions that the 'percentage of deployments failing' is currently at 5%. What does this metric primarily indicate?
A high deployment failure rate signals problems within the deployment pipeline – whether it's related to testing, infrastructure provisioning, or integration. Monitoring this percentage helps identify bottlenecks and proactively address issues that impact release velocity.
What will I practice in "Platform Metrics Language — Exercises"?
This is a Platform as a Product exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of platform as a product 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 10 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 platform as a product 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 Platform as a Product exercises?
See the Platform as a Product 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 — platform as a product vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.