CompTIA SK0-005 Practice Test 29
Question 280
A change board is planning a verified response to this server event: A mission-critical service has a secondary instance, but the failover procedure never updates connection endpoints or verifies consistency. For the Database replication and failover objective 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.
- Measure apply lag, replication errors, client reconnection behavior and failover event timestamps.
- Define supported sync/async replication and failover mechanisms consistent with RPO/RTO; test role promotion and endpoint switching.
- Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
- Assume any asynchronous replica provides zero data loss and instant failover.
Explanation
Correct Answer
B:These observations investigate the exact Database replication and failover objective failure rather than unrelated components. The expected technical relationship is: A standby's existence does not prove recoverability; replication lag, failover automation and consistency determine outcomes.
C:A standby's existence does not prove recoverability; replication lag, failover automation and consistency determine outcomes. This is the appropriate targeted correction for Database replication and failover objective.
Incorrect Answers
A:For this incident, the relevant principle is: A standby's existence does not prove recoverability; replication lag, failover automation and consistency determine outcomes. It does not directly address the reported Database replication and failover objective fault or prove its repair.
D:For this incident, the relevant principle is: A standby's existence does not prove recoverability; replication lag, failover automation and consistency determine outcomes. This statement concerns Load balancer health checking, a different Server+ technical control.
E:Incident: A mission-critical service has a secondary instance, but the failover procedure never updates connection endpoints or verifies consistency.
Question 281
A server administrator is investigating a server issue involving hypervisor resource overcommit and reservations: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Right-size vCPU and RAM allocations using contention telemetry and supportable reservations or resource controls.
- Verify migration CPU compatibility, shared/storage accessibility and destination resource headroom before moving VMs.
- Align virtual switch and distributed port-group VLAN, uplink and security settings across hosts; preserve network isolation.
- Increase every VM's configured vCPU and RAM without checking host contention.
Explanation
Correct Answer
A:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A successful outcome is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Incorrect Answers
B:That option would verify migration CPU compatibility, shared/storage accessibility and destination resource headroom before moving VMs, but it addresses a different concern. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
C:That option would align virtual switch and distributed port-group VLAN, uplink and security settings across hosts; preserve network isolation, but it addresses a different concern. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
D:This is the unsafe shortcut in the Hypervisor resource overcommit and reservations scenario, not a justified remediation or diagnostic. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
Question 282
While reviewing the CompTIA Server+ administration incident, a technician learns: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization.
- Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
- DHCP broadcasts normally need a relay across routed subnets, and leases must match the client network and scope policy.
- Snapshots depend on the underlying datastore and often have performance/space costs; they are not independent backups.
Explanation
Correct Answer
B:The acceptance test is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation. This is the controlling principle for the reported Hypervisor resource overcommit and reservations incident.
Incorrect Answers
A:This statement concerns Containers and host isolation, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
C:This statement concerns DHCP scope and relay design, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
D:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Question 283
Before a server change is approved, the on-call engineer receives this incident report: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Increase every VM's configured vCPU and RAM without checking host contention.
- Inspect container runtime flags, privileged status, mounted paths, image digest and host patch level.
- Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
- Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
Explanation
Correct Answer
D:These observations investigate the exact Hypervisor resource overcommit and reservations failure rather than unrelated components. The expected technical relationship is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
Incorrect Answers
A:This is the unsafe shortcut in the Hypervisor resource overcommit and reservations scenario, not a justified remediation or diagnostic. Discriminate using: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
B:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
C:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This statement concerns Live migration compatibility and resource headroom, a different Server+ technical control.
Question 284
After the team implements a targeted remediation for Hypervisor resource overcommit and reservations, the original incident was: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Expired snapshots are consolidated safely and a separate tested backup can restore the VM.
- Authorized readers can read but cannot modify, and only approved writer groups can change files.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
- The VM retains approved network connectivity through migration without gaining unauthorized subnet reachability.
Explanation
Correct Answer
C:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. Incident: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic.
Incorrect Answers
A:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair.
B:This statement concerns File share authorization and inheritance, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
D:This statement concerns Virtual switch isolation and port group assignment, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Question 285
A change board is planning a verified response to this server event: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic. For the Hypervisor resource overcommit and reservations issue, which response elements belong in the approved plan? Select ONE best answer.
- Right-size vCPU and RAM allocations using contention telemetry and supportable reservations or resource controls. Then validate the change by confirming: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
- Increase every VM's configured vCPU and RAM without checking host contention.
- Inspect script condition checks, before/after configuration, test reruns and failure logs.
- Run containers with least privileges, limited mounts and capabilities, verified images and supported host hardening.
Explanation
Correct Answer
A:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This avoids the unsafe shortcut: Increase every VM's configured vCPU and RAM without checking host contention.
Incorrect Answers
B:This is the unsafe shortcut in the Hypervisor resource overcommit and reservations scenario, not a justified remediation or diagnostic. Incident: A virtualization host is allocated twice its physical memory across VMs and begins heavy ballooning and swapping during peak traffic.
C:That option would inspect script condition checks, before/after configuration, test reruns and failure logs, but it addresses a different concern. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
D:That option would run containers with least privileges, limited mounts and capabilities, verified images and supported host hardening, but it addresses a different concern. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
Question 286
A server administrator is investigating a server issue involving hypervisor resource overcommit and reservations: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
- Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
- Right-size vCPU and RAM allocations using contention telemetry and supportable reservations or resource controls.
- Increase every VM's configured vCPU and RAM without checking host contention.
Explanation
Correct Answer
C:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. For this case, A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
Incorrect Answers
A:This statement concerns Service dependency and restart management, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
B:That option would align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation, but it addresses a different concern. Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
D:This is the unsafe shortcut in the Hypervisor resource overcommit and reservations scenario, not a justified remediation or diagnostic. Incident: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
Question 287
While reviewing the CompTIA Server+ administration incident, a technician learns: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
- Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
- A transport-level open port may not prove application readiness, and graceful draining protects in-flight sessions.
- UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
Explanation
Correct Answer
B:The acceptance test is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Incorrect Answers
A:This statement concerns Service dependency and restart management, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair.
C:This statement concerns Load balancer health checking, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
D:This statement concerns UEFI boot and GPT provisioning, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Question 288
Before a server change is approved, the on-call engineer receives this incident report: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens. 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.
- Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
- Increase every VM's configured vCPU and RAM without checking host contention.
- Inspect container runtime flags, privileged status, mounted paths, image digest and host patch level.
Explanation
Correct Answer
B:These observations investigate the exact Hypervisor resource overcommit and reservations failure rather than unrelated components. Incident: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
Incorrect Answers
A:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. Incident: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
C:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
D:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This statement concerns Containers and host isolation, a different Server+ technical control.
Question 289
After the team implements a targeted remediation for Hypervisor resource overcommit and reservations, the original incident was: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Expired snapshots are consolidated safely and a separate tested backup can restore the VM.
- The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
- The VM retains approved network connectivity through migration without gaining unauthorized subnet reachability.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Explanation
Correct Answer
D:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. Incident: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
Incorrect Answers
A:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
B:This statement concerns UEFI boot and GPT provisioning, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair.
C:This statement concerns Virtual switch isolation and port group assignment, a different Server+ technical control. It does not directly address the reported Hypervisor resource overcommit and reservations fault or prove its repair. For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. A targeted investigation checks: Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves. The desired recovery condition is: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Question 290
A change board is planning a verified response to this server event: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens. For the Hypervisor resource overcommit and reservations issue, which response elements belong in the approved plan? Select TWO answers.
- The VM retains approved network connectivity through migration without gaining unauthorized subnet reachability.
- Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
- Right-size vCPU and RAM allocations using contention telemetry and supportable reservations or resource controls.
- Use application-aware health checks, appropriate rise/fall thresholds and connection draining for deployments.
- Increase every VM's configured vCPU and RAM without checking host contention.
Explanation
Correct Answer
B:These observations investigate the exact Hypervisor resource overcommit and reservations failure rather than unrelated components. Confirm remediation through: Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
C:Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This is the appropriate targeted correction for Hypervisor resource overcommit and reservations.
Incorrect Answers
A:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This statement concerns Virtual switch isolation and port group assignment, a different Server+ technical control.
D:For this incident, the relevant principle is: Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency. This statement concerns Load balancer health checking, a different Server+ technical control.
E:Incident: A latency-sensitive VM is given eight vCPUs on a busy host but its ready time increases and application response worsens.
