Question 1030
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A compliance dashboard shows a noncompliant laptop but an analyst treats it as proof of malware infection. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a compliance dashboard shows a noncompliant laptop but an analyst treats it as proof of malware infection. The relevant technical mechanism is: Device configuration noncompliance and actual threat detection are distinct evidence classes. The most direct diagnostic or implementation action is: Inspect posture failure reasons separately from antivirus, IPS and DLP security detections. A useful verification is: The case identifies the missing compliance control without claiming unobserved malware. An ongoing safeguard is: Keep posture and compromise indicators separate in reporting. 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
That test belongs to another control with this basis: Application activity controls and malware scanning generate different security signals. In the current case, the governing reason is: Device configuration noncompliance and actual threat detection are distinct evidence classes. The direct verification is “The case identifies the missing compliance control without claiming unobserved malware”.
This observation would test a different technical dependency: Transported log events can be misinterpreted through parser or time conversion errors. The current issue is governed by: Device configuration noncompliance and actual threat detection are distinct evidence classes. Its decisive check is “The case identifies the missing compliance control without claiming unobserved malware”.
That test belongs to another control with this basis: Different log types represent different stages and cannot be summed as identical incidents. In the current case, the governing reason is: Device configuration noncompliance and actual threat detection are distinct evidence classes. The direct verification is “The case identifies the missing compliance control without claiming unobserved malware”.