The correct options are Exclude flaky tests from the test pass calculation and Manually mark the test as flaky in the build settings.

Exclude flaky tests from the test pass calculation is correct because it prevents an intermittently failing test from affecting the overall pass rate that gates the build. Excluding the test lets the pipeline ignore occasional timeouts for that test when computing pass thresholds while still treating other tests as normal.

Manually mark the test as flaky in the build settings is correct because explicitly flagging the test as flaky gives you a targeted way to handle that specific test. Marking it lets the CI system treat its results differently and avoids broad changes that could hide real regressions.

Disable flaky test detection is incorrect because turning off detection removes the mechanism that identifies and handles flakiness. That approach would not keep intermittent failures from breaking the build and would make it harder to manage flaky tests over time.

Enable retry of failed tests for the job is incorrect because retries can mask intermittent issues and make it harder to notice real failures. Retries may reduce noise but they do not explicitly exclude the test from pass calculations or provide a clear signal that the test is flaky.

Enable Test Impact Analysis is incorrect because Test Impact Analysis selects which tests to run based on code changes and does not address intermittent test flakiness or pass rate calculations. It will not prevent a flaky test from affecting build pass criteria.

Full AWS Practitioner Certification Question