CompTIA SK0-005 Practice Test 17
Question 160
A change board is planning a verified response to this server event: An enterprise deploys 50 hosts from a network image but credentials and unattended-install secrets are embedded in a world-readable answer file. For the PXE and unattended installation integrity issue, which response elements belong in the approved plan? Select TWO answers.
- Trace DHCP/PXE boot source, image hashes and signatures, access ACLs and answer-file permissions.
- Restrict PXE and imaging infrastructure to trusted networks and protect signed, versioned images and unattended-install credentials.
- Use any responding PXE image server and store administrative passwords in public install scripts.
- Newly deployed hosts match a supported baseline with documented provenance and no unapproved critical gaps.
- Use snapshots only as short-lived change rollback points and maintain independently recoverable, application-consistent backups.
Explanation
Correct Answer
A:These observations investigate the exact PXE and unattended installation integrity failure rather than unrelated components. The expected technical relationship is: Network boot is a high-trust supply chain; authenticated image provenance and secret protection matter as much as automation speed.
B:A successful outcome is: A fresh node installs the approved version reproducibly without credential disclosure or rogue boot sources. This is the appropriate targeted correction for PXE and unattended installation integrity.
Incorrect Answers
C:Network boot is a high-trust supply chain; authenticated image provenance and secret protection matter as much as automation speed.
D:A targeted investigation checks: Trace DHCP/PXE boot source, image hashes and signatures, access ACLs and answer-file permissions.
E:This statement concerns VM snapshot use and backup boundaries, a different Server+ technical control.
Question 161
A server administrator is investigating a server issue involving partition and mount strategy for server roles: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
- Restrict PXE and imaging infrastructure to trusted networks and protect signed, versioned images and unattended-install credentials.
- Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring.
- Maintain supported, patched golden images with version pinning, vulnerability scanning and reproducible configuration validation.
Explanation
Correct Answer
C:Before rollout, confirm the problem with: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
Incorrect Answers
A:This is the unsafe shortcut in the Partition and mount strategy for server roles scenario, not a justified remediation or diagnostic. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
B:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
D:That option would maintain supported, patched golden images with version pinning, vulnerability scanning and reproducible configuration validation, but it addresses a different concern. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Question 162
While reviewing the CompTIA Server+ administration incident, a technician learns: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- UEFI, GPT and the installed bootloader must match a supported boot path; changing boot mode after installation can prevent startup.
- Software rights depend on the actual product agreement and deployment topology; a paid license on one host is not always transferable.
- File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
- Effective file access results from intersecting share/export rules, filesystem permissions and identity context.
Explanation
Correct Answer
C:This is the controlling principle for the reported Partition and mount strategy for server roles incident. Scenario: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed.
Incorrect Answers
A:This statement concerns UEFI boot and GPT provisioning, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
B:This statement concerns Per-core and virtual machine licensing, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
D:This statement concerns File share authorization and inheritance, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
Question 163
Before a server change is approved, the on-call engineer receives this incident report: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Compare OS vendor support dates, package inventory, image build ID and scan findings against the approved baseline.
- 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.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
Explanation
Correct Answer
B:These observations investigate the exact Partition and mount strategy for server roles failure rather than unrelated components. Incident: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed.
Incorrect Answers
A:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
C:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
D:Instead, the supported correction is: Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring. This is the unsafe shortcut in the Partition and mount strategy for server roles scenario, not a justified remediation or diagnostic.
Question 164
After the team implements a targeted remediation for Partition and mount strategy for server roles, the original incident was: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Authorized readers can read but cannot modify, and only approved writer groups can change files.
- Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
- During a planned partition only one side accepts authoritative writes and recovery avoids divergent state.
- A fresh node installs the approved version reproducibly without credential disclosure or rogue boot sources.
Explanation
Correct Answer
B:File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Incorrect Answers
A:This statement concerns File share authorization and inheritance, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair.
C:This statement concerns Cluster quorum and split-brain prevention, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
D:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair.
Question 165
A change board is planning a verified response to this server event: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed. For the Partition and mount strategy for server roles issue, which response elements belong in the approved plan? Select ONE best answer.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
- Review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity.
- Align firmware boot mode, supported GPT partitioning and Secure Boot policy with the OS image before installation.
- Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring. Then validate the change by confirming: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
Explanation
Correct Answer
D:This avoids the unsafe shortcut: Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
Incorrect Answers
A:This is the unsafe shortcut in the Partition and mount strategy for server roles scenario, not a justified remediation or diagnostic. Incident: A log-heavy service writes to the OS root partition until the boot volume fills and system updates cannot proceed.
B:That option would review EVC/CPU compatibility, datastore visibility, network mapping and free host capacity, but it addresses a different concern. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
C: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. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Question 166
A server administrator is investigating a server issue involving partition and mount strategy for server roles: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Baseline CPU, memory, IOPS, network and latency against workload SLOs; adjust constrained capacity using measured evidence.
- Use approved secret storage, minimize secret exposure and validate command errors with audit-friendly failure handling.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
- Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring.
Explanation
Correct Answer
D:Before rollout, confirm the problem with: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Incorrect Answers
A:This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
B:That option would use approved secret storage, minimize secret exposure and validate command errors with audit-friendly failure handling, but it addresses a different concern. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
C:This is the unsafe shortcut in the Partition and mount strategy for server roles scenario, not a justified remediation or diagnostic. Discriminate using: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
Question 167
While reviewing the CompTIA Server+ administration incident, a technician learns: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Reliable administration scripts should be safe to rerun after partial execution rather than multiply state changes.
- File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
- Capacity planning must identify the bottleneck resource and trend, not confuse free capacity with sufficient throughput.
- Automated commands must protect credentials and report failures accurately; output success is not evidence of task completion.
Explanation
Correct Answer
B:This is the controlling principle for the reported Partition and mount strategy for server roles incident. Applying it leads to this operational action: Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring.
Incorrect Answers
A:This statement concerns Idempotent configuration automation, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
C:This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair.
D:This statement concerns Script secret handling and exit-code validation, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
Question 168
Before a server change is approved, the on-call engineer receives this incident report: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan. 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.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
- Compare OS vendor support dates, package inventory, image build ID and scan findings against the approved baseline.
- Inspect script condition checks, before/after configuration, test reruns and failure logs.
Explanation
Correct Answer
A:These observations investigate the exact Partition and mount strategy for server roles failure rather than unrelated components. The expected technical relationship is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Incorrect Answers
B:Instead, the supported correction is: Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring. File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
C:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. This statement concerns Golden image lifecycle and OS support, a different Server+ technical control.
D:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. This statement concerns Idempotent configuration automation, a different Server+ technical control.
Question 169
After the team implements a targeted remediation for Partition and mount strategy for server roles, the original incident was: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- A fresh node installs the approved version reproducibly without credential disclosure or rogue boot sources.
- Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
- Target latency and throughput hold under representative peak load with monitored headroom.
- Deployments have traceable licenses and required notices or source obligations are fulfilled.
Explanation
Correct Answer
B:File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
Incorrect Answers
A:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
C:This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults.
D:This statement concerns Open-source license obligations and audit, a different Server+ technical control. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair. For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. A targeted investigation checks: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. The desired recovery condition is: Log growth no longer fills system volumes and data mounts have tested capacity thresholds and recovery procedures.
Question 170
A change board is planning a verified response to this server event: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan. For the Partition and mount strategy for server roles issue, which response elements belong in the approved plan? Select TWO answers.
- A fresh node installs the approved version reproducibly without credential disclosure or rogue boot sources.
- Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
- Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring.
- Leave unlimited application logs on the OS boot volume because unused disk exists elsewhere.
- Implement desired-state checks and idempotent updates with logs and bounded retries so repeated runs converge.
Explanation
Correct Answer
B:These observations investigate the exact Partition and mount strategy for server roles failure rather than unrelated components. Incident: A database server stores application data, temporary files and backups together on a single undersized filesystem with no growth plan.
C:Before rollout, confirm the problem with: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths. This is the appropriate targeted correction for Partition and mount strategy for server roles.
Incorrect Answers
A:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. This statement concerns PXE and unattended installation integrity, a different Server+ technical control.
D:Instead, the supported correction is: Separate high-growth data and logs from critical system space using supported mount points, volume sizing and monitoring. Discriminate using: Inspect filesystem usage by mount, expected data/log growth, backup layout and application storage paths.
E:For this incident, the relevant principle is: File-system layout should reflect workload growth and recovery boundaries rather than only installer defaults. It does not directly address the reported Partition and mount strategy for server roles fault or prove its repair.
