A security team is conducting a routine audit of endpoint security compliance. Which TWO artifacts should the auditors inspect to verify that antivirus and endpoint detection and response (EDR) agents are functioning correctly across all workstations? (Choose two)
Local service status confirms the antivirus daemon is actually running, and recent scan logs evidence that detection and remediation executed on that endpoint. This provides per-workstation proof of agent function, complementing the fleet-wide view from the management console.
Why this answer
Option B is correct because checking the endpoint's local service status verifies that the antivirus daemon/service is actually running, and reviewing recent scan logs confirms the agent is performing its scanning function rather than merely being installed. Option D is correct because a centralized EDR management console dashboard aggregates agent health telemetry and signature update status across all workstations, which is the most efficient way to confirm fleet-wide functionality and compliance. Option A is incorrect because spanning-tree root bridge priority is a Layer 2 switching parameter unrelated to endpoint security agents.
Option C is incorrect because DNS root hint tables only affect name resolution and reveal nothing about antivirus or EDR operation. Option E is incorrect because BGP ASN peering configurations concern internet routing between autonomous systems, not endpoint protection status.
Exam trap
The trap is selecting network-centric artifacts (STP, DNS, BGP) that sound technical but are irrelevant to endpoint agent health; candidates must focus on host-level service state and centralized management console reporting.