Why is network reachability part of the architecture decision rather than an implementation detail?
Select an answer to reveal the explanation.
Short Explanation
If an isolated network can't reach the SaaS endpoint, that decides the architecture. You can't treat reachability as a later workaround.
Full Explanation
The correct answer says agents must reach the chosen backend from every monitored environment, and networks that cannot reach a SaaS endpoint constrain the model itself. Air-gapped or restricted environments cannot reach an external endpoint, and that constraint selects the architecture rather than being solved within it. The option saying reachability determines how much telemetry the backend retains is incorrect because retention is a policy and capacity matter unrelated to connectivity. The option saying reachability affects only synthetic monitoring, not agent reporting, is incorrect because every agent depends on reaching the backend, not only synthetic components. The option saying reachability is guaranteed in SaaS deployments and needs no consideration is incorrect because SaaS requires outbound connectivity from each monitored environment, which restricted networks may not permit. For the exam, include reachability among architecture drivers.