Technical Writing Diagnostic 3 — Questions and Answers
Question 1: Which element is MOST important to define before beginning any technical writing project?
- Page layout and font size
- Audience, purpose, and scope (Correct answer)
- Number of visuals to include
- Publication platform
Correct answer: Audience, purpose, and scope
Knowing the audience, purpose, and scope shapes every decision about content, tone, and format in a document.
Question 2: In a user manual, what is the recommended way to write a warning about potential equipment damage?
- Mention it in a footnote at the end of the section
- Place a clearly labeled CAUTION or WARNING notice before the relevant step (Correct answer)
- Include it in the introduction only
- Use italic text within the body paragraph
Correct answer: Place a clearly labeled CAUTION or WARNING notice before the relevant step
Standards like ANSI Z535 require safety notices to appear before the step they relate to so users see them in time.
Question 3: What is 'chunking' in technical writing?
- Dividing a document into large, dense paragraphs
- Breaking content into small, logically grouped units for easier scanning (Correct answer)
- Removing all transitions between sections
- Combining multiple procedures into a single step
Correct answer: Breaking content into small, logically grouped units for easier scanning
Chunking organizes information into discrete, manageable blocks, improving readability and comprehension.
Question 4: A technical writer must document a REST API. Which format is MOST useful for developers consuming this documentation?
- A narrative essay describing the API's history
- Reference tables with endpoints, parameters, request/response examples, and error codes (Correct answer)
- A FAQ section only
- A glossary of programming terms
Correct answer: Reference tables with endpoints, parameters, request/response examples, and error codes
Developers need precise, structured reference information including endpoints, parameters, and examples to integrate APIs effectively.
Question 5: Which revision strategy BEST improves the clarity of a complex technical sentence?
- Add more qualifying clauses to provide context
- Break the sentence into shorter sentences, each expressing one idea (Correct answer)
- Replace all technical terms with synonyms
- Convert the sentence to a question
Correct answer: Break the sentence into shorter sentences, each expressing one idea
Short, focused sentences reduce cognitive load and make complex technical information easier to parse.
Question 6: What is the purpose of a style guide in technical writing?
- To define the aesthetic preferences of the lead writer
- To ensure consistency in language, formatting, and terminology across documents (Correct answer)
- To list all approved graphics for the organization
- To track document version history
Correct answer: To ensure consistency in language, formatting, and terminology across documents
A style guide establishes standards that keep all team members aligned on tone, terminology, and formatting conventions.
Question 7: When writing for a novice audience, which approach is MOST effective?
- Use advanced jargon to build their vocabulary
- Define technical terms, use analogies, and avoid unnecessary complexity (Correct answer)
- Assume readers will look up unfamiliar terms independently
- Include only technical diagrams without explanations
Correct answer: Define technical terms, use analogies, and avoid unnecessary complexity
Novice audiences need definitions, relatable analogies, and simplified language to build understanding from the ground up.
Which element is MOST important to define before beginning any technical writing project?