McAfee Secure

Huawei H12-811 Bundle

Exam Code: H12-811

Exam Name HCIA-Datacom V1.0

Certification Provider: Huawei

Corresponding Certification: HCIA-Datacom

Huawei H12-811 Bundle $25.00

100% Huawei H12-811 Guaranteed Success With Testking Training Materials

Get Real H12-811 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    H12-811 Questions & Answers

    445 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual H12-811 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • H12-811 Video Course

    H12-811 Training Course

    40 Video Lectures

    H12-811 Video Course is developed by Huawei Professionals to help you pass the H12-811 exam.

    Description

    This course will improve your knowledge and skills required to pass HCIA-Datacom V1.0 exam.

HCIA-Datacom V1.0 (H12-811) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    445 Questions

    $124.99
  • H12-811 Video Course

    Training Course

    40 Video Lectures

    $39.99

Huawei H12-811 Practice Test 54

Question 530

During an independent network handover at the River Mill branch of Kingsmere Media, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8994. The on-duty analyst documents this symptom before proposing any configuration: A branch client VLAN has no local DHCP server and its broadcast Discover requests never reach the centralized server. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at River Mill: Track active leases, allocation errors and address-conflict alarms.
  2. For a monitoring check at River Mill: Monitor relay request/response counts and per-VLAN lease success.
  3. For a monitoring check at River Mill: Review ACL range expansion and overbroad rule matches.
  4. For a monitoring check at River Mill: Audit interface-to-ACL bindings and denied-flow logs.

Answer and explanations

A.

Track active leases, allocation errors and address-conflict alarms. This alternative addresses a different issue (dhcp address pool depletion). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A branch client VLAN has no local DHCP server and its broadcast Discover requests never reach the centralized server. The decisive distinction is: Monitor relay request/response counts and per-VLAN lease success.

B.

The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: A branch client VLAN has no local DHCP server and its broadcast Discover requests never reach the centralized server. Monitor relay request/response counts and per-VLAN lease success.

C.

Review ACL range expansion and overbroad rule matches. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A branch client VLAN has no local DHCP server and its broadcast Discover requests never reach the centralized server. This alternative addresses a different issue (acl wildcard matching). The decisive distinction is: Monitor relay request/response counts and per-VLAN lease success.

D.

This alternative addresses a different issue (acl direction and placement). The option would address: Audit interface-to-ACL bindings and denied-flow logs. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A branch client VLAN has no local DHCP server and its broadcast Discover requests never reach the centralized server.

Question 531

At Quarry Creek School in Whitehaven, engineers maintain a small Huawei VRP-based wired/WLAN campus for air-quality sensor reporting, with client segment 10.91.44.0/24. An approved maintenance window follows change DC-9006. The change team records this observable condition: Clients can ping an application by IP but fail by hostname after a DNS server change. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. What explanation best fits the observed network failure, rather than a merely possible separate fault?

  1. For DC-9006 at Whitehaven, the technical interpretation is: Reachability through an inter-VLAN gateway is not the same as an approved least-privilege security policy.
  2. For DC-9006 at Whitehaven, the technical interpretation is: The rule's direction and placement do not align with the actual packet traversal path.
  3. For DC-9006 at Whitehaven, the technical interpretation is: Name resolution fails independently of data-plane reachability to the service IP.
  4. For DC-9006 at Whitehaven, the technical interpretation is: The management-plane identity source lacks individually attributable centralized AAA authentication.

Answer and explanations

A.

This alternative addresses a different issue (security segmentation gateway rules). Reachability through an inter-VLAN gateway is not the same as an approved least-privilege security policy. In the reported case: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Name resolution fails independently of data-plane reachability to the service IP.

B.

The rule's direction and placement do not align with the actual packet traversal path. The observed condition is: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (acl direction and placement). The decisive distinction is: Name resolution fails independently of data-plane reachability to the service IP.

C.

Name resolution fails independently of data-plane reachability to the service IP. The reported evidence is: Clients can ping an application by IP but fail by hostname after a DNS server change. Confirm the affected layer or service before applying a configuration change.

D.

The management-plane identity source lacks individually attributable centralized AAA authentication. This alternative addresses a different issue (aaa management authentication). The reported case is: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Name resolution fails independently of data-plane reachability to the service IP.

Question 532

At Quarry Creek School in Whitehaven, engineers maintain a small Huawei VRP-based wired/WLAN campus for air-quality sensor reporting, with client segment 10.91.44.0/24. An approved maintenance window follows change DC-9006. The change team records this observable condition: Clients can ping an application by IP but fail by hostname after a DNS server change. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which precise corrective change addresses the demonstrated failure with minimal unrelated disruption?

  1. For a controlled repair of air-quality sensor reporting in Whitehaven: Trace source, destination and ingress/egress direction before applying the ACL on the correct interface and direction.
  2. For a controlled repair of air-quality sensor reporting in Whitehaven: Restrict management source networks and use authenticated SSH or another supported encrypted interface instead of Telnet.
  3. For a controlled repair of air-quality sensor reporting in Whitehaven: Configure the authorized DHCP relay target on the correct gateway interface and allow the required UDP exchange.
  4. For a controlled repair of air-quality sensor reporting in Whitehaven: Check configured resolvers, queries and authoritative records before editing routes or switch ports.

Answer and explanations

A.

For a controlled repair of air-quality sensor reporting in Whitehaven: Trace source, destination and ingress/egress direction before applying the ACL on the correct interface and direction. The observed condition is: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (acl direction and placement). The decisive distinction is: For a controlled repair of air-quality sensor reporting in Whitehaven: Check configured resolvers, queries and authoritative records before editing routes or switch ports.

B.

This alternative addresses a different issue (management plane secure access). The option would address: For a controlled repair of air-quality sensor reporting in Whitehaven: Restrict management source networks and use authenticated SSH or another supported encrypted interface instead of Telnet. The scenario instead reports: Clients can ping an application by IP but fail by hostname after a DNS server change.

C.

For a controlled repair of air-quality sensor reporting in Whitehaven: Configure the authorized DHCP relay target on the correct gateway interface and allow the required UDP exchange. This alternative addresses a different issue (dhcp relay across vlans). The reported case is: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: For a controlled repair of air-quality sensor reporting in Whitehaven: Check configured resolvers, queries and authoritative records before editing routes or switch ports.

D.

Clients can ping an application by IP but fail by hostname after a DNS server change. That points to this explanation: For a controlled repair of air-quality sensor reporting in Whitehaven: Check configured resolvers, queries and authoritative records before editing routes or switch ports. Validate it through the controlled case because A correct DNS response does not prove the target application is healthy.

Question 533

At Quarry Creek School in Whitehaven, engineers maintain a small Huawei VRP-based wired/WLAN campus for air-quality sensor reporting, with client segment 10.91.44.0/24. An approved maintenance window follows change DC-9006. The change team records this observable condition: Clients can ping an application by IP but fail by hostname after a DNS server change. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which acceptance evidence most directly demonstrates that the proposed targeted correction works?

  1. For acceptance review of Whitehaven change DC-9006: The correct hostname resolves to its intended address and the application succeeds using the name.
  2. For acceptance review of Whitehaven change DC-9006: Named test administrators authenticate with their own identities and audit records associate actions to users.
  3. For acceptance review of Whitehaven change DC-9006: Several fresh clients obtain unique leases with the correct mask, gateway and DNS options.
  4. For acceptance review of Whitehaven change DC-9006: Only the documented /27 test addresses match the intended ACL entry while adjacent ranges do not.

Answer and explanations

A.

The correct hostname resolves to its intended address and the application succeeds using the name. This addresses the decisive observation: Clients can ping an application by IP but fail by hostname after a DNS server change.

B.

Named test administrators authenticate with their own identities and audit records associate actions to users. This alternative addresses a different issue (would not prove the reported issue was corrected). The reported case is: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: The correct hostname resolves to its intended address and the application succeeds using the name.

C.

This alternative addresses a different issue (would not prove the reported issue was corrected). Several fresh clients obtain unique leases with the correct mask, gateway and DNS options. In the reported case: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: The correct hostname resolves to its intended address and the application succeeds using the name.

D.

Only the documented /27 test addresses match the intended ACL entry while adjacent ranges do not. The observed condition is: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (would not prove the reported issue was corrected). The decisive distinction is: The correct hostname resolves to its intended address and the application succeeds using the name.

Question 534

At Quarry Creek School in Whitehaven, engineers maintain a small Huawei VRP-based wired/WLAN campus for air-quality sensor reporting, with client segment 10.91.44.0/24. An approved maintenance window follows change DC-9006. The change team records this observable condition: Clients can ping an application by IP but fail by hostname after a DNS server change. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which remaining limitation should the engineer explicitly record even after the targeted repair?

  1. For the Whitehaven network design record: NAT does not itself authorize outbound traffic or provide application encryption.
  2. For the Whitehaven network design record: A correct DNS response does not prove the target application is healthy.
  3. For the Whitehaven network design record: Segmentation rules cannot replace endpoint authorization and do not assure data confidentiality alone.
  4. For the Whitehaven network design record: Enlarging a DHCP pool cannot fix a DHCP relay path or a VLAN tagging mismatch.

Answer and explanations

A.

For the Whitehaven network design record: NAT does not itself authorize outbound traffic or provide application encryption. This alternative addresses a different issue (nat outbound translation). The reported case is: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: For the Whitehaven network design record: A correct DNS response does not prove the target application is healthy.

B.

The decisive evidence is: Clients can ping an application by IP but fail by hostname after a DNS server change. For the Whitehaven network design record: A correct DNS response does not prove the target application is healthy.

C.

For the Whitehaven network design record: Segmentation rules cannot replace endpoint authorization and do not assure data confidentiality alone. The observed condition is: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (security segmentation gateway rules). The decisive distinction is: For the Whitehaven network design record: A correct DNS response does not prove the target application is healthy.

D.

This alternative addresses a different issue (dhcp address pool depletion). The option would address: For the Whitehaven network design record: Enlarging a DHCP pool cannot fix a DHCP relay path or a VLAN tagging mismatch. The scenario instead reports: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: For the Whitehaven network design record: A correct DNS response does not prove the target application is healthy.

Question 535

At Quarry Creek School in Whitehaven, engineers maintain a small Huawei VRP-based wired/WLAN campus for air-quality sensor reporting, with client segment 10.91.44.0/24. An approved maintenance window follows change DC-9006. The change team records this observable condition: Clients can ping an application by IP but fail by hostname after a DNS server change. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at Whitehaven: Track active leases, allocation errors and address-conflict alarms.
  2. For a monitoring check at Whitehaven: Review ACL range expansion and overbroad rule matches.
  3. For a monitoring check at Whitehaven: Track resolver latency, NXDOMAIN spikes and stale address records.
  4. For a monitoring check at Whitehaven: Audit interface-to-ACL bindings and denied-flow logs.

Answer and explanations

A.

This alternative addresses a different issue (dhcp address pool depletion). Track active leases, allocation errors and address-conflict alarms. In the reported case: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

B.

Review ACL range expansion and overbroad rule matches. The observed condition is: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (acl wildcard matching). The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

C.

Track resolver latency, NXDOMAIN spikes and stale address records. The reported evidence is: Clients can ping an application by IP but fail by hostname after a DNS server change.

D.

Audit interface-to-ACL bindings and denied-flow logs. This alternative addresses a different issue (acl direction and placement). The reported case is: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

Question 536

During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. What explanation best fits the observed network failure, rather than a merely possible separate fault?

  1. For DC-9011 at Hollow Creek, the technical interpretation is: First-match ACL processing allows traffic before the later denial is considered.
  2. For DC-9011 at Hollow Creek, the technical interpretation is: The ACL address wildcard has been confused with the subnet mask or prefix length.
  3. For DC-9011 at Hollow Creek, the technical interpretation is: Management services are exposed to an untrusted subnet and an unencrypted administrative protocol.
  4. For DC-9011 at Hollow Creek, the technical interpretation is: Name resolution fails independently of data-plane reachability to the service IP.

Answer and explanations

A.

First-match ACL processing allows traffic before the later denial is considered. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (acl rule ordering). The decisive distinction is: Name resolution fails independently of data-plane reachability to the service IP.

B.

This alternative addresses a different issue (acl wildcard matching). The option would address: The ACL address wildcard has been confused with the subnet mask or prefix length. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change.

C.

Management services are exposed to an untrusted subnet and an unencrypted administrative protocol. This alternative addresses a different issue (management plane secure access). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Name resolution fails independently of data-plane reachability to the service IP.

D.

The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. That points to this explanation: Name resolution fails independently of data-plane reachability to the service IP. Confirm the affected layer or service before applying a configuration change.

Question 537

During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which precise corrective change addresses the demonstrated failure with minimal unrelated disruption?

  1. For a controlled repair of production analytics in Hollow Creek: Check configured resolvers, queries and authoritative records before editing routes or switch ports.
  2. For a controlled repair of production analytics in Hollow Creek: Compute the intended address range and wildcard or use the platform's supported exact prefix matching.
  3. For a controlled repair of production analytics in Hollow Creek: Apply the approved source NAT policy to eligible outbound sessions after confirming route and security rules.
  4. For a controlled repair of production analytics in Hollow Creek: Configure approved NTP sources and verify clock/time-zone handling across the monitored devices.

Answer and explanations

A.

For a controlled repair of production analytics in Hollow Creek: Check configured resolvers, queries and authoritative records before editing routes or switch ports. This addresses the decisive observation: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. Validate it through the controlled case because A correct DNS response does not prove the target application is healthy.

B.

For a controlled repair of production analytics in Hollow Creek: Compute the intended address range and wildcard or use the platform's supported exact prefix matching. This alternative addresses a different issue (acl wildcard matching). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: For a controlled repair of production analytics in Hollow Creek: Check configured resolvers, queries and authoritative records before editing routes or switch ports.

C.

This alternative addresses a different issue (nat outbound translation). For a controlled repair of production analytics in Hollow Creek: Apply the approved source NAT policy to eligible outbound sessions after confirming route and security rules. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change.

D.

For a controlled repair of production analytics in Hollow Creek: Configure approved NTP sources and verify clock/time-zone handling across the monitored devices. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (ntp clock consistency). The decisive distinction is: For a controlled repair of production analytics in Hollow Creek: Check configured resolvers, queries and authoritative records before editing routes or switch ports.

Question 538

During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which acceptance evidence most directly demonstrates that the proposed targeted correction works?

  1. For acceptance review of Hollow Creek change DC-9011: Guest hosts cannot connect to management ports while authorized operators establish encrypted sessions.
  2. For acceptance review of Hollow Creek change DC-9011: The correct hostname resolves to its intended address and the application succeeds using the name.
  3. For acceptance review of Hollow Creek change DC-9011: The remote server sees the correct relay context and a test client receives an appropriate subnet lease.
  4. For acceptance review of Hollow Creek change DC-9011: Named test administrators authenticate with their own identities and audit records associate actions to users.

Answer and explanations

A.

Guest hosts cannot connect to management ports while authorized operators establish encrypted sessions. This alternative addresses a different issue (would not prove the reported issue was corrected). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: The correct hostname resolves to its intended address and the application succeeds using the name.

B.

The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The correct hostname resolves to its intended address and the application succeeds using the name.

C.

The remote server sees the correct relay context and a test client receives an appropriate subnet lease. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (would not prove the reported issue was corrected). The decisive distinction is: The correct hostname resolves to its intended address and the application succeeds using the name.

D.

This alternative addresses a different issue (would not prove the reported issue was corrected). The option would address: Named test administrators authenticate with their own identities and audit records associate actions to users. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change.

Question 539

During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which remaining limitation should the engineer explicitly record even after the targeted repair?

  1. For the Hollow Creek network design record: Adding a public address does not repair upstream packet loss or denied firewall policy.
  2. For the Hollow Creek network design record: ACL order cannot remediate a rule installed on the wrong interface or in the wrong direction.
  3. For the Hollow Creek network design record: A correct DNS response does not prove the target application is healthy.
  4. For the Hollow Creek network design record: A relay cannot choose a correct scope if the server is misconfigured or reachable only on a blocked return path.

Answer and explanations

A.

This alternative addresses a different issue (pat address exhaustion). For the Hollow Creek network design record: Adding a public address does not repair upstream packet loss or denied firewall policy. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change.

B.

For the Hollow Creek network design record: ACL order cannot remediate a rule installed on the wrong interface or in the wrong direction. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (acl rule ordering). The decisive distinction is: For the Hollow Creek network design record: A correct DNS response does not prove the target application is healthy.

C.

For the Hollow Creek network design record: A correct DNS response does not prove the target application is healthy. The reported evidence is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change.

D.

For the Hollow Creek network design record: A relay cannot choose a correct scope if the server is misconfigured or reachable only on a blocked return path. This alternative addresses a different issue (dhcp relay across vlans). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: For the Hollow Creek network design record: A correct DNS response does not prove the target application is healthy.

Question 540

During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at Hollow Creek: Monitor relay request/response counts and per-VLAN lease success.
  2. For a monitoring check at Hollow Creek: Track AAA availability, failed logins and emergency account use.
  3. For a monitoring check at Hollow Creek: Review ACL range expansion and overbroad rule matches.
  4. For a monitoring check at Hollow Creek: Track resolver latency, NXDOMAIN spikes and stale address records.

Answer and explanations

A.

Monitor relay request/response counts and per-VLAN lease success. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (dhcp relay across vlans). The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

B.

This alternative addresses a different issue (aaa management authentication). The option would address: Track AAA availability, failed logins and emergency account use. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

C.

Review ACL range expansion and overbroad rule matches. This alternative addresses a different issue (acl wildcard matching). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.

D.

The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. That points to this explanation: Track resolver latency, NXDOMAIN spikes and stale address records.