Each question below shows the correct answer with a full explanation. Use these to build conceptual understanding before attempting a timed quiz.
Communication & Documentation of SolutionsEasy
Q1. Why documentation important?
- A.It is completely unnecessary to do
- B.Only managers need to read the docs
- C.It wastes time that could be coding
- D.Records solutions for understanding/reuse✓ Correct
Explanation
Enables understanding and reuse.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q2. What is a code comment?
- A.A variable declaration in the code
- B.Social feedback on the project
- C.An error in the source code
- D.Text explaining code, compiler ignores✓ Correct
Explanation
Explanatory ignored text.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q3. Good docs include?
- A.Only the final answer or result
- B.Problem, approach, usage, examples✓ Correct
- C.Only the raw source code itself
- D.Only variable names and types
Explanation
Comprehensive documentation.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q4. What is a README?
- A.A personal diary for the developer
- B.A system log of all the events
- C.A configuration file for the app
- D.Introduces project with purpose/setup✓ Correct
Explanation
Project introduction.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q5. Why clear communication?
- A.Alignment on problems and solutions✓ Correct
- B.It is only needed for presentations
- C.It is not important for the team
- D.It slows down the project progress
Explanation
Reduces misunderstanding.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q6. Why clear names?
- A.To confuse other developers reading
- B.They create self-documenting code✓ Correct
- C.To make the code look fancy
- D.Variable names do not matter at all
Explanation
Convey purpose.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q7. What is user manual?
- A.A tutorial for learning to code
- B.End-user software usage instructions✓ Correct
- C.Source code documentation for devs
- D.A developer guide for the APIs
Explanation
End-user instructions.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q8. What is changelog?
- A.A debug log of runtime errors seen
- B.Chronological notable changes per version✓ Correct
- C.An error log of system failures
- D.A log of all user passwords used
Explanation
Version change record.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q9. Why document approach?
- A.It is a waste of team time
- B.No one reads documentation anyway
- C.Review thinking, learn, and share✓ Correct
- D.It makes the project much harder
Explanation
Learning and sharing.
Report an error in this question
Communication & Documentation of SolutionsEasy
Q10. What is a bug report?
- A.Defect with repro steps and details✓ Correct
- B.A proposal for new feature ideas
- C.A financial report for the project
- D.A report about actual insects found
Explanation
Defect documentation.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q11. What is API documentation?
- A.A marketing brochure for the app
- B.Describes endpoints, params, examples✓ Correct
- C.Internal code comments only written
- D.A testing plan for quality checks
Explanation
API usage guide.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q12. What is technical spec?
- A.A user guide for end-user features
- B.Detailed technical design and architecture✓ Correct
- C.A marketing brochure for clients
- D.A sales pitch for stakeholders
Explanation
Architecture details.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q13. Inline vs block comments?
- A.Block comments are for single lines
- B.Inline: single line; block: section✓ Correct
- C.Inline comments are always longer
- D.They are exactly the same thing
Explanation
Line vs section level.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q14. What is RFC/design doc?
- A.Change proposal with rationale given✓ Correct
- B.A financial budget document for project
- C.A test plan for quality assurance
- D.A bug report filed by the team
Explanation
Proposed changes.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q15. Documentation-driven development?
- A.Only writing docs for bugs that are found
- B.Avoiding all documentation in the project
- C.Write docs before code to clarify design✓ Correct
- D.Writing docs only after the project ends
Explanation
Docs-first clarity.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q16. What is UML?
- A.Just drawing pictures for fun only
- B.Only for database schema diagrams
- C.Standardized software modeling notation✓ Correct
- D.Only for creating flowchart diagrams
Explanation
Standardized modeling.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q17. Document the why not what?
- A.Never write any comments at all
- B.Comment every single line of code
- C.Explain reasoning, not restate code✓ Correct
- D.Only document variable names used
Explanation
Reasoning over restating.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q18. What is knowledge base?
- A.A collection of team passwords stored
- B.A textbook for learning to code
- C.A code repository on version control
- D.Repository of solutions for problems✓ Correct
Explanation
Solution repository.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q19. Version control for docs?
- A.Track changes with revision history✓ Correct
- B.Deleting old versions of documents
- C.Counting the number of documents
- D.Numbering pages in the document
Explanation
Change history.
Report an error in this question
Communication & Documentation of SolutionsMedium
Q20. What is an ADR?
- A.A blueprint for building construction
- B.A server log of all system events
- C.Architectural decision with context noted✓ Correct
- D.A test result from quality checks
Explanation
Decision documentation.
Report an error in this question
Communication & Documentation of SolutionsHard
Q21. What is literate programming?
- A.Adding many comments everywhere found
- B.Writing poetry about the algorithms
- C.Writing literary fiction about code
- D.Code embedded in documentation text✓ Correct
Explanation
Code within documentation.
Report an error in this question
Communication & Documentation of SolutionsHard
Q22. What is docs-as-code?
- A.Using code tools to write docs
- B.Docs with version control and CI/CD✓ Correct
- C.Writing code inside documentation
- D.Replacing code with documentation
Explanation
Software practices for docs.
Report an error in this question
Communication & Documentation of SolutionsHard
Q23. What is C4 model?
- A.A C programming language standard
- B.A security classification framework
- C.Four levels: Context, Container, Component, Code✓ Correct
- D.A testing methodology for the app
Explanation
Four-level architecture docs.
Report an error in this question
Communication & Documentation of SolutionsHard
Q24. Technical writing for diverse audiences?
- A.Write only for experts in the field
- B.Always use maximum jargon in writing
- C.Adapt style and depth for audience✓ Correct
- D.Write the longest documents possible
Explanation
Audience-appropriate writing.
Report an error in this question
Communication & Documentation of SolutionsHard
Q25. What are runbooks?
- A.Step-by-step operational procedure guides✓ Correct
- B.A marathon training plan document
- C.Code execution logs from the system
- D.Competitions between team members
Explanation
Operational procedures.
Report an error in this question
Communication & Documentation of SolutionsHard
Q26. Diagramming in distributed systems?
- A.Designing logos for the application
- B.Diagrams for complex interactions shown✓ Correct
- C.Creating art for the office walls
- D.Drawing pictures for decoration only
Explanation
Visual complexity communication.
Report an error in this question
Communication & Documentation of SolutionsHard
Q27. Retrospective documentation?
- A.Documenting very old legacy systems
- B.Record successes, failures, improvements✓ Correct
- C.Archiving old documents for storage
- D.Deleting outdated documentation files
Explanation
Sprint learnings.
Report an error in this question
Communication & Documentation of SolutionsHard
Q28. What is traceability?
- A.Link requirements to design and tests✓ Correct
- B.Numbering all the pages in documents
- C.Finding lost documentation on the server
- D.Tracking user access to the system
Explanation
Lifecycle linkage.
Report an error in this question
Communication & Documentation of SolutionsHard
Q29. What is communication debt?
- A.Outstanding phone bills to be paid
- B.Cost of poor communication accumulated✓ Correct
- C.Too many meetings in the schedule
- D.Email overload in the team inbox
Explanation
Accumulated poor communication costs.
Report an error in this question
Communication & Documentation of SolutionsHard
Q30. Post-incident review docs?
- A.Legal documents for court proceedings
- B.Documents assigning blame to someone
- C.Deleting all evidence of the incident
- D.Blameless timeline, root cause, actions✓ Correct
Explanation
Learning and prevention.
Report an error in this question