Question 150An organization forwards full debug traffic from every edge device to the SIEM and overwhelms ingestion capacity with duplicate low-value records. Which cause-and-effect relationship determines the best answer? IKE success alone does not prove child-SA selectors cover the required inner traffic. Flow records identify endpoints, ports and volumes while interface totals cannot show individual conversations. Time-consistent telemetry is necessary to reconstruct sequences across independent security systems. Telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. ExplanationCorrect Answer D:Telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. The practical corrective action is: Apply source filtering, field normalization and risk-based retention while preserving required high-signal detections. Confirm it by: Confirm critical test detections still arrive while redundant event volume and ingest costs fall. Other Answers A:IKE success alone does not prove child-SA selectors cover the required inner traffic. By contrast, telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. B:Flow records identify endpoints, ports and volumes while interface totals cannot show individual conversations. In the stated system, telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. C:Time-consistent telemetry is necessary to reconstruct sequences across independent security systems. By contrast, telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume.
Question 151An organization forwards full debug traffic from every edge device to the SIEM and overwhelms ingestion capacity with duplicate low-value records. Which observable result shows the correction is effective? Confirm critical test detections still arrive while redundant event volume and ingest costs fall. Find a seeded large outbound session with correct source, destination, time and transfer volume in the collector. Trace a staged login and firewall denial and verify the ordered events share a reliable time basis. Check child-SA selectors and packet counters while generating traffic from the authorized test subnet. ExplanationCorrect Answer A:Confirm critical test detections still arrive while redundant event volume and ingest costs fall. The evidence confirms the intended action: Apply source filtering, field normalization and risk-based retention while preserving required high-signal detections. It matters because telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. Other Answers B:Flow records identify endpoints, ports and volumes while interface totals cannot show individual conversations. The relevant acceptance check is to confirm critical test detections still arrive while redundant event volume and ingest costs fall. C:Time-consistent telemetry is necessary to reconstruct sequences across independent security systems. A more meaningful verification is to confirm critical test detections still arrive while redundant event volume and ingest costs fall. D:IKE success alone does not prove child-SA selectors cover the required inner traffic. Proving this correction calls for a check to confirm critical test detections still arrive while redundant event volume and ingest costs fall.
Question 152An organization forwards full debug traffic from every edge device to the SIEM and overwhelms ingestion capacity with duplicate low-value records. What should be institutionalized before future deployments? Run bidirectional selector and route tests before declaring each new VPN production-ready. Enforce authenticated time synchronization and collector parsing rules for all log sources. Define per-source ingestion budgets, sampling limits and loss alerts tied to incident requirements. Monitor flow-exporter health and verify clock synchronization between network devices and the collector. ExplanationCorrect Answer C:Define per-source ingestion budgets, sampling limits and loss alerts tied to incident requirements. This safeguard limits repeat failures because telemetry quality depends on relevance and consistent parsing, not maximizing raw message volume. The direct correction remains: Apply source filtering, field normalization and risk-based retention while preserving required high-signal detections. Other Answers A:IKE success alone does not prove child-SA selectors cover the required inner traffic. The stronger recurring control is to define per-source ingestion budgets, sampling limits and loss alerts tied to incident requirements. B:Time-consistent telemetry is necessary to reconstruct sequences across independent security systems. Reducing this risk requires a practice to define per-source ingestion budgets, sampling limits and loss alerts tied to incident requirements. D:Flow records identify endpoints, ports and volumes while interface totals cannot show individual conversations. A more direct preventive measure is to define per-source ingestion budgets, sampling limits and loss alerts tied to incident requirements.
Question 153A switch learns forged ARP responses claiming to be the default gateway after a rogue endpoint joins an access port. What should the engineer change first to meet these conditions? Enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. Protect edge access ports with BPDU Guard and apply root-bridge controls to intended infrastructure links. Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. Associate an appropriate intrusion policy and file inspection actions with the matched access rule. ExplanationCorrect Answer A:Enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. This action specifically works because dAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. Verify with: Inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. Other Answers B:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. This failure calls for a decision to enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. C:DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. This failure calls for a decision to enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. D:Traffic allowed by an access control rule is not automatically deeply inspected without relevant inspection configuration. A more relevant action is to enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs.
Question 154A switch learns forged ARP responses claiming to be the default gateway after a rogue endpoint joins an access port. Which cause-and-effect relationship determines the best answer? DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. Traffic allowed by an access control rule is not automatically deeply inspected without relevant inspection configuration. BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. ExplanationCorrect Answer A:DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. The practical corrective action is: Enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. Confirm it by: Inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. Other Answers B:DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. By contrast, DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. C:Traffic allowed by an access control rule is not automatically deeply inspected without relevant inspection configuration. In the stated system, DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. D:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. By contrast, DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims.
Question 155A switch learns forged ARP responses claiming to be the default gateway after a rogue endpoint joins an access port. Which observable result shows the correction is effective? Inject a controlled BPDU on a PortFast edge port and check the expected protected state and alert. Connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. Replay a safe IPS test pattern and review policy hit, intrusion event and enforcement action. Inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. ExplanationCorrect Answer D:Inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. The evidence confirms the intended action: Enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. It matters because dAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. Other Answers A:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. The relevant acceptance check is to inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. B:DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. The relevant acceptance check is to inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. C:Traffic allowed by an access control rule is not automatically deeply inspected without relevant inspection configuration. Proving this correction calls for a check to inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate.
Question 156A switch learns forged ARP responses claiming to be the default gateway after a rogue endpoint joins an access port. What should be institutionalized before future deployments? Require rule-review evidence that permitted high-risk flows carry intended threat inspection. Apply access-port templates and review exceptions before connecting third-party switches. Maintain trusted uplink design and DHCP binding persistence across switch reloads. Audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses. ExplanationCorrect Answer C:Maintain trusted uplink design and DHCP binding persistence across switch reloads. This safeguard limits repeat failures because dAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. The direct correction remains: Enable Dynamic ARP Inspection backed by trusted DHCP snooping bindings on appropriate VLANs. Other Answers A:Traffic allowed by an access control rule is not automatically deeply inspected without relevant inspection configuration. Reducing this risk requires a practice to maintain trusted uplink design and DHCP binding persistence across switch reloads. B:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. The lasting safeguard is to maintain trusted uplink design and DHCP binding persistence across switch reloads. D:DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. The lasting safeguard is to maintain trusted uplink design and DHCP binding persistence across switch reloads.
Question 157An unauthorized DHCP server connected at a conference room port hands users an attacker-controlled DNS and default router. What should the engineer change first to meet these conditions? Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. Protect edge access ports with BPDU Guard and apply root-bridge controls to intended infrastructure links. Enable Dynamic ARP Inspection alone without treating the conference-room port as an untrusted source of DHCP server replies. Scope FTD access control by application identity, relevant endpoints and business authorization. ExplanationCorrect Answer A:Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. This action specifically works because dHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. Verify with: Connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. Other Answers B:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. This failure calls for a decision to use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. C:Enable Dynamic ARP Inspection alone without treating the conference-room port as an untrusted source of DHCP server replies. ARP validation addresses forged address mappings, not the rogue DHCP OFFER messages that the specific case reports. The case-specific answer is: Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. D:Application visibility and control can distinguish sanctioned services that share common transport ports. This failure calls for a decision to use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted.
Question 158An unauthorized DHCP server connected at a conference room port hands users an attacker-controlled DNS and default router. Which cause-and-effect relationship determines the best answer? Application visibility and control can distinguish sanctioned services that share common transport ports. DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. ExplanationCorrect Answer C:DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. The practical corrective action is: Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. Confirm it by: Connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. Other Answers A:Application visibility and control can distinguish sanctioned services that share common transport ports. In the stated system, DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. B:DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. By contrast, DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. D:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. In the stated system, DHCP snooping drops server responses received from untrusted ports before clients accept rogue leases.
Question 159An unauthorized DHCP server connected at a conference room port hands users an attacker-controlled DNS and default router. Which observable result shows the correction is effective? Test approved app traffic and a different HTTPS application from the same source against the rule. Connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. Inject a forged ARP reply and confirm the untrusted access port drops it while legitimate learned clients communicate. Inject a controlled BPDU on a PortFast edge port and check the expected protected state and alert. ExplanationCorrect Answer B:Connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. The evidence confirms the intended action: Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. It matters because dHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. Other Answers A:Application visibility and control can distinguish sanctioned services that share common transport ports. Proving this correction calls for a check to connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. C:DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. The failure is checked more directly by a test to connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed. D:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. Proving this correction calls for a check to connect a test rogue server to a guest port and confirm its offers are rejected while authorized offers succeed.
Question 160An unauthorized DHCP server connected at a conference room port hands users an attacker-controlled DNS and default router. What should be institutionalized before future deployments? Audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses. Maintain trusted uplink design and DHCP binding persistence across switch reloads. Apply access-port templates and review exceptions before connecting third-party switches. Review application discovery logs before expanding access rules. ExplanationCorrect Answer A:Audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses. This safeguard limits repeat failures because dHCP snooping drops server responses received from untrusted ports before clients accept rogue leases. The direct correction remains: Use DHCP snooping with the uplink marked trusted and guest-facing switch ports untrusted. Other Answers B:DAI validates ARP mappings against authorized IP-to-MAC bindings rather than accepting arbitrary ARP claims. The stronger recurring control is to audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses. C:BPDU Guard can disable an access port receiving unexpected BPDUs, limiting unauthorized switching topology changes. Reducing this risk requires a practice to audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses. D:Application visibility and control can distinguish sanctioned services that share common transport ports. Reducing this risk requires a practice to audit trunk and uplink trust flags so no ordinary edge port can serve DHCP responses.