ECCouncil 312-38 (Certified Network Defender) Practice Test 77

Question 760

To separate physical link faults from malicious packet drops, which option is the direct technical match?

  1. Throughput-versus-bandwidth distinction
  2. Jitter measurement
  3. QoS queue monitoring
  4. Round-trip latency monitoring
  5. Interface error counters
  6. Packet-loss measurement

Explanation

Correct Answer

E:

CRC errors and discards provide clues to media or congestion issues outside IP application logs; the requested outcome is precisely to separate physical link faults from malicious packet drops.

Incorrect Answers

A:

Protocol overhead, congestion and endpoints reduce achieved throughput beneath nominal link capacity; that is useful when the task is to avoid assuming a gigabit link always delivers one gigabit of application data, not the stated requirement to separate physical link faults from malicious packet drops.

B:

Variation in packet delay affects real-time playback buffers and interactive communication; a team would select it to explain inconsistent voice-call quality even when average latency looks acceptable, which does not provide the particular result to separate physical link faults from malicious packet drops.

C:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; its operational purpose is to detect priority voice traffic starved by a misconfigured egress scheduler, not to achieve the specific requirement to separate physical link faults from malicious packet drops.

D:

RTT trends reveal timing degradation but cannot alone locate which hop or endpoint caused it; applying it would serve identify a remote network path with rising delay during business hours without directly satisfying the goal to separate physical link faults from malicious packet drops.

F:

Loss rates and direction measurements distinguish reliability problems from pure server processing delay; the technique works for situations involving determine whether unstable application sessions coincide with dropped network traffic, rather than this need to separate physical link faults from malicious packet drops.

Question 761

To identify a remote network path with rising delay during business hours, which approach should a network traffic analyst choose?

  1. Interface error counters
  2. Round-trip latency monitoring
  3. Throughput-versus-bandwidth distinction
  4. QoS queue monitoring

Explanation

Correct Answer

B:

RTT trends reveal timing degradation but cannot alone locate which hop or endpoint caused it; this choice fits the scenario because the team must identify a remote network path with rising delay during business hours.

Incorrect Answers

A:

CRC errors and discards provide clues to media or congestion issues outside IP application logs; it could help someone trying to separate physical link faults from malicious packet drops, but the problem is instead to identify a remote network path with rising delay during business hours.

C:

Protocol overhead, congestion and endpoints reduce achieved throughput beneath nominal link capacity; a team would select it to avoid assuming a gigabit link always delivers one gigabit of application data, which does not provide the particular result to identify a remote network path with rising delay during business hours.

D:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; its operational purpose is to detect priority voice traffic starved by a misconfigured egress scheduler, not to achieve the specific requirement to identify a remote network path with rising delay during business hours.

Question 762

To explain inconsistent voice-call quality even when average latency looks acceptable, which method is designed for the task?

  1. Packet-loss measurement
  2. Throughput-versus-bandwidth distinction
  3. Jitter measurement
  4. Round-trip latency monitoring

Explanation

Correct Answer

C:

Variation in packet delay affects real-time playback buffers and interactive communication; this mechanism directly supports the requirement to explain inconsistent voice-call quality even when average latency looks acceptable.

Incorrect Answers

A:

Loss rates and direction measurements distinguish reliability problems from pure server processing delay; although relevant to determine whether unstable application sessions coincide with dropped network traffic, it does not by itself achieve the required task to explain inconsistent voice-call quality even when average latency looks acceptable.

B:

Protocol overhead, congestion and endpoints reduce achieved throughput beneath nominal link capacity; it could help someone trying to avoid assuming a gigabit link always delivers one gigabit of application data, but the problem is instead to explain inconsistent voice-call quality even when average latency looks acceptable.

D:

RTT trends reveal timing degradation but cannot alone locate which hop or endpoint caused it; a team would select it to identify a remote network path with rising delay during business hours, which does not provide the particular result to explain inconsistent voice-call quality even when average latency looks acceptable.

Question 763

To determine whether unstable application sessions coincide with dropped network traffic, what technique should the team use?

  1. Packet-loss measurement
  2. SNMP interface trend
  3. Round-trip latency monitoring
  4. QoS queue monitoring

Explanation

Correct Answer

A:

Loss rates and direction measurements distinguish reliability problems from pure server processing delay; it supplies the specific control needed to determine whether unstable application sessions coincide with dropped network traffic.

Incorrect Answers

B:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; although relevant to compare switch utilization across several weeks of routine operation, it does not by itself achieve the required task to determine whether unstable application sessions coincide with dropped network traffic.

C:

RTT trends reveal timing degradation but cannot alone locate which hop or endpoint caused it; it could help someone trying to identify a remote network path with rising delay during business hours, but the problem is instead to determine whether unstable application sessions coincide with dropped network traffic.

D:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; that is useful when the task is to detect priority voice traffic starved by a misconfigured egress scheduler, not the stated requirement to determine whether unstable application sessions coincide with dropped network traffic.

Question 764

To avoid assuming a gigabit link always delivers one gigabit of application data, which protective or investigative measure applies?

  1. Throughput-versus-bandwidth distinction
  2. Round-trip latency monitoring
  3. Interface error counters
  4. Packet-loss measurement

Explanation

Correct Answer

A:

Protocol overhead, congestion and endpoints reduce achieved throughput beneath nominal link capacity; that is why it addresses the operational task to avoid assuming a gigabit link always delivers one gigabit of application data.

Incorrect Answers

B:

RTT trends reveal timing degradation but cannot alone locate which hop or endpoint caused it; the outcome it supports is to identify a remote network path with rising delay during business hours, whereas this scenario asks defenders to avoid assuming a gigabit link always delivers one gigabit of application data.

C:

CRC errors and discards provide clues to media or congestion issues outside IP application logs; although relevant to separate physical link faults from malicious packet drops, it does not by itself achieve the required task to avoid assuming a gigabit link always delivers one gigabit of application data.

D:

Loss rates and direction measurements distinguish reliability problems from pure server processing delay; it could help someone trying to determine whether unstable application sessions coincide with dropped network traffic, but the problem is instead to avoid assuming a gigabit link always delivers one gigabit of application data.

Question 765

To detect priority voice traffic starved by a misconfigured egress scheduler, what is the most direct option?

  1. QoS queue monitoring
  2. Jitter measurement
  3. SNMP interface trend
  4. Packet capture retention policy
  5. Throughput-versus-bandwidth distinction

Explanation

Correct Answer

A:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; its relevant protective or investigative effect is to detect priority voice traffic starved by a misconfigured egress scheduler.

Incorrect Answers

B:

Variation in packet delay affects real-time playback buffers and interactive communication; its mechanism supports explain inconsistent voice-call quality even when average latency looks acceptable, while the requested control must be able to detect priority voice traffic starved by a misconfigured egress scheduler.

C:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; the outcome it supports is to compare switch utilization across several weeks of routine operation, whereas this scenario asks defenders to detect priority voice traffic starved by a misconfigured egress scheduler.

D:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; although relevant to limit storage duration for sensitive network traces after an investigation, it does not by itself achieve the required task to detect priority voice traffic starved by a misconfigured egress scheduler.

E:

Protocol overhead, congestion and endpoints reduce achieved throughput beneath nominal link capacity; it could help someone trying to avoid assuming a gigabit link always delivers one gigabit of application data, but the problem is instead to detect priority voice traffic starved by a misconfigured egress scheduler.

Question 766

To identify hosts producing disproportionate outbound bytes on a WAN circuit, what should defenders select?

  1. Traffic mirror audit
  2. NetFlow top talkers
  3. QoS queue monitoring
  4. SNMP interface trend

Explanation

Correct Answer

B:

Ranked flow summaries highlight traffic contributors for authorization and capacity review; the requested outcome is precisely to identify hosts producing disproportionate outbound bytes on a WAN circuit.

Incorrect Answers

A:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; it addresses the different need to verify the monitoring configuration includes both directions of a critical VLAN, leaving the requested ability to identify hosts producing disproportionate outbound bytes on a WAN circuit unresolved.

C:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; its mechanism supports detect priority voice traffic starved by a misconfigured egress scheduler, while the requested control must be able to identify hosts producing disproportionate outbound bytes on a WAN circuit.

D:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; the outcome it supports is to compare switch utilization across several weeks of routine operation, whereas this scenario asks defenders to identify hosts producing disproportionate outbound bytes on a WAN circuit.

Question 767

To compare switch utilization across several weeks of routine operation, which mechanism best fits?

  1. Traffic mirror audit
  2. Packet capture retention policy
  3. SNMP interface trend
  4. NetFlow top talkers

Explanation

Correct Answer

C:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; this choice fits the scenario because the team must compare switch utilization across several weeks of routine operation.

Incorrect Answers

A:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; applying it would serve verify the monitoring configuration includes both directions of a critical VLAN without directly satisfying the goal to compare switch utilization across several weeks of routine operation.

B:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; it addresses the different need to limit storage duration for sensitive network traces after an investigation, leaving the requested ability to compare switch utilization across several weeks of routine operation unresolved.

D:

Ranked flow summaries highlight traffic contributors for authorization and capacity review; its mechanism supports identify hosts producing disproportionate outbound bytes on a WAN circuit, while the requested control must be able to compare switch utilization across several weeks of routine operation.

Question 768

To decide whether a new destination is malicious or part of an approved rollout, which measure best meets the requirement?

  1. Network anomaly alert correlation
  2. QoS queue monitoring
  3. Packet capture retention policy
  4. Traffic mirror audit

Explanation

Correct Answer

A:

Combining flow, DNS, identity and change evidence improves signal precision; this mechanism directly supports the requirement to decide whether a new destination is malicious or part of an approved rollout.

Incorrect Answers

B:

Queue drop and latency metrics show whether traffic classification and scheduling meet service goals; applying it would serve detect priority voice traffic starved by a misconfigured egress scheduler without directly satisfying the goal to decide whether a new destination is malicious or part of an approved rollout.

C:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; it addresses the different need to limit storage duration for sensitive network traces after an investigation, leaving the requested ability to decide whether a new destination is malicious or part of an approved rollout unresolved.

D:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; the technique works for situations involving verify the monitoring configuration includes both directions of a critical VLAN, rather than this need to decide whether a new destination is malicious or part of an approved rollout.

Question 769

To verify the monitoring configuration includes both directions of a critical VLAN, what control should be selected?

  1. Packet capture retention policy
  2. SNMP interface trend
  3. Traffic mirror audit
  4. Network anomaly alert correlation

Explanation

Correct Answer

C:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; it supplies the specific control needed to verify the monitoring configuration includes both directions of a critical VLAN.

Incorrect Answers

A:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; a team would select it to limit storage duration for sensitive network traces after an investigation, which does not provide the particular result to verify the monitoring configuration includes both directions of a critical VLAN.

B:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; its operational purpose is to compare switch utilization across several weeks of routine operation, not to achieve the specific requirement to verify the monitoring configuration includes both directions of a critical VLAN.

D:

Combining flow, DNS, identity and change evidence improves signal precision; it addresses the different need to decide whether a new destination is malicious or part of an approved rollout, leaving the requested ability to verify the monitoring configuration includes both directions of a critical VLAN unresolved.

Question 770

To limit storage duration for sensitive network traces after an investigation, which practice addresses that objective?

  1. Packet capture retention policy
  2. NetFlow top talkers
  3. SNMP interface trend
  4. Traffic mirror audit
  5. Network anomaly alert correlation

Explanation

Correct Answer

A:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; that is why it addresses the operational task to limit storage duration for sensitive network traces after an investigation.

Incorrect Answers

B:

Ranked flow summaries highlight traffic contributors for authorization and capacity review; a team would select it to identify hosts producing disproportionate outbound bytes on a WAN circuit, which does not provide the particular result to limit storage duration for sensitive network traces after an investigation.

C:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; its operational purpose is to compare switch utilization across several weeks of routine operation, not to achieve the specific requirement to limit storage duration for sensitive network traces after an investigation.

D:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; applying it would serve verify the monitoring configuration includes both directions of a critical VLAN without directly satisfying the goal to limit storage duration for sensitive network traces after an investigation.

E:

Combining flow, DNS, identity and change evidence improves signal precision; it addresses the different need to decide whether a new destination is malicious or part of an approved rollout, leaving the requested ability to limit storage duration for sensitive network traces after an investigation unresolved.

Certified Network Defender (312-38) Practice Tests