The correct option is To signal that the work is still in progress and to invite early feedback without initiating a full review.

A draft pull request lets a developer share work in progress so teammates can follow the direction and start a conversation without triggering a formal review. It keeps collaboration open for comments and suggestions while clearly indicating that the changes are not ready for review. The author can later mark it as ready when the feature stabilizes.

Draft pull requests are required for very large repositories and cannot be skipped is incorrect because this status is optional for any repository and there is no requirement based on repository size.

To automatically start continuous integration and deployment workflows as soon as the pull request is opened is incorrect because draft pull requests do not start pull request triggered workflows by default and they typically run when the request is marked ready for review.

To block all collaboration so no one can comment or suggest changes until the code is complete is incorrect because collaborators can still comment and suggest changes on this type of request and the label only prevents the formal review process from starting.

Full AWS Practitioner Certification Question