Question 730
To spot receive-buffer pressure that is limiting application throughput, which tool, policy, or technique is appropriate?
- SYN retransmission analysis
- DNS query-response correlation
- TCP window analysis
- TCP three-way handshake
- ARP traffic inspection
Explanation
Correct Answer
C:Advertised receive windows govern how much unacknowledged data a sender may transmit; the requested outcome is precisely to spot receive-buffer pressure that is limiting application throughput.
Incorrect Answers
A:Repeated initial SYNs without replies suggest path loss, filtering or unavailable service; that is useful when the task is to identify a client repeatedly trying to reach an unresponsive server port, not the stated requirement to spot receive-buffer pressure that is limiting application throughput.
B:Transaction IDs, questions and source addresses help relate responses to resolver requests; a team would select it to find clients receiving unexpected answers for a sensitive hostname, which does not provide the particular result to spot receive-buffer pressure that is limiting application throughput.
D:SYN, SYN-ACK and ACK exchange establishes connection state before ordinary application data; applying it would serve distinguish a new established TCP session from an unanswered connection request without directly satisfying the goal to spot receive-buffer pressure that is limiting application throughput.
E:Conflicting address announcements reveal potential local impersonation or legitimate failover needing confirmation; it addresses the different need to detect two MAC addresses repeatedly claiming the same default gateway IP, leaving the requested ability to spot receive-buffer pressure that is limiting application throughput unresolved.
Question 731
To investigate congestion or packet loss affecting a file transfer, what safeguard would be most applicable?
- DNS query-response correlation
- SYN retransmission analysis
- TLS certificate handshake
- TCP retransmission rate
Explanation
Correct Answer
D:Retransmissions indicate missing acknowledgments or loss and need context from round-trip timing; this choice fits the scenario because the team must investigate congestion or packet loss affecting a file transfer.
Incorrect Answers
A:Transaction IDs, questions and source addresses help relate responses to resolver requests; it could help someone trying to find clients receiving unexpected answers for a sensitive hostname, but the problem is instead to investigate congestion or packet loss affecting a file transfer.
B:Repeated initial SYNs without replies suggest path loss, filtering or unavailable service; that is useful when the task is to identify a client repeatedly trying to reach an unresponsive server port, not the stated requirement to investigate congestion or packet loss affecting a file transfer.
C:Certificate validation and handshake failures distinguish trust errors from ordinary IP packet loss; a team would select it to check whether a service presented the expected identity during connection setup, which does not provide the particular result to investigate congestion or packet loss affecting a file transfer.
Question 732
To find clients receiving unexpected answers for a sensitive hostname, what is the relevant defensive action?
- TCP three-way handshake
- DNS query-response correlation
- TLS certificate handshake
- DHCP DORA sequence
Explanation
Correct Answer
B:Transaction IDs, questions and source addresses help relate responses to resolver requests; this mechanism directly supports the requirement to find clients receiving unexpected answers for a sensitive hostname.
Incorrect Answers
A:SYN, SYN-ACK and ACK exchange establishes connection state before ordinary application data; although relevant to distinguish a new established TCP session from an unanswered connection request, it does not by itself achieve the required task to find clients receiving unexpected answers for a sensitive hostname.
C:Certificate validation and handshake failures distinguish trust errors from ordinary IP packet loss; that is useful when the task is to check whether a service presented the expected identity during connection setup, not the stated requirement to find clients receiving unexpected answers for a sensitive hostname.
D:Discover, Offer, Request and Acknowledge messages identify where normal lease negotiation stops; a team would select it to troubleshoot why new endpoints do not obtain valid addresses, which does not provide the particular result to find clients receiving unexpected answers for a sensitive hostname.
Question 733
To detect two MAC addresses repeatedly claiming the same default gateway IP, which option most directly provides the capability?
- DNS query-response correlation
- DHCP DORA sequence
- ARP traffic inspection
- ICMP unreachable analysis
Explanation
Correct Answer
C:Conflicting address announcements reveal potential local impersonation or legitimate failover needing confirmation; it supplies the specific control needed to detect two MAC addresses repeatedly claiming the same default gateway IP.
Incorrect Answers
A:Transaction IDs, questions and source addresses help relate responses to resolver requests; the outcome it supports is to find clients receiving unexpected answers for a sensitive hostname, whereas this scenario asks defenders to detect two MAC addresses repeatedly claiming the same default gateway IP.
B:Discover, Offer, Request and Acknowledge messages identify where normal lease negotiation stops; although relevant to troubleshoot why new endpoints do not obtain valid addresses, it does not by itself achieve the required task to detect two MAC addresses repeatedly claiming the same default gateway IP.
D:ICMP error types and codes describe reachability failures under specific routing conditions; that is useful when the task is to identify a network device explicitly reporting a blocked or unavailable destination, not the stated requirement to detect two MAC addresses repeatedly claiming the same default gateway IP.
Question 734
To troubleshoot why new endpoints do not obtain valid addresses, which control achieves the target outcome?
- TCP reset examination
- ARP traffic inspection
- ICMP unreachable analysis
- DHCP DORA sequence
Explanation
Correct Answer
D:Discover, Offer, Request and Acknowledge messages identify where normal lease negotiation stops; that is why it addresses the operational task to troubleshoot why new endpoints do not obtain valid addresses.
Incorrect Answers
A:RST frames indicate a participant or intervening device reset the session state; its mechanism supports distinguish an actively rejected connection from silent packet dropping, while the requested control must be able to troubleshoot why new endpoints do not obtain valid addresses.
B:Conflicting address announcements reveal potential local impersonation or legitimate failover needing confirmation; the outcome it supports is to detect two MAC addresses repeatedly claiming the same default gateway IP, whereas this scenario asks defenders to troubleshoot why new endpoints do not obtain valid addresses.
C:ICMP error types and codes describe reachability failures under specific routing conditions; although relevant to identify a network device explicitly reporting a blocked or unavailable destination, it does not by itself achieve the required task to troubleshoot why new endpoints do not obtain valid addresses.
Question 735
To identify a network device explicitly reporting a blocked or unavailable destination and to check whether a service presented the expected identity during connection setup, which TWO measures should the defender select? Choose TWO.
- ICMP unreachable analysis
- TCP window analysis
- TLS certificate handshake
- HTTP status-code comparison
- DNS query-response correlation
Explanation
Correct Answers
A:ICMP error types and codes describe reachability failures under specific routing conditions; this is the measure that can identify a network device explicitly reporting a blocked or unavailable destination as one of the separately stated outcomes.
C:Certificate validation and handshake failures distinguish trust errors from ordinary IP packet loss; this is the measure that can check whether a service presented the expected identity during connection setup as one of the separately stated outcomes.
Incorrect Answers
B:Advertised receive windows govern how much unacknowledged data a sender may transmit; its mechanism supports spot receive-buffer pressure that is limiting application throughput, while the requested control must be able to identify a network device explicitly reporting a blocked or unavailable destination and to check whether a service presented the expected identity during connection setup.
D:401/403 and 5xx outcomes have different authorization and processing implications, subject to application behavior; although relevant to separate authentication failures from application-server errors during API troubleshooting, it does not by itself achieve the required task to identify a network device explicitly reporting a blocked or unavailable destination and to check whether a service presented the expected identity during connection setup.
E:Transaction IDs, questions and source addresses help relate responses to resolver requests; it could help someone trying to find clients receiving unexpected answers for a sensitive hostname, but the problem is instead to identify a network device explicitly reporting a blocked or unavailable destination and to check whether a service presented the expected identity during connection setup.
Question 736
To check whether a service presented the expected identity during connection setup, which of the available controls is suitable?
- TCP retransmission rate
- TLS certificate handshake
- ICMP unreachable analysis
- HTTP status-code comparison
Explanation
Correct Answer
B:Certificate validation and handshake failures distinguish trust errors from ordinary IP packet loss; the requested outcome is precisely to check whether a service presented the expected identity during connection setup.
Incorrect Answers
A:Retransmissions indicate missing acknowledgments or loss and need context from round-trip timing; it addresses the different need to investigate congestion or packet loss affecting a file transfer, leaving the requested ability to check whether a service presented the expected identity during connection setup unresolved.
C:ICMP error types and codes describe reachability failures under specific routing conditions; its mechanism supports identify a network device explicitly reporting a blocked or unavailable destination, while the requested control must be able to check whether a service presented the expected identity during connection setup.
D:401/403 and 5xx outcomes have different authorization and processing implications, subject to application behavior; the outcome it supports is to separate authentication failures from application-server errors during API troubleshooting, whereas this scenario asks defenders to check whether a service presented the expected identity during connection setup.
Question 737
To separate authentication failures from application-server errors during API troubleshooting, which of the available controls is suitable?
- HTTP status-code comparison
- ICMP unreachable analysis
- TLS certificate handshake
- DHCP DORA sequence
Explanation
Correct Answer
A:401/403 and 5xx outcomes have different authorization and processing implications, subject to application behavior; this choice fits the scenario because the team must separate authentication failures from application-server errors during API troubleshooting.
Incorrect Answers
B:ICMP error types and codes describe reachability failures under specific routing conditions; it addresses the different need to identify a network device explicitly reporting a blocked or unavailable destination, leaving the requested ability to separate authentication failures from application-server errors during API troubleshooting unresolved.
C:Certificate validation and handshake failures distinguish trust errors from ordinary IP packet loss; the technique works for situations involving check whether a service presented the expected identity during connection setup, rather than this need to separate authentication failures from application-server errors during API troubleshooting.
D:Discover, Offer, Request and Acknowledge messages identify where normal lease negotiation stops; its mechanism supports troubleshoot why new endpoints do not obtain valid addresses, while the requested control must be able to separate authentication failures from application-server errors during API troubleshooting.
Question 738
To notice a branch link consuming far more outbound traffic than usual, which option is the direct technical match?
- Periodic beacon detection
- Connection-count baseline
- Bandwidth baseline
- East-west scanning detection
Explanation
Correct Answer
C:Historical utilization by time and application supports anomaly thresholds that account for routine peaks; this mechanism directly supports the requirement to notice a branch link consuming far more outbound traffic than usual.
Incorrect Answers
A:Temporal analysis detects potential command-and-control polling without relying on known payload signatures; its operational purpose is to find repeat short connections to one external host at regular intervals, not to achieve the specific requirement to notice a branch link consuming far more outbound traffic than usual.
B:Per-host flow frequency comparisons reveal scanning or command activity beyond known user behavior; applying it would serve detect a workstation opening hundreds of unusual outbound sessions without directly satisfying the goal to notice a branch link consuming far more outbound traffic than usual.
D:Breadth and timing of failed connections can distinguish reconnaissance from normal business applications; the technique works for situations involving find sequential connection attempts across many internal ports and hosts, rather than this need to notice a branch link consuming far more outbound traffic than usual.
Question 739
To detect a workstation opening hundreds of unusual outbound sessions, which approach should a network traffic analyst choose?
- DNS entropy analysis
- Periodic beacon detection
- Bandwidth baseline
- Connection-count baseline
Explanation
Correct Answer
D:Per-host flow frequency comparisons reveal scanning or command activity beyond known user behavior; it supplies the specific control needed to detect a workstation opening hundreds of unusual outbound sessions.
Incorrect Answers
A:High-entropy names can indicate tunneling but require false-positive checks for legitimate telemetry; a team would select it to flag unusually long and random-looking subdomain queries to one domain, which does not provide the particular result to detect a workstation opening hundreds of unusual outbound sessions.
B:Temporal analysis detects potential command-and-control polling without relying on known payload signatures; its operational purpose is to find repeat short connections to one external host at regular intervals, not to achieve the specific requirement to detect a workstation opening hundreds of unusual outbound sessions.
C:Historical utilization by time and application supports anomaly thresholds that account for routine peaks; applying it would serve notice a branch link consuming far more outbound traffic than usual without directly satisfying the goal to detect a workstation opening hundreds of unusual outbound sessions.
Question 740
To flag unusually long and random-looking subdomain queries to one domain, which method is designed for the task?
- Connection-count baseline
- DNS entropy analysis
- Lateral SMB activity
- Bandwidth baseline
- East-west scanning detection
Explanation
Correct Answer
B:High-entropy names can indicate tunneling but require false-positive checks for legitimate telemetry; that is why it addresses the operational task to flag unusually long and random-looking subdomain queries to one domain.
Incorrect Answers
A:Per-host flow frequency comparisons reveal scanning or command activity beyond known user behavior; that is useful when the task is to detect a workstation opening hundreds of unusual outbound sessions, not the stated requirement to flag unusually long and random-looking subdomain queries to one domain.
C:SMB flow patterns can expose movement attempts when combined with identity and host events; its operational purpose is to investigate a user workstation suddenly connecting to many peers on SMB ports, not to achieve the specific requirement to flag unusually long and random-looking subdomain queries to one domain.
D:Historical utilization by time and application supports anomaly thresholds that account for routine peaks; applying it would serve notice a branch link consuming far more outbound traffic than usual without directly satisfying the goal to flag unusually long and random-looking subdomain queries to one domain.
E:Breadth and timing of failed connections can distinguish reconnaissance from normal business applications; it addresses the different need to find sequential connection attempts across many internal ports and hosts, leaving the requested ability to flag unusually long and random-looking subdomain queries to one domain unresolved.