This set builds vocabulary for tracing and diagnosing application performance regressions.
0 / 5 completed
1 / 5
At standup, a dev mentions a captured record of a single request's full timing breakdown across frontend rendering, network, and backend processing. What is this called?
A performance transaction, or trace, captures the full timing breakdown of a single request as it moves across frontend rendering, network transit, and backend processing, giving a unified view of where time was actually spent. This granularity lets an engineer pinpoint the specific stage responsible for a slow experience rather than guessing. It's the foundational unit that performance monitoring tooling is built around.
2 / 5
During a design review, the team wants to identify which specific database query is responsible for the majority of a slow endpoint's total response time. Which capability supports this?
A span-level breakdown decomposes a transaction into its individual operations, like a specific database query or external API call, showing exactly how much time each contributed to the total response time. This granularity turns a vague "this endpoint is slow" observation into a precise, actionable target for optimization. It's a core capability of any performance monitoring tool built around distributed tracing.
3 / 5
In a code review, a dev configures an alert to fire when the 95th percentile response time for a critical endpoint exceeds a defined threshold. What does this represent?
Percentile-based alerting, like tracking the 95th percentile response time, catches degradation affecting a meaningful share of slower requests that a simple average could mask by being pulled down by many fast, unaffected requests. This is a more representative signal of the experience for users on the tail end of the performance distribution. Percentile-based thresholds are a standard practice for performance-related alerting rather than relying on averages alone.
4 / 5
An incident report shows a performance regression was missed because the team only monitored average response time, which stayed flat while a subset of requests slowed dramatically. What practice would prevent this?
An unchanged average response time can hide a real regression affecting a smaller but significant subset of requests, since a few dramatically slower requests can be diluted by many unaffected fast ones. Monitoring percentile metrics like p95 or p99 alongside the average surfaces this kind of tail-latency regression that an average alone would miss. This combination is standard practice for performance monitoring that aims to reflect real user experience accurately.
5 / 5
During a PR review, a teammate asks why the team uses span-level transaction tracing instead of relying only on a single aggregate response time metric. What is the reasoning?
A single aggregate response time metric confirms that a request was slow but gives no insight into which specific step, like a query or external call, actually caused it, while span-level tracing breaks the request down into its component operations. This detail is what turns a vague performance alert into an actionable debugging starting point. The tradeoff is the added instrumentation and data volume required to capture this granularity.
What does the "Sentry Performance Monitoring Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to sentry performance monitoring vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.