HomeSubjectsUniversityBlogAbout

Communication & Documentation of Solutions

Topic in Problem Solving & Analytical Skills

210 total MCQsShowing 30 with explanations10 Easy10 Medium10 Hard

About This Topic

Documenting a solution means explaining its design, decisions and usage clearly enough for others to understand, maintain and extend it. Questions ask why documentation matters, what good code comments explain (intent, not the obvious), and how README files, API references, user manuals and inline docstrings differ. Engineering items cover Architecture Decision Records (ADRs) that capture the reasoning behind design choices, UML diagrams, version-controlled docs and keeping documentation accurate as code evolves. Presentation questions touch audience analysis, structuring technical talks with the rule of three, writing concise reports and giving constructive feedback during code reviews.

Below are 30 practice questions from a pool of 210 Communication & Documentation of Solutions MCQs, one of 16 topics in Problem Solving & Analytical Skills. Each shows the correct answer with an explanation; when you are ready, take a timed quiz to test recall under exam conditions.

Practice Questions

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?

  1. A.It is completely unnecessary to do
  2. B.Only managers need to read the docs
  3. C.It wastes time that could be coding
  4. 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?

  1. A.A variable declaration in the code
  2. B.Social feedback on the project
  3. C.An error in the source code
  4. 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?

  1. A.Only the final answer or result
  2. B.Problem, approach, usage, examples✓ Correct
  3. C.Only the raw source code itself
  4. D.Only variable names and types

Explanation

Comprehensive documentation.

Report an error in this question

Communication & Documentation of SolutionsEasy

Q4. What is a README?

  1. A.A personal diary for the developer
  2. B.A system log of all the events
  3. C.A configuration file for the app
  4. D.Introduces project with purpose/setup✓ Correct

Explanation

Project introduction.

Report an error in this question

Communication & Documentation of SolutionsEasy

Q5. Why clear communication?

  1. A.Alignment on problems and solutions✓ Correct
  2. B.It is only needed for presentations
  3. C.It is not important for the team
  4. D.It slows down the project progress

Explanation

Reduces misunderstanding.

Report an error in this question

Communication & Documentation of SolutionsEasy

Q6. Why clear names?

  1. A.To confuse other developers reading
  2. B.They create self-documenting code✓ Correct
  3. C.To make the code look fancy
  4. 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?

  1. A.A tutorial for learning to code
  2. B.End-user software usage instructions✓ Correct
  3. C.Source code documentation for devs
  4. 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?

  1. A.A debug log of runtime errors seen
  2. B.Chronological notable changes per version✓ Correct
  3. C.An error log of system failures
  4. 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?

  1. A.It is a waste of team time
  2. B.No one reads documentation anyway
  3. C.Review thinking, learn, and share✓ Correct
  4. 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?

  1. A.Defect with repro steps and details✓ Correct
  2. B.A proposal for new feature ideas
  3. C.A financial report for the project
  4. 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?

  1. A.A marketing brochure for the app
  2. B.Describes endpoints, params, examples✓ Correct
  3. C.Internal code comments only written
  4. 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?

  1. A.A user guide for end-user features
  2. B.Detailed technical design and architecture✓ Correct
  3. C.A marketing brochure for clients
  4. D.A sales pitch for stakeholders

Explanation

Architecture details.

Report an error in this question

Communication & Documentation of SolutionsMedium

Q13. Inline vs block comments?

  1. A.Block comments are for single lines
  2. B.Inline: single line; block: section✓ Correct
  3. C.Inline comments are always longer
  4. 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?

  1. A.Change proposal with rationale given✓ Correct
  2. B.A financial budget document for project
  3. C.A test plan for quality assurance
  4. 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?

  1. A.Only writing docs for bugs that are found
  2. B.Avoiding all documentation in the project
  3. C.Write docs before code to clarify design✓ Correct
  4. 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?

  1. A.Just drawing pictures for fun only
  2. B.Only for database schema diagrams
  3. C.Standardized software modeling notation✓ Correct
  4. 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?

  1. A.Never write any comments at all
  2. B.Comment every single line of code
  3. C.Explain reasoning, not restate code✓ Correct
  4. 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?

  1. A.A collection of team passwords stored
  2. B.A textbook for learning to code
  3. C.A code repository on version control
  4. 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?

  1. A.Track changes with revision history✓ Correct
  2. B.Deleting old versions of documents
  3. C.Counting the number of documents
  4. D.Numbering pages in the document

Explanation

Change history.

Report an error in this question

Communication & Documentation of SolutionsMedium

Q20. What is an ADR?

  1. A.A blueprint for building construction
  2. B.A server log of all system events
  3. C.Architectural decision with context noted✓ Correct
  4. 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?

  1. A.Adding many comments everywhere found
  2. B.Writing poetry about the algorithms
  3. C.Writing literary fiction about code
  4. 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?

  1. A.Using code tools to write docs
  2. B.Docs with version control and CI/CD✓ Correct
  3. C.Writing code inside documentation
  4. 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?

  1. A.A C programming language standard
  2. B.A security classification framework
  3. C.Four levels: Context, Container, Component, Code✓ Correct
  4. 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?

  1. A.Write only for experts in the field
  2. B.Always use maximum jargon in writing
  3. C.Adapt style and depth for audience✓ Correct
  4. D.Write the longest documents possible

Explanation

Audience-appropriate writing.

Report an error in this question

Communication & Documentation of SolutionsHard

Q25. What are runbooks?

  1. A.Step-by-step operational procedure guides✓ Correct
  2. B.A marathon training plan document
  3. C.Code execution logs from the system
  4. D.Competitions between team members

Explanation

Operational procedures.

Report an error in this question

Communication & Documentation of SolutionsHard

Q26. Diagramming in distributed systems?

  1. A.Designing logos for the application
  2. B.Diagrams for complex interactions shown✓ Correct
  3. C.Creating art for the office walls
  4. D.Drawing pictures for decoration only

Explanation

Visual complexity communication.

Report an error in this question

Communication & Documentation of SolutionsHard

Q27. Retrospective documentation?

  1. A.Documenting very old legacy systems
  2. B.Record successes, failures, improvements✓ Correct
  3. C.Archiving old documents for storage
  4. D.Deleting outdated documentation files

Explanation

Sprint learnings.

Report an error in this question

Communication & Documentation of SolutionsHard

Q28. What is traceability?

  1. A.Link requirements to design and tests✓ Correct
  2. B.Numbering all the pages in documents
  3. C.Finding lost documentation on the server
  4. 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?

  1. A.Outstanding phone bills to be paid
  2. B.Cost of poor communication accumulated✓ Correct
  3. C.Too many meetings in the schedule
  4. 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?

  1. A.Legal documents for court proceedings
  2. B.Documents assigning blame to someone
  3. C.Deleting all evidence of the incident
  4. D.Blameless timeline, root cause, actions✓ Correct

Explanation

Learning and prevention.

Report an error in this question

Ready to test yourself on Communication & Documentation of Solutions?

Take a timed quiz drawn from 210+ questions on this topic. No signup required — your progress saves in your browser.

Start Communication & Documentation of Solutions Quiz