The project scope establishes client expectations of which tasks are included and which are not.

• A. It outlines risk management strategies.
• B. It defines the project budget only.
• C. It lists all potential vendors.
• D. It establishes client expectations of which tasks are—and are not—included in the project.

Answer: (D)

Defining what work is included and what is excluded is what project scope is all about. It sets the boundaries for the project, so everyone—from the client to the team—knows which tasks will be delivered and which ones won’t be part of the project. This clarity helps prevent misunderstandings and scope creep, because any requested additions can be evaluated against what’s in scope and handled through a formal change process. The statement that best captures this is the one that says it establishes client expectations of which tasks are—and are not—included in the project.

Other areas focus on different aspects: risk management strategies address potential problems and how to respond to them; the budget outlines cost constraints; listing all potential vendors concerns procurement and sourcing. These are important, but they’re separate from defining what work is in or out of the project scope.