A build pipeline intermittently fails because a test that measures an API endpoint’s response time is unstable. You need to prevent the pipeline from failing due to that test. Which two actions should you take?

To prevent the pipeline from failing due to an unstable test, you should first manually mark the test as flaky. This identifies the test as unreliable without immediately failing the build. Then, clear the "Flaky tests included in test pass percentage" option. This ensures that even if a flaky test fails, it won't negatively impact the overall test pass percentage, allowing the pipeline to succeed. Setting "Flaky test detection to Off" would prevent the system from identifying other flaky tests, which is not ideal for long-term stability. Enabling Test Impact Analysis (TIA) helps run only relevant tests but doesn't address the flakiness of a specific test. Enabling test slicing distributes tests across agents but doesn't resolve the underlying instability of the test itself.