What is lost by running synthetic tests only after users report a problem?
Select an answer to reveal the explanation.
Short Explanation
If you only run synthetic tests after users complain, you lose the early warning they're built for. Scheduled runs are monitoring; on-demand runs are just debugging after the fact.
Full Explanation
Running synthetic tests only after users report a problem loses the early detection they exist to provide, since scheduled tests find failures before users do. Scheduled execution turns a test into monitoring, and reactive runs also lose baseline history showing when behaviour changed. Saying nothing is lost because on-demand execution produces the same data is wrong: the result may match, but detection timing and trend history do not. Saying multi-location testing is lost is wrong because location choice is available regardless of when the test runs. Saying multi-step journey testing is lost is wrong because journey tests can be run either way. For the exam, associate scheduled synthetics with proactive detection and baseline history.