Developer Survey & Feedback
Learn the IT-English vocabulary of developer surveys: open-ended questions, sentiment, response rate, NPS and actionable insights.
0 / 45 completed
1 / 45
A survey uses an 'open-ended question'. What does that mean?
Open-ended questions let respondents answer in their own words, surfacing richer feedback.
2 / 45
A DevRel reports 'developer sentiment is improving'. What is sentiment?
Sentiment is the emotional tone of feedback — how positive or negative developers feel.
3 / 45
A low 'response rate' is a concern. What does response rate measure?
Response rate is the share of those invited who responded; low rates risk unrepresentative results.
4 / 45
The team wants 'actionable insights' from the survey. What does that mean?
Actionable insights point to specific changes the team can make, not just vague observations.
5 / 45
Which sentence correctly uses 'NPS'?
NPS (Net Promoter Score) gauges willingness to recommend, a common loyalty/satisfaction metric.
6 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
7 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
8 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
9 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
10 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
11 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
12 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
13 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
14 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
15 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
16 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
17 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
18 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
19 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
20 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
21 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
22 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
23 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
24 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
25 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
26 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
27 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
28 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
29 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
30 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
31 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
32 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
33 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
34 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
35 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
36 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
37 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
38 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
39 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
40 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
41 / 45
Sarah: "Hey team, I've just reviewed the recent developer survey data. The average satisfaction score for our new API is only 3.2 out of 5. What's the best way to communicate this concern to the product manager?"This scenario presents a realistic code review situation. While a low satisfaction score (3.2) *is* concerning, framing it as 'critical' might overstate the immediate urgency and could lead to unnecessary panic. 'Adequate' is incorrect because simply noting the feedback isn't proactive; the team needs to explain the implications. Communicating it as 'adequate' risks downplaying a genuine problem by not suggesting any further action.
42 / 45
David: "I just submitted a PR with the changes for the user authentication flow. The survey results show that developers are consistently rating the error messages as 'unhelpful' – specifically mentioning they're too technical and lack clear guidance. Should I include this feedback in my PR description?"This scenario focuses on effectively communicating survey data within a code review context. While all options touch upon aspects of communication, 'adequate' is the most appropriate response because it concisely summarizes the key feedback (unhelpful error messages) directly tied to David's PR changes. The other options either misrepresent the purpose of a PR description or fail to connect the feedback to the specific code being reviewed. A good PR description should quickly highlight important issues for reviewers.
43 / 45
John: "Okay team, I've analyzed the feedback from the recent survey regarding our new logging service. A significant number of developers (approximately 45%) reported difficulty understanding the default configuration options. They described them as 'opaque' and 'overwhelming.' What's the most effective way to phrase this finding when presenting it to the engineering leadership?"The question focuses on effectively communicating survey findings to leadership. Options A and B are incorrect because they suggest either ignoring or over-complicating the feedback. Option C highlights the importance of concisely summarizing key issues with supporting evidence (specific examples), which is crucial for driving action. Option D emphasizes the need for clarity, but doesn't address *how* to present complex data – a summary allows leadership to quickly grasp the problem and decide on next steps.
44 / 45
Mark: "I'm updating the PR description for this feature. The survey shows developers are frequently using the term 'edge case' to describe scenarios that aren't actually problematic. Should I include a note suggesting we clarify its meaning within our documentation?"The question focuses on the interpretation of survey feedback. While 'edge case' might seem confusing to some, the correct answer acknowledges its frequent use as a *descriptor* in the survey. The other options misinterpret the feedback – either overemphasize the importance of edge cases or dismiss the data entirely. Including clarification would be genuinely useful for developers who are using the term in their own way.
45 / 45
Liam: "Hey team, I'm drafting the PR description for this new payment processing module. The survey results show a high percentage of developers (around 65%) are struggling to understand how to integrate with our existing SDK. They're using terms like 'callback' and 'asynchronous' repeatedly, but seem confused about the overall flow. What's the most effective way to highlight this issue in my PR description?" This question focuses on clear communication within a code review scenario. The correct option provides a direct and understandable summary of the survey findings, using language suitable for a PR description. The other options either overcomplicate the issue (option 1), provide an excessively detailed explanation that might overwhelm the reader (option 3), or suggest an unproductive course of action (option 4). It's important to distill complex feedback into easily digestible statements.
Frequently Asked Questions
What does the "Developer Survey & Feedback" exercise cover?
Learn the IT-English vocabulary of developer surveys: open-ended questions, sentiment, response rate, NPS and actionable insights.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Developer Survey & Feedback"?
This exercise has 45 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Developer Relations exercises?
Browse the full Developer Relations hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.