The correct option is Use check_run with types created and completed. This configuration listens when a GitHub App creates a new check run and when that run completes, which satisfies the requirement to react on both creation and completion.

The check_run event is emitted for individual check runs and includes actions for when a run is created and when it is completed. Using a types filter limited to created and completed makes the workflow precise so it triggers only at the start and the end of each run reported by the third party app.

Use check_suite with types requested and completed is not appropriate because check_suite relates to the overall suite of checks and not each run. It fires when a suite is requested or when the suite completes, which does not reliably capture each individual run creation event.

Google Cloud Build does not define a GitHub Actions trigger. It is a separate service and does not satisfy the requirement to configure a workflow event inside GitHub.

Use check_run with type started only is incorrect because started is not a valid check_run type and it would not capture completion. Valid check_run types include created, rerequested, completed, and requested_action.

Full AWS Practitioner Certification Question