Question 750
Which threat to reliable or secure operations is most specific to this situation: The service provides SaaS access from two POPs but one region's sessions fail because a backend application allowlist contains only the other POP's egress?
Explanation
Correct Answer
The named risk is directly connected to the design rule: Cloud egress ranges and partner allowlisting must account for approved POP behavior. The targeted preventive step is: Update the sanctioned application allowlist or stable egress design for intended POPs. Expected evidence: Authorized sessions succeed from each permitted region without opening unrestricted access.
Incorrect Answers
This alternative addresses the separate case “FortiSASE logs show blocked uploads but the administrator cannot tell whether web filtering or data loss prevention caused the result”. This hazard is more relevant than general operational concerns because security services have distinct decision records and enforcement criteria. The deciding requirement here is “A single-POP allowlist can make regional failover appear as authentication failure”.
The option would apply to “The engineering team is reviewing A cloud access policy rejects an authorized user because an old endpoint posture tag remains in a rule after a compliance migration”. A shortcut would leave the case-specific dependency unresolved: Effective SPA permissions can fail due to stale posture conditions even when identity is correct. This question instead requires “A single-POP allowlist can make regional failover appear as authentication failure”.
The related but distinct situation is “A FortiSASE administrator enables DNS filtering but an endpoint's applications keep resolving through an uninspected custom resolver”. The operational danger arises from this condition: DNS security controls only apply to queries that traverse the intended enforcement path. For the stated problem, “A single-POP allowlist can make regional failover appear as authentication failure” addresses the central condition.