1.2. Prepare Documentation to Summarize a Customer Interaction. 100-140 Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which statement best describes a clear and concise problem description in IT support documentation?

   • AA detailed narrative of the user's emotional reaction to the issue
   • BA factual summary that includes the issue, affected system, and observed symptoms without ambiguity
   • CA brief note stating only the final resolution, omitting the original problem
   • DA list of every possible cause the technician considered, even if not tested
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   While troubleshooting a login issue, you try three different fixes. The first two fail, and the third succeeds. You are writing the ticket. How should you document the troubleshooting steps?

   • ADocument all three attempts in order, noting the outcome of each, and highlight the successful one.
   • BDocument the first and third attempts, skipping the second to save time.
   • CDocument the steps in reverse order to show the final solution first.
   • DDocument only the successful fix to keep the ticket concise.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   Your IT team maintains a shared knowledge base. You are about to add a new article about a common printer issue. To ensure the article is easily searchable and understandable, which practice is most important?

   • AUse unique terminology for each article to avoid duplication.
   • BWrite the article in a casual tone with personal anecdotes to make it relatable.
   • CInclude every possible variation of the issue in one long article.
   • DUse consistent keywords and a standard template that includes symptom, cause, and resolution.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   During a support call, you run several commands to diagnose a network issue. You need to document the troubleshooting steps for the ticket. Which approach best follows documentation best practices?

   • AList each command and its output in the order you ran them, noting what each result indicated.
   • BSummarize the final conclusion and skip the intermediate commands to keep the ticket short.
   • CWrite a narrative paragraph describing your thought process without specific commands.
   • DAttach a screenshot of the terminal and add no text explanation.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   Which of the following is the best example of documenting a troubleshooting step?

   • ATried to fix the network issue.
   • BRan ipconfig /flushdns and observed that the command completed successfully.
   • CThe user was asked to restart the computer.
   • DChecked the network settings and they were fine.
   Reveal Solution Discussion Select an answer first