Internal Wiki and Knowledge Base Writing (English)
Practice the vocabulary and best practices for writing internal wikis and knowledge bases: structure, discoverability, and maintenance.
0 / 48 completed
1 / 48
What distinguishes a 'knowledge base' from a 'wiki' in a corporate context?
While often used interchangeably, knowledge bases typically have more structure and editorial oversight (especially customer-facing ones). Wikis tend to be open, collaborative, and grow organically.
2 / 48
What is a 'single source of truth' (SSOT) in documentation strategy?
SSOT means each fact, process, or decision has exactly one canonical source. Duplicating documentation causes drift — one version gets updated and the other doesn't, leading to conflicting information.
3 / 48
What is 'information architecture' in the context of an internal wiki?
Information architecture determines whether your wiki is findable. Poor IA means useful content exists but nobody can find it. Good IA uses clear naming, consistent structure, and logical groupings.
4 / 48
What does 'orphaned page' mean in a wiki context?
Orphaned pages exist in the wiki but are not linked from anywhere. They are invisible to users browsing the wiki unless they search specifically. Regular wiki audits should identify and link or archive orphaned pages.
5 / 48
Which principle should guide the 'freshness' of a knowledge base article?
Knowledge bases degrade if not maintained. Displaying last-reviewed dates and flagging stale content (e.g., 'This article was last reviewed 8 months ago — verify before following') maintains reader trust.
6 / 48
What is 'progressive disclosure' in knowledge base writing?
Progressive disclosure shows summaries first and lets readers drill down for details. A wiki article might start with a one-paragraph summary, then provide a detailed guide in expandable sections.
7 / 48
What is the purpose of 'tagging' or 'labels' in a wiki or knowledge base?
Tags allow cross-cutting categorization. A page about 'deploying to production' might be tagged with both 'deployment' and 'on-call-runbook', making it findable via either tag even if its location in the wiki hierarchy is under 'operations'.
8 / 48
Which sentence is an example of good knowledge base article writing?
Good knowledge base articles are actionable: numbered steps, specific commands or actions, expected outcomes. Vague references to other pages or team leads create friction and defeat the purpose of a knowledge base.
9 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
10 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
11 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
12 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.13 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
14 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
15 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
16 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
17 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.18 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
19 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
20 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
21 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
22 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.23 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
24 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
25 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
26 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
27 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.28 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
29 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
30 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
31 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
32 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.33 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
34 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
35 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
36 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
37 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.38 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
39 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
40 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
41 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
42 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.43 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
44 / 48
John: "Hey team, I'm stuck on how to handle the new OAuth2 flow for our API. The documentation is…sparse."This scenario highlights the need for an internal wiki or knowledge base. John's frustration demonstrates that the existing documentation is inadequate; a well-maintained resource would provide step-by-step instructions, code examples (like the OAuth2 flow), and potential troubleshooting steps specifically tailored to the team's needs. Simply asking for help without context doesn't address the underlying issue of missing information—the goal is to proactively provide developers with the knowledge they need to solve problems quickly.
45 / 48
Sarah: "Hey team, I'm reviewing this PR for the new user onboarding flow. The wiki article on 'Account Verification' is really unclear about the expected API response format after a successful verification attempt. It just says '200 OK' and doesn't provide any example JSON or details on what fields are required. This is making it difficult to validate the code against the specification."This scenario focuses on a common pain point when developing internal knowledge bases. Sarah isn't simply stating that the documentation is bad; she's articulating a specific issue: a lack of concrete examples for the expected API response after account verification. The correct answer recognizes this needs to be addressed by adding more detail, particularly an example JSON payload, which would allow developers to accurately validate their code against the specification. The other options misinterpret Sarah's concern – it's about documentation clarity, not a direct bug in the PR itself.
46 / 48
David: "I'm trying to troubleshoot this intermittent error with the payment processing service. I've added a comment to the relevant wiki page about it, but it still seems to be happening. Should I flag this for someone more senior?"The key here is understanding the role of a knowledge base in troubleshooting. Simply adding a comment doesn't guarantee resolution; rather, it should be part of a process of documenting and tracking an issue. Monitoring the page for updates or new comments demonstrates proactive engagement and allows others to contribute to the solution, while escalating immediately might be premature without further investigation. Deleting the comment would hinder collaborative problem-solving.
47 / 48
John is writing a comment on the company wiki regarding a complex new feature. He writes: 'This page needs more detail about how to handle rate limiting with the external service. It just mentions 'respect the limits' – that's not helpful!' Which of the following best describes
John's concern and what action he should take regarding this wiki page?
John's comment highlights a significant issue: vague guidance can have serious consequences in a technical environment. Simply stating 'respect the limits' isn't actionable; developers need concrete details about thresholds, error handling, and potential impact. The correct answer reflects this urgency – rate limiting failures can directly affect service availability and performance, making immediate attention crucial for mitigation and preventing further problems. Options A & B are too simplistic; Option C minimizes the problem's severity, while Option D is completely inaccurate.48 / 48
Sarah is reviewing a PR and notices the wiki article on 'Account Verification' lacks crucial details. The article simply states '200 OK' after successful verification but doesn't provide example JSON or required field information. This makes validating the code difficult.
Which of the following actions best addresses Sarah's concern regarding the wiki page?
The correct answer highlights the importance of providing concrete examples within a knowledge base. Simply stating '200 OK' is insufficient; developers need tangible data to understand expected behavior and validate their code. Flagging for the API team (Option B) delays progress unnecessarily. Editing immediately (Option A) without referencing the source specification could introduce inaccuracies, while ignoring the problem (Option D) is a poor solution as it leaves the developer struggling. Providing an example based on the specification ensures consistency and clarity within the knowledge base.
Frequently Asked Questions
What does the "Internal Wiki and Knowledge Base Writing (English)" exercise cover?
Practice the vocabulary and best practices for writing internal wikis and knowledge bases: structure, discoverability, and maintenance.
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 "Internal Wiki and Knowledge Base Writing (English)"?
This exercise has 48 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 Documentation Types exercises?
Browse the full Documentation Types 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.