Why is a single availability ping an inadequate synthetic strategy for a transactional application?
Select an answer to reveal the explanation.
Short Explanation
A site can answer on port 443 while checkout is completely broken. A ping is happy either way. You need a test that walks the login, search, and checkout journey.
Full Explanation
Endpoint availability is a weak proxy for functional health.
A ping confirms something is responding, but it does not confirm that the multi-step journey users depend on—login, search, checkout—still completes successfully. The failures users care about are usually inside the journey, well past the point a ping stops.
The claim that ping checks are not supported by Instana Synthetic Monitoring is incorrect because simple checks are supported and are appropriate for basic availability. The claim that ping checks consume more resources than full journey tests is incorrect because a ping is cheaper, not more expensive. The claim that ping checks can only run from one location is incorrect because location selection applies to test types generally.
For the exam, match test depth to what actually needs validating.