Question 830
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A user complains an allowed video call is blocked after an application-control profile is updated to deny the entire collaboration category. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a user complains an allowed video call is blocked after an application-control profile is updated to deny the entire collaboration category. The relevant technical mechanism is: An overly broad application category action can affect legitimate services sharing taxonomy. The most direct diagnostic or implementation action is: Inspect the exact detected application and scope a permitted exception after business authorization. A useful verification is: The sanctioned call succeeds while explicitly unapproved collaboration apps stay denied. An ongoing safeguard is: Test business-critical applications during signature updates. This is the INTENDED choice for the strongest verification evidence. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
This observation would test a different technical dependency: Transport ports alone do not establish which application is in use. The current issue is governed by: An overly broad application category action can affect legitimate services sharing taxonomy. Its decisive check is “The sanctioned call succeeds while explicitly unapproved collaboration apps stay denied”.
That test belongs to another control with this basis: Creating a filtering profile does not enforce it unless the correct traffic path uses it. In the current case, the governing reason is: An overly broad application category action can affect legitimate services sharing taxonomy. The direct verification is “The sanctioned call succeeds while explicitly unapproved collaboration apps stay denied”.
This observation would test a different technical dependency: Uniform endpoint prerequisites can harm legitimate workflows when business roles differ. The current issue is governed by: An overly broad application category action can affect legitimate services sharing taxonomy. Its decisive check is “The sanctioned call succeeds while explicitly unapproved collaboration apps stay denied”.