Question 480
A Fortinet team is working on this situation: a project assumes private proxy is automatically available in every newly created FortiSASE instance. It attempted: Request the select-availability private-proxy feature through FortiCare when applicable. Expected evidence (Verify the private proxy option becomes available for the licensed tenant) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
Explanation
Correct Answer
Address the unsupported feature flag rather than guessing an undocumented API toggle. The missing evidence (verify the private proxy option becomes available for the licensed tenant) points to a problem with the implementation of request the select-availability private-proxy feature through FortiCare when applicable. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
Repair edge-to-PoP transport before distributing unsupported client software addresses a different operational issue: an enterprise has many public web appliances at branch sites but no user-installed agent. This situation calls for address the unsupported feature flag rather than guessing an undocumented API toggle because the missing result relates to verify the private proxy option becomes available for the licensed tenant.
Fix traffic classification and route reachability rather than forcing all destinations into one internet policy addresses a different operational issue: a branch wants direct internet breakout but employees also need private applications. This situation calls for address the unsupported feature flag rather than guessing an undocumented API toggle because the missing result relates to verify the private proxy option becomes available for the licensed tenant.
Repair the AP cloud-security assignment instead of changing an unrelated WAN BGP community addresses a different operational issue: a shop needs FortiAP-connected wireless clients to receive cloud security. This situation calls for address the unsupported feature flag rather than guessing an undocumented API toggle because the missing result relates to verify the private proxy option becomes available for the licensed tenant.



Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests