The correct options are Leverage appropriate field types such as iteration, single select, and date to model work, Keep the project description, README, and status updates current to share context, Split large issues into smaller issues so work can progress in parallel, Maintain a single source of truth for key information so details do not diverge, and Use @mentions to notify specific teammates or groups in comments and discussions.

Leverage appropriate field types such as iteration, single select, and date to model work because purpose built fields capture schedule, categorization, and timelines in a structured way. This enables reliable filtering, views, automation, and reporting so the project board reflects real planning artifacts rather than unstructured notes.

Keep the project description, README, and status updates current to share context because these surfaces communicate goals, scope, and changes to everyone without requiring meetings. When combined with Maintain a single source of truth for key information so details do not diverge the team avoids duplication and drift as stakeholders can trust one canonical place for objectives, definitions, and links.

Split large issues into smaller issues so work can progress in parallel because breaking down work clarifies ownership and acceptance criteria, reduces coordination overhead, and allows independent pull requests that merge sooner. This leads to faster feedback and more predictable throughput.

Use @mentions to notify specific teammates or groups in comments and discussions because explicit notifications route questions and decisions to the right people, which improves responsiveness and accountability while keeping the conversation discoverable on GitHub.

Prefer ad hoc email threads over issues and pull requests for coordination is incorrect because email fragments context, is not easily searchable, and lacks linked history with code and reviews. GitHub issues, pull requests, and discussions keep decisions transparent and auditable in the same system where the work happens.

Full AWS Practitioner Certification Question