What is true about the assumption documents

Question

Options

• AMust never be included in the solution proposal
• BAssumptions are so essentials that they need to always be included with every solution
• CAssumptions are only needed if the customer asks for it
• DAssumptions vary based on the project

• A
  2% (1)
• B
  5% (2)
• C
  2% (1)
• D
  91% (40)

Explanation

Assumptions in project documentation are inherently project-specific - they depend on the scope, client context, technical environment, and unknowns unique to each engagement, making D the only universally true statement. Option A is wrong because assumptions are often recommended inclusions in solution proposals to set expectations and reduce scope disputes. Option B overcorrects in the other direction; not every solution requires a formal assumptions document, and mandating it universally would be impractical. Option C is wrong because best practice dictates that assumptions should be documented proactively by the solution provider, not only when a customer explicitly requests them.

Memory tip: Think of assumptions like a project's fingerprint - no two are identical. When you see an absolute word like "always" or "never" in an answer choice (A, B, C all use one), treat it as a red flag on a contextual topic like documentation.

No community discussion yet for this question.