Sample question 1 — Configure processes and communications
A business change group of twelve staff tracks whether the features they requested have shipped, checks the target dates, and wants to comment when a date threatens a regulatory deadline. None of them writes code, administers the organization, or runs builds. The IT director has one budget line for extra seats and would rather not spend it on this group. What should the project administrator do?
- A. Assign Stakeholder access to the twelve staff so they can follow their requests.
- B. Buy Basic access for the group and revoke it once each release closes.
- C. Add the group to the Contributors group and rely on discipline to avoid edits.
- D. Create a read-only copy of the board in a separate project for the group.
Answer: A. Option A is correct because Stakeholder access lets the twelve staff follow the work and add comments at no seat cost, which is exactly the visibility the group needs and the director is willing to fund. Basic access would satisfy them too but would consume the budget line for features they do not use. Contributors membership hands over edit rights that put the board's integrity at risk. A copied board in another project goes stale and cannot carry the comments back.