Question 760
A network architect investigates this Fortinet environment: A team distributes a FortiClient installer while the service's approved endpoint version differs across Windows and macOS. What underlying distinction most directly explains the symptoms?
Explanation
Correct Answer
The condition is explained by the following rule: Endpoint installers and supported capabilities can vary by operating-system family. Address it with this step: Select supported FortiClient packages and test the intended endpoint profile by platform. Check that: Both supported operating systems enroll and apply appropriate steering and security settings.
Incorrect Answers
The related but distinct situation is “A remote-user client package is downloaded from an old portal link with settings for a different FortiSASE tenant”. The situation is governed by this dependency: Client provisioning packages carry tenant-specific settings and must match the intended organization. For the stated problem, “Endpoint installers and supported capabilities can vary by operating-system family” addresses the central condition.
This option serves the scenario “An organization configures SAML administrator login but assumes the same configuration authenticates every ordinary remote-user endpoint”. This case illustrates that FortiSASE administrator SSO and user authentication sources can require distinct mappings. The present scenario is distinguished by “Endpoint installers and supported capabilities can vary by operating-system family”.
This alternative addresses the separate case “Users receive a proxy auto-config file but browser traffic bypasses FortiSASE because the PAC file is never applied”. This case illustrates that a PAC file must be deployed and selected by the browsing environment to affect proxy decisions. The deciding requirement here is “Endpoint installers and supported capabilities can vary by operating-system family”.