CompTIA SK0-005 Practice Test 74
Question 730
A change board is planning a verified response to this server event: A hypervisor moves a VM to another switch and loses one tenant network because the destination trunk allows fewer VLANs. For the Incorrect switch VLAN trunk allowance issue, which response elements belong in the approved plan? Select TWO answers.
- Validate zoning, masking, path policies and fabric independence; restore optimized healthy multipath.
- Inspect switchport mode, native VLAN, allowed VLAN set, MAC learning and packet tags on the affected uplink.
- Connections complete through approved paths in both directions without broad firewall bypasses.
- Convert every trunk to allow all VLANs to avoid diagnosing the missing tenant tag.
- Correct access/trunk VLAN membership and allowed VLAN lists while preserving intended segmentation.
Explanation
Correct Answer
B:These observations investigate the exact Incorrect switch VLAN trunk allowance failure rather than unrelated components. The expected technical relationship is: Tagged VLAN traffic must be permitted end-to-end; routing changes do not repair a missing layer-two VLAN path.
E:Tagged VLAN traffic must be permitted end-to-end; routing changes do not repair a missing layer-two VLAN path. A successful outcome is: Only intended VLANs traverse the trunk and test VMs reach their approved peers.
Incorrect Answers
A:For this incident, the relevant principle is: Tagged VLAN traffic must be permitted end-to-end; routing changes do not repair a missing layer-two VLAN path. This statement concerns SAN fabric multipath failover and latency, a different Server+ technical control.
C:For this incident, the relevant principle is: Tagged VLAN traffic must be permitted end-to-end; routing changes do not repair a missing layer-two VLAN path. This statement concerns Routing and stateful firewall asymmetry, a different Server+ technical control.
D:Tagged VLAN traffic must be permitted end-to-end; routing changes do not repair a missing layer-two VLAN path. Discriminate using: Inspect switchport mode, native VLAN, allowed VLAN set, MAC learning and packet tags on the affected uplink.
Question 731
A server administrator is investigating a server issue involving dns client-specific failure: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
- Inspect forward/return routing, gateway selection and stateful firewall rules; correct the narrow route or policy.
- Change the application's database schema to compensate for an unresolved hostname.
- Correct access/trunk VLAN membership and allowed VLAN lists while preserving intended segmentation.
Explanation
Correct Answer
A:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Incorrect Answers
B:That option would inspect forward/return routing, gateway selection and stateful firewall rules; correct the narrow route or policy, but it addresses a different concern. Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
C:This is the unsafe shortcut in the DNS client-specific failure scenario, not a justified remediation or diagnostic. Incident: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address.
D:This statement concerns Incorrect switch VLAN trunk allowance, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
Question 732
While reviewing the CompTIA Server+ administration incident, a technician learns: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Thermal throttling and protective shutdown may result from heat transfer or airflow faults even without high average CPU use.
- Intermittent IP conflicts and unauthorized DHCP options can appear as random server outages while switch ports remain healthy.
- Power redundancy requires end-to-end capacity and isolation, not merely green status indicators on redundant modules.
- Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Explanation
Correct Answer
D:Applying it leads to this operational action: Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
Incorrect Answers
A:This statement concerns Thermal shutdown and heatsink diagnostics, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
B:This statement concerns DHCP and IP address conflict isolation, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
C:This statement concerns PSU and power event isolation, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
Question 733
Before a server change is approved, the on-call engineer receives this incident report: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Change the application's database schema to compensate for an unresolved hostname.
- Capture DHCP offers and ARP announcements, inspect scope exclusions, MAC addresses and gateway options.
- Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs.
- Trace route tables, firewall session logs, interface captures and asymmetric path metrics.
Explanation
Correct Answer
C:Use findings to decide whether to: Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
Incorrect Answers
A:This is the unsafe shortcut in the DNS client-specific failure scenario, not a justified remediation or diagnostic. Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
B:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs.
D:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Question 734
After the team implements a targeted remediation for DNS client-specific failure, the original incident was: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Affected clients resolve the correct application endpoint and connect consistently.
- Sustained stress tests run within component thermal limits without unexpected throttling or shutdown.
- Transfer throughput and latency recover while physical error counters remain stable.
- Only intended VLANs traverse the trunk and test VMs reach their approved peers.
Explanation
Correct Answer
A:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Incorrect Answers
B:This statement concerns Thermal shutdown and heatsink diagnostics, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair.
C:This statement concerns NIC port errors and duplex mismatch, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
D:This statement concerns Incorrect switch VLAN trunk allowance, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair.
Question 735
A change board is planning a verified response to this server event: An internal service is reachable by IP but fails by name on one server because its resolver points to an obsolete DNS address. For the DNS client-specific failure issue, which response elements belong in the approved plan? Select ONE best answer.
- Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior. Then validate the change by confirming: Affected clients resolve the correct application endpoint and connect consistently.
- Change the application's database schema to compensate for an unresolved hostname.
- Compare df -h and df -i, user quotas, deleted-open files and per-directory usage.
- Trace conflicting ARP/DHCP responses, eliminate overlapping assignments or rogue offers and correct lease options.
Explanation
Correct Answer
A:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. The proposed change and outcome assessment work together for DNS client-specific failure.
Incorrect Answers
B:This is the unsafe shortcut in the DNS client-specific failure scenario, not a justified remediation or diagnostic. Discriminate using: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs.
C:That option would compare df -h and df -i, user quotas, deleted-open files and per-directory usage, but it addresses a different concern. Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
D:That option would trace conflicting ARP/DHCP responses, eliminate overlapping assignments or rogue offers and correct lease options, but it addresses a different concern. Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Question 736
A server administrator is investigating a server issue involving dns client-specific failure: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Correlate ECC and memory training events with physical slots, then replace faulty qualified DIMMs using approved service steps.
- Change the application's database schema to compensate for an unresolved hostname.
- Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
- Record symptoms and recent changes, form a testable hypothesis, change one variable at a time and preserve rollback evidence.
Explanation
Correct Answer
C:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Incorrect Answers
A:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
B:This is the unsafe shortcut in the DNS client-specific failure scenario, not a justified remediation or diagnostic. Incident: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully.
D:That option would record symptoms and recent changes, form a testable hypothesis, change one variable at a time and preserve rollback evidence, but it addresses a different concern. Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Question 737
While reviewing the CompTIA Server+ administration incident, a technician learns: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- A repeatable incident method isolates causes and prevents uncontrolled fixes from introducing new failures.
- Correctable memory errors are early-warning evidence; a rising count can precede uncorrectable failures.
- Filesystem write failures can arise from inode or quota limits as well as free-block exhaustion.
- Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Explanation
Correct Answer
D:Applying it leads to this operational action: Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
Incorrect Answers
A:This statement concerns Structured troubleshooting hypothesis and controlled change, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
B:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair.
C:This statement concerns Filesystem full, inode exhaustion and quotas, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
Question 738
Before a server change is approved, the on-call engineer receives this incident report: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs.
- Compare df -h and df -i, user quotas, deleted-open files and per-directory usage.
- Change the application's database schema to compensate for an unresolved hostname.
- Trace route tables, firewall session logs, interface captures and asymmetric path metrics.
Explanation
Correct Answer
A:Use findings to decide whether to: Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
Incorrect Answers
B:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
C:Incident: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully.
D:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. This statement concerns Routing and stateful firewall asymmetry, a different Server+ technical control.
Question 739
After the team implements a targeted remediation for DNS client-specific failure, the original incident was: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Affected clients resolve the correct application endpoint and connect consistently.
- Only intended VLANs traverse the trunk and test VMs reach their approved peers.
- Hardware reports no recurring ECC faults and memory validation passes under representative load.
- Unapproved outbound flows stop, legitimate data transfers remain and incident findings are documented.
Explanation
Correct Answer
A:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
Incorrect Answers
B:This statement concerns Incorrect switch VLAN trunk allowance, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
C:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
D:This statement concerns Unauthorized outbound traffic and exfiltration detection, a different Server+ technical control. It does not directly address the reported DNS client-specific failure fault or prove its repair. For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. A targeted investigation checks: Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs. The desired recovery condition is: Affected clients resolve the correct application endpoint and connect consistently.
Question 740
A change board is planning a verified response to this server event: A web node has stale negative DNS cache after an application record is created, while peer nodes resolve successfully. For the DNS client-specific failure issue, which response elements belong in the approved plan? Select TWO answers.
- Change the application's database schema to compensate for an unresolved hostname.
- Compare dig/nslookup answers per resolver, cache state, DNS suffix, zone authority and TTLs.
- Only intended VLANs traverse the trunk and test VMs reach their approved peers.
- Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
- Identify whether blocks, inodes, quotas or reserved space is exhausted; reclaim or expand only the constrained resource.
Explanation
Correct Answer
B:Use findings to decide whether to: Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior. These observations investigate the exact DNS client-specific failure failure rather than unrelated components.
D:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. This is the appropriate targeted correction for DNS client-specific failure.
Incorrect Answers
A:Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
C:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. This statement concerns Incorrect switch VLAN trunk allowance, a different Server+ technical control.
E:For this incident, the relevant principle is: Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries. This statement concerns Filesystem full, inode exhaustion and quotas, a different Server+ technical control.