CompTIA SK0-005 Practice Test 33
Question 320
A change board is planning a verified response to this server event: A server team assumes a container image automatically provides kernel-level isolation from a vulnerable shared host. For the Containers and host isolation issue, which response elements belong in the approved plan? Select TWO answers.
- Expired snapshots are consolidated safely and a separate tested backup can restore the VM.
- Inspect container runtime flags, privileged status, mounted paths, image digest and host patch level.
- Configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset.
- Run containers with least privileges, limited mounts and capabilities, verified images and supported host hardening.
- Use --privileged and mount the host root filesystem to fix a narrow file permission error.
Explanation
Correct Answer
B:The expected technical relationship is: Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization. Confirm remediation through: The workload performs its required task without unnecessary host capabilities or filesystem access.
D:Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization.
Incorrect Answers
A:For this incident, the relevant principle is: Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization. This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control.
C:For this incident, the relevant principle is: Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization. The desired recovery condition is: The workload performs its required task without unnecessary host capabilities or filesystem access.
E:Discriminate using: Inspect container runtime flags, privileged status, mounted paths, image digest and host patch level.
Question 321
A server administrator is investigating a server issue involving live migration compatibility and resource headroom: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline. 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.
- Schedule migration based only on the destination host's power-on status.
Explanation
Correct Answer
B:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. For this case, A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline.
Incorrect Answers
A:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
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. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
D:This is the unsafe shortcut in the Live migration compatibility and resource headroom scenario, not a justified remediation or diagnostic. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Question 322
While reviewing the CompTIA Server+ administration incident, a technician learns: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline. 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.
- Software rights depend on the actual product agreement and deployment topology; a paid license on one host is not always transferable.
- Containers share a host kernel and depend on namespace, capability, filesystem and image security; they are not full hardware virtualization.
- Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Explanation
Correct Answer
D:The acceptance test is: The VM migrates without guest interruption and maintains its workload performance after placement.
Incorrect Answers
A:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
B:This statement concerns Per-core and virtual machine licensing, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
C:This statement concerns Containers and host isolation, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
Question 323
Before a server change is approved, the on-call engineer receives this incident report: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
- Inspect snapshot tree age/size, delta growth, datastore free space and backup restore-point availability.
- Compare source/destination port-group IDs, uplink teaming, VLAN tags and effective firewall policies.
- Schedule migration based only on the destination host's power-on status.
Explanation
Correct Answer
A:These observations investigate the exact Live migration compatibility and resource headroom failure rather than unrelated components. Incident: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline.
Incorrect Answers
B:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
C:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. Incident: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline.
D:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This is the unsafe shortcut in the Live migration compatibility and resource headroom scenario, not a justified remediation or diagnostic.
Question 324
After the team implements a targeted remediation for Live migration compatibility and resource headroom, the original incident was: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- The VM migrates without guest interruption and maintains its workload performance after placement.
- Inventory and dependency records match deployed assets and can be used to locate each service during incidents.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
- The workload performs its required task without unnecessary host capabilities or filesystem access.
Explanation
Correct Answer
A:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. Incident: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline.
Incorrect Answers
B:This statement concerns Asset inventory and change records, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
C:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair.
D:This statement concerns Containers and host isolation, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair.
Question 325
A change board is planning a verified response to this server event: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline. For the Live migration compatibility and resource headroom issue, which response elements belong in the approved plan? Select ONE best answer.
- Verify migration CPU compatibility, shared/storage accessibility and destination resource headroom before moving VMs. Then validate the change by confirming: The VM migrates without guest interruption and maintains its workload performance after placement.
- Schedule migration based only on the destination host's power-on status.
- Use snapshots only as short-lived change rollback points and maintain independently recoverable, application-consistent backups.
- Inspect script condition checks, before/after configuration, test reruns and failure logs.
Explanation
Correct Answer
A:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This avoids the unsafe shortcut: Schedule migration based only on the destination host's power-on status.
Incorrect Answers
B:This is the unsafe shortcut in the Live migration compatibility and resource headroom scenario, not a justified remediation or diagnostic. Incident: A VM migration fails because the destination cluster uses a CPU feature set unsupported by the source compatibility baseline.
C:That option would use snapshots only as short-lived change rollback points and maintain independently recoverable, application-consistent backups, but it addresses a different concern. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
D:That option would inspect script condition checks, before/after configuration, test reruns and failure logs, but it addresses a different concern. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Question 326
A server administrator is investigating a server issue involving live migration compatibility and resource headroom: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Verify migration CPU compatibility, shared/storage accessibility and destination resource headroom before moving VMs.
- Schedule migration based only on the destination host's power-on status.
- Configure nonoverlapping DHCP scopes, appropriate relay or helper settings and correct lease, gateway and DNS options.
- Configure an appropriate witness and quorum voting model with fencing or leader election to avoid simultaneous primaries.
Explanation
Correct Answer
A:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A successful outcome is: The VM migrates without guest interruption and maintains its workload performance after placement.
Incorrect Answers
B:This is the unsafe shortcut in the Live migration compatibility and resource headroom scenario, not a justified remediation or diagnostic. Discriminate using: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
C:That option would configure nonoverlapping DHCP scopes, appropriate relay or helper settings and correct lease, gateway and DNS options, but it addresses a different concern. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
D: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. Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Question 327
While reviewing the CompTIA Server+ administration incident, a technician learns: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- DHCP broadcasts normally need a relay across routed subnets, and leases must match the client network and scope policy.
- Reliable administration scripts should be safe to rerun after partial execution rather than multiply state changes.
- Availability must preserve data consistency during partitions; an extra node is not sufficient without quorum and fencing.
- Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Explanation
Correct Answer
D:The acceptance test is: The VM migrates without guest interruption and maintains its workload performance after placement. This is the controlling principle for the reported Live migration compatibility and resource headroom incident.
Incorrect Answers
A:This statement concerns DHCP scope and relay design, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
B:This statement concerns Idempotent configuration automation, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
C:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
Question 328
Before a server change is approved, the on-call engineer receives this incident report: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Schedule migration based only on the destination host's power-on status.
- Compare source/destination port-group IDs, uplink teaming, VLAN tags and effective firewall policies.
- Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
- Inspect script condition checks, before/after configuration, test reruns and failure logs.
Explanation
Correct Answer
C:These observations investigate the exact Live migration compatibility and resource headroom failure rather than unrelated components. The expected technical relationship is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged.
Incorrect Answers
A:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. Discriminate using: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
B:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This statement concerns Virtual switch isolation and port group assignment, a different Server+ technical control.
D:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This statement concerns Idempotent configuration automation, a different Server+ technical control.
Question 329
After the team implements a targeted remediation for Live migration compatibility and resource headroom, the original incident was: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival. 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.
- During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
- The VM migrates without guest interruption and maintains its workload performance after placement.
Explanation
Correct Answer
D:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. Incident: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival.
Incorrect Answers
A:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
B:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair.
C:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported Live migration compatibility and resource headroom fault or prove its repair. For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. A targeted investigation checks: Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
Question 330
A change board is planning a verified response to this server event: An administrator live-migrates a heavy VM to a host with insufficient memory headroom, triggering severe ballooning after arrival. For the Live migration compatibility and resource headroom issue, which response elements belong in the approved plan? Select TWO answers.
- Implement desired-state checks and idempotent updates with logs and bounded retries so repeated runs converge.
- Schedule migration based only on the destination host's power-on status.
- Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
- Verify migration CPU compatibility, shared/storage accessibility and destination resource headroom before moving VMs.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
Explanation
Correct Answer
C:These observations investigate the exact Live migration compatibility and resource headroom failure rather than unrelated components. Confirm remediation through: The VM migrates without guest interruption and maintains its workload performance after placement.
D:Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This is the appropriate targeted correction for Live migration compatibility and resource headroom.
Incorrect Answers
A:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. The desired recovery condition is: The VM migrates without guest interruption and maintains its workload performance after placement.
B:This is the unsafe shortcut in the Live migration compatibility and resource headroom scenario, not a justified remediation or diagnostic.
E:For this incident, the relevant principle is: Live migration depends on compatible host features and enough resources on the target, even if the guest OS is unchanged. This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control.
