CompTIA SK0-005 Practice Test 15
Question 140
A change board is planning a verified response to this server event: A rack facility dismisses rising fan errors and battery warnings because the servers are still answering application health checks. For the Preventive hardware maintenance and spares issue, which response elements belong in the approved plan? Select TWO answers.
- Correlate sensor alarms, fault trends, part numbers, vendor lifecycle notices and support response agreements.
- Connect redundant PSUs to independently protected PDU and UPS paths where available; size each path to carry the required load.
- Use lifecycle and alert data to schedule preventive maintenance, stock qualified critical spares and document replacement runbooks.
- Wait for complete service outage before acting on persistent hardware health alarms.
- The component is replaced per approved procedure and POST or hardware diagnostics show normal health.
Explanation
Correct Answer
A:These observations investigate the exact Preventive hardware maintenance and spares failure rather than unrelated components. Use findings to decide whether to: Use lifecycle and alert data to schedule preventive maintenance, stock qualified critical spares and document replacement runbooks.
C:Before rollout, confirm the problem with: Correlate sensor alarms, fault trends, part numbers, vendor lifecycle notices and support response agreements. This is the appropriate targeted correction for Preventive hardware maintenance and spares.
Incorrect Answers
B:For this incident, the relevant principle is: Preventive maintenance reduces recoverable downtime by detecting degrading components and planning compatible replacements. It does not directly address the reported Preventive hardware maintenance and spares fault or prove its repair.
D:Incident: A rack facility dismisses rising fan errors and battery warnings because the servers are still answering application health checks.
E:For this incident, the relevant principle is: Preventive maintenance reduces recoverable downtime by detecting degrading components and planning compatible replacements. This statement concerns ESD and hot-swap replacement procedure, a different Server+ technical control.
Question 141
A server administrator is investigating a server issue involving uefi boot and gpt provisioning: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- Restrict PXE and imaging infrastructure to trusted networks and protect signed, versioned images and unattended-install credentials.
- Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
- Maintain supported, patched golden images with version pinning, vulnerability scanning and reproducible configuration validation.
Explanation
Correct Answer
C:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. For this case, A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries.
Incorrect Answers
A:This is the unsafe shortcut in the UEFI boot and GPT provisioning scenario, not a justified remediation or diagnostic. UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
B:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
D:That option would maintain supported, patched golden images with version pinning, vulnerability scanning and reproducible configuration validation, but it addresses a different concern. UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
Question 142
While reviewing the CompTIA Server+ administration incident, a technician learns: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Software rights depend on the actual product agreement and deployment topology; a paid license on one host is not always transferable.
- UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
- File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
- Availability must preserve data consistency during partitions; an extra node is not sufficient without quorum and fencing.
Explanation
Correct Answer
B:Applying it leads to this operational action: Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
Incorrect Answers
A:This statement concerns Per-core and virtual machine licensing, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
C:This statement concerns Partition and mount strategy for server roles, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
D:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Question 143
Before a server change is approved, the on-call engineer receives this incident report: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
- Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- Trace DHCP/PXE boot source, image hashes and signatures, access ACLs and answer-file permissions.
Explanation
Correct Answer
B:These observations investigate the exact UEFI boot and GPT provisioning failure rather than unrelated components. Incident: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries.
Incorrect Answers
A:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support.
C:This is the unsafe shortcut in the UEFI boot and GPT provisioning scenario, not a justified remediation or diagnostic. Incident: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries.
D:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. Incident: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries.
Question 144
After the team implements a targeted remediation for UEFI boot and GPT provisioning, the original incident was: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
- Newly deployed hosts match a supported baseline with documented provenance and no unapproved critical gaps.
- The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
- Offset falls within the authentication policy threshold and timestamps align across systems.
Explanation
Correct Answer
C:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. Incident: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries.
Incorrect Answers
A:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair.
B:This statement concerns Golden image lifecycle and OS support, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
D:This statement concerns NTP time sources and clock skew, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Question 145
A change board is planning a verified response to this server event: A deployment technician installs a modern server OS in legacy BIOS mode but the standardized fleet expects Secure Boot and UEFI boot entries. For the UEFI boot and GPT provisioning issue, which response elements belong in the approved plan? Select ONE best answer.
- Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation. Then validate the change by confirming: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring.
- Compare source/destination port-group IDs, uplink teaming, VLAN tags and effective firewall policies.
Explanation
Correct Answer
A:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. The proposed change and outcome assessment work together for UEFI boot and GPT provisioning.
Incorrect Answers
B:This is the unsafe shortcut in the UEFI boot and GPT provisioning scenario, not a justified remediation or diagnostic. Discriminate using: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support.
C:This statement concerns Partition and mount strategy for server roles, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair.
D:That option would compare source/destination port-group IDs, uplink teaming, VLAN tags and effective firewall policies, but it addresses a different concern. UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
Question 146
A server administrator is investigating a server issue involving uefi boot and gpt provisioning: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Update authoritative asset, dependency and change records at deployment and verify ownership and configuration links.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- 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.
Explanation
Correct Answer
C:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. For this case, A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
Incorrect Answers
A:That option would update authoritative asset, dependency and change records at deployment and verify ownership and configuration links, but it addresses a different concern. UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
B:This is the unsafe shortcut in the UEFI boot and GPT provisioning scenario, not a justified remediation or diagnostic. Incident: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
D:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Question 147
While reviewing the CompTIA Server+ administration incident, a technician learns: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout. 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.
- Accurate inventories and documented changes shorten incident response and support accountable operations.
- UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
Explanation
Correct Answer
D:Applying it leads to this operational action: Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
Incorrect Answers
A:This statement concerns Service dependency and restart management, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
B:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair.
C:This statement concerns Asset inventory and change records, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Question 148
Before a server change is approved, the on-call engineer receives this incident report: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- Trace DHCP/PXE boot source, image hashes and signatures, access ACLs and answer-file permissions.
- Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
- Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support.
Explanation
Correct Answer
D:These observations investigate the exact UEFI boot and GPT provisioning failure rather than unrelated components. Incident: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
Incorrect Answers
A:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
B:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. Incident: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
C:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. This statement concerns Service dependency and restart management, a different Server+ technical control.
Question 149
After the team implements a targeted remediation for UEFI boot and GPT provisioning, the original incident was: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Newly deployed hosts match a supported baseline with documented provenance and no unapproved critical gaps.
- Peak workload runs within latency targets without excessive CPU ready or host memory reclamation.
- Unready nodes receive no new requests, ready nodes join predictably and existing requests drain successfully.
- The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Explanation
Correct Answer
D:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. Incident: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
Incorrect Answers
A:This statement concerns Golden image lifecycle and OS support, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
B:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
C:This statement concerns Load balancer health checking, a different Server+ technical control. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair. For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. A targeted investigation checks: Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support. The desired recovery condition is: The OS boots consistently using the intended UEFI entry and approved partition scheme after reboot tests.
Question 150
A change board is planning a verified response to this server event: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout. For the UEFI boot and GPT provisioning issue, which response elements belong in the approved plan? Select TWO answers.
- Inspect boot mode, partition-table format, Secure Boot state, boot entries and installation media support.
- Toggle between legacy BIOS and UEFI at random after installation to make an incompatible bootloader work.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
- Newly deployed hosts match a supported baseline with documented provenance and no unapproved critical gaps.
- Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
Explanation
Correct Answer
A:These observations investigate the exact UEFI boot and GPT provisioning failure rather than unrelated components. The expected technical relationship is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
E:UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. This is the appropriate targeted correction for UEFI boot and GPT provisioning.
Incorrect Answers
B:Incident: A replacement boot disk exceeds the legacy MBR addressing design and the new operating system image cannot use the planned partition layout.
C:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. It does not directly address the reported UEFI boot and GPT provisioning fault or prove its repair.
D:For this incident, the relevant principle is: UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup. This statement concerns Golden image lifecycle and OS support, a different Server+ technical control.
