Question 720
At Willow Mobility, an infrastructure review by the fleet security engineers is evaluating parts and diagnostics services across a vehicle service branch platform before an expanded branch rollout (FT-D-05-01). The review finds that external consultants lack managed endpoints yet require controlled access to a narrow set of web destinations. Any correction must respect this operating requirement: vehicle telemetry is available only to approved maintenance roles. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that external consultants lack managed endpoints yet require controlled access to a narrow set of web destinations. Select an approved FortiSASE agentless internet access deployment with scoped policies as part of Willow Mobility's parts and diagnostics services update (FT-D-05-01), while enforcing the constraint that vehicle telemetry is available only to approved maintenance roles. A successful implementation must be checked rather than assumed: In a controlled a vehicle service branch platform acceptance test, A test unmanaged browser reaches approved sites while blocked categories remain denied; the outcome is recorded under Willow Mobility's rollout (FT-D-05-01). The technical reason is that Agentless access offers a different traffic-onboarding model from an installed agent.
Incorrect Answers
The source case reports that external consultants lack managed endpoints yet require controlled access to a narrow set of web destinations. This option would change the control governed by: Federated authentication establishes identity but administrative roles still control permissions. That does not resolve the present failure, where select an approved FortiSASE agentless internet access deployment with scoped policies as part of Willow Mobility's parts and diagnostics services update (FT-D-05-01), while enforcing the constraint that vehicle telemetry is available only to approved maintenance roles. The applicable response is “Select an approved FortiSASE agentless internet access deployment with scoped policies; stage the change with an explicit backout plan”.
The source case reports that external consultants lack managed endpoints yet require controlled access to a narrow set of web destinations. “Bind authentication to the approved identity source and enforce appropriate group mapping; test both primary and backup paths” addresses the technical dependency: Identity-source selection and authorization group mapping must remain explicit. The reported problem instead follows: Select an approved FortiSASE agentless internet access deployment with scoped policies as part of Willow Mobility's parts and diagnostics services update (FT-D-05-01), while enforcing the constraint that vehicle telemetry is available only to approved maintenance roles. The more direct correction is “Select an approved FortiSASE agentless internet access deployment with scoped policies; stage the change with an explicit backout plan”.
The source case reports that external consultants lack managed endpoints yet require controlled access to a narrow set of web destinations. This option would change the control governed by: Cloud access continuity requires awareness of service-point health and placement. That does not resolve the present failure, where select an approved FortiSASE agentless internet access deployment with scoped policies as part of Willow Mobility's parts and diagnostics services update (FT-D-05-01), while enforcing the constraint that vehicle telemetry is available only to approved maintenance roles. The applicable response is “Select an approved FortiSASE agentless internet access deployment with scoped policies; stage the change with an explicit backout plan”.