CompTIA SK0-005 Practice Test 27
Question 260
A change board is planning a verified response to this server event: A stretched cluster was configured without quorum design for a network partition between sites, creating divergent writes. For the Cluster quorum and split-brain prevention issue, which response elements belong in the approved plan? Select TWO answers.
- Set authoritative zone records and split-view policy correctly, then validate resolver paths, TTL and cache expiration.
- Configure an appropriate witness and quorum voting model with fencing or leader election to avoid simultaneous primaries.
- Force both partitioned nodes active to maximize the apparent number of running servers.
- Review cluster vote configuration, witness reachability, fencing logs and simulated partition behavior.
- Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
Explanation
Correct Answer
B:Availability must preserve data consistency during partitions; an extra node is not sufficient without quorum and fencing. This is the appropriate targeted correction for Cluster quorum and split-brain prevention.
D:These observations investigate the exact Cluster quorum and split-brain prevention failure rather than unrelated components. Confirm remediation through: During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
Incorrect Answers
A:That option would set authoritative zone records and split-view policy correctly, then validate resolver paths, TTL and cache expiration, but it addresses a different concern. Availability must preserve data consistency during partitions; an extra node is not sufficient without quorum and fencing.
C:Incident: A stretched cluster was configured without quorum design for a network partition between sites, creating divergent writes.
E:This statement concerns Load balancer health checking, a different Server+ technical control. It does not directly address the reported Cluster quorum and split-brain prevention fault or prove its repair.
Question 261
A server administrator is investigating a server issue involving load balancer health checking: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Configure an appropriate witness and quorum voting model with fencing or leader election to avoid simultaneous primaries.
- Mark a backend healthy solely because the VM answers ping.
- Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments.
- Define supported sync/async replication and failover mechanisms consistent with RPO/RTO; test role promotion and endpoint switching.
Explanation
Correct Answer
C:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. For this case, A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors.
Incorrect Answers
A:That option would configure an appropriate witness and quorum voting model with fencing or leader election to avoid simultaneous primaries, but it addresses a different concern. A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
B:This is the unsafe shortcut in the Load balancer health checking scenario, not a justified remediation or diagnostic. A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
D:That option would define supported sync/async replication and failover mechanisms consistent with RPO/RTO; test role promotion and endpoint switching, but it addresses a different concern. A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
Question 262
While reviewing the CompTIA Server+ administration incident, a technician learns: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Snapshots depend on the underlying datastore and often have performance/space costs; they are not independent backups.
- A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
- Network boot is a high-trust supply chain; authenticated image provenance and secret protection matter as much as automation speed.
- DHCP broadcasts normally need a relay across routed subnets, and leases must match the client network and scope policy.
Explanation
Correct Answer
B:Applying it leads to this operational action: Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments. Collect evidence first: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
Incorrect Answers
A:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
C:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
D:This statement concerns DHCP scope and relay design, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
Question 263
Before a server change is approved, the on-call engineer receives this incident report: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
- Review cluster vote configuration, witness reachability, fencing logs and simulated partition behavior.
- Mark a backend healthy solely because the VM answers ping.
- Trace DHCP/PXE boot source, image hashes and signatures, access ACLs and answer-file permissions.
Explanation
Correct Answer
A:The expected technical relationship is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors.
Incorrect Answers
B:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
C:This is the unsafe shortcut in the Load balancer health checking scenario, not a justified remediation or diagnostic. Discriminate using: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
D:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors.
Question 264
After the team implements a targeted remediation for Load balancer health checking, the original incident was: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Clients on each VLAN consistently obtain valid leases with correct options and no address conflicts.
- A rehearsed failover restores service within RTO with observed data loss no greater than RPO.
- Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
- The VM migrates without guest interruption and maintains its workload performance after placement.
Explanation
Correct Answer
C:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors.
Incorrect Answers
A:This statement concerns DHCP scope and relay design, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair.
B:This statement concerns Database replication and failover objective, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
D:This statement concerns Live migration compatibility and resource headroom, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
Question 265
A change board is planning a verified response to this server event: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors. For the Load balancer health checking issue, which response elements belong in the approved plan? Select ONE best answer.
- Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments. Then validate the change by confirming: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
- Inventory physical cores, virtual instances, license assignments, agreement version and current usage.
- Mark a backend healthy solely because the VM answers ping.
- Restrict PXE and imaging infrastructure to trusted networks and protect signed, versioned images and unattended-install credentials.
Explanation
Correct Answer
A:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Before modifying systems, gather: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
Incorrect Answers
B:This statement concerns Per-core and virtual machine licensing, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
C:This is the unsafe shortcut in the Load balancer health checking scenario, not a justified remediation or diagnostic. Incident: A load balancer reports healthy backends when port 443 accepts TCP but the application endpoint returns repeated 503 errors.
D:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair.
Question 266
A server administrator is investigating a server issue involving load balancer health checking: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments.
- Maintain a software bill of materials and honor relevant distribution, attribution and support-license obligations.
- Mark a backend healthy solely because the VM answers ping.
- Configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset.
Explanation
Correct Answer
A:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. For this case, A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness.
Incorrect Answers
B:That option would maintain a software bill of materials and honor relevant distribution, attribution and support-license obligations, but it addresses a different concern. A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
C:This is the unsafe shortcut in the Load balancer health checking scenario, not a justified remediation or diagnostic. Incident: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness.
D:That option would configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset, but it addresses a different concern. A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
Question 267
While reviewing the CompTIA Server+ administration incident, a technician learns: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- DNS answers depend on resolver selection, authoritative records and caching; a ping of one host does not validate all name-resolution paths.
- Open-source use still carries license conditions, and support subscriptions are separate from copyright permissions.
- A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
- Time synchronization is required for trustworthy logs, certificate validation windows and time-sensitive authentication.
Explanation
Correct Answer
C:Applying it leads to this operational action: Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments.
Incorrect Answers
A:This statement concerns DNS split-horizon and resolver troubleshooting, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
B:This statement concerns Open-source license obligations and audit, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
D:This statement concerns NTP time sources and clock skew, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
Question 268
Before a server change is approved, the on-call engineer receives this incident report: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Mark a backend healthy solely because the VM answers ping.
- Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
- Query each resolver directly, inspect answer sections and TTLs, compare private/public zones and client resolver lists.
- Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
Explanation
Correct Answer
D:The expected technical relationship is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness.
Incorrect Answers
A:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
B:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness.
C:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. This statement concerns DNS split-horizon and resolver troubleshooting, a different Server+ technical control.
Question 269
After the team implements a targeted remediation for Load balancer health checking, the original incident was: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Deployments have traceable licenses and required notices or source obligations are fulfilled.
- Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
- Installed instances and host resources are covered by documented valid entitlements after migration.
- During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
Explanation
Correct Answer
B:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Incident: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness.
Incorrect Answers
A:This statement concerns Open-source license obligations and audit, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair.
C:This statement concerns Per-core and virtual machine licensing, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
D:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported Load balancer health checking fault or prove its repair. For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. A targeted investigation checks: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections. The desired recovery condition is: Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
Question 270
A change board is planning a verified response to this server event: A new web release rolls out while a pool member takes 90 seconds to warm up, causing clients to receive failures before readiness. For the Load balancer health checking issue, which response elements belong in the approved plan? Select TWO answers.
- During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
- Mark a backend healthy solely because the VM answers ping.
- Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
- Set authoritative zone records and split-view policy correctly, then validate resolver paths, TTL and cache expiration.
- Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments.
Explanation
Correct Answer
C:The expected technical relationship is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. These observations investigate the exact Load balancer health checking failure rather than unrelated components.
E:A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. Before rollout, confirm the problem with: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
Incorrect Answers
A:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control.
B:Discriminate using: Compare TCP checks with application-level probe status, backend error rates, warm-up time and active connections.
D:For this incident, the relevant principle is: A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions. It does not directly address the reported Load balancer health checking fault or prove its repair.