CompTIA SK0-005 Practice Test 24
Question 230
A change board is planning a verified response to this server event: A Linux NFS export unintentionally permits write access from a wider subnet than intended after a filesystem group change. For the File share authorization and inheritance issue, which response elements belong in the approved plan? Select TWO answers.
- All required services start in order after reboot and pass application-level health checks.
- Use test identities to review effective ACLs, inheritance, export host restrictions and access audit events.
- Configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset.
- Grant Everyone full control at each layer to work around an access complaint.
- Align share/export permissions with filesystem ACLs, least-privilege group membership and documented inheritance tests.
Explanation
Correct Answer
B:These observations investigate the exact File share authorization and inheritance failure rather than unrelated components. Incident: A Linux NFS export unintentionally permits write access from a wider subnet than intended after a filesystem group change.
E:A successful outcome is: Authorized readers can read but cannot modify, and only approved writer groups can change files. This is the appropriate targeted correction for File share authorization and inheritance.
Incorrect Answers
A:For this incident, the relevant principle is: Effective file access results from intersecting share/export rules, filesystem permissions and identity context. This statement concerns Service dependency and restart management, a different Server+ technical control.
C:For this incident, the relevant principle is: Effective file access results from intersecting share/export rules, filesystem permissions and identity context.
D:Discriminate using: Use test identities to review effective ACLs, inheritance, export host restrictions and access audit events.
Question 231
A server administrator is investigating a server issue involving service dependency and restart management: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Align share/export permissions with filesystem ACLs, least-privilege group membership and documented inheritance tests.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
- Baseline CPU, memory, IOPS, network and latency against workload SLOs; adjust constrained capacity using measured evidence.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
Explanation
Correct Answer
B:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Incorrect Answers
A:That option would align share/export permissions with filesystem ACLs, least-privilege group membership and documented inheritance tests, but it addresses a different concern. A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
C:This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
D:This is the unsafe shortcut in the Service dependency and restart management scenario, not a justified remediation or diagnostic. A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Question 232
While reviewing the CompTIA Server+ administration incident, a technician learns: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first. 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.
- Virtual network topology must be consistent across hosts, and hypervisor port groups enforce connectivity and isolation.
- A standby's existence does not prove recoverability; replication lag, failover automation and consistency determine outcomes.
- A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Explanation
Correct Answer
D:Applying it leads to this operational action: Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts. The acceptance test is: All required services start in order after reboot and pass application-level health checks.
Incorrect Answers
A:This statement concerns Idempotent configuration automation, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
B:This statement concerns Virtual switch isolation and port group assignment, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
C:This statement concerns Database replication and failover objective, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
Question 233
Before a server change is approved, the on-call engineer receives this incident report: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
- Measure apply lag, replication errors, client reconnection behavior and failover event timestamps.
- Collect resource counters, queue depth, latency percentile, working-set and workload time series.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
Explanation
Correct Answer
A:These observations investigate the exact Service dependency and restart management failure rather than unrelated components. Incident: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first.
Incorrect Answers
B:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
C:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
D:This is the unsafe shortcut in the Service dependency and restart management scenario, not a justified remediation or diagnostic. Incident: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first.
Question 234
After the team implements a targeted remediation for Service dependency and restart management, the original incident was: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Offset falls within the authentication policy threshold and timestamps align across systems.
- Running the automation twice produces the same intended end state without duplicate objects.
- All required services start in order after reboot and pass application-level health checks.
- Authorized readers can read but cannot modify, and only approved writer groups can change files.
Explanation
Correct Answer
C:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Incorrect Answers
A:This statement concerns NTP time sources and clock skew, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
B:This statement concerns Idempotent configuration automation, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair.
D:This statement concerns File share authorization and inheritance, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
Question 235
A change board is planning a verified response to this server event: A billing application fails after reboot because its database service is configured for manual startup and dependent services start first. For the Service dependency and restart management issue, which response elements belong in the approved plan? Select ONE best answer.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts. Then validate the change by confirming: All required services start in order after reboot and pass application-level health checks.
- Define supported sync/async replication and failover mechanisms consistent with RPO/RTO; test role promotion and endpoint switching.
- Inspect switch port VLAN/trunk state, ARP tables, interface settings, routing table and path traces.
Explanation
Correct Answer
B:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. This avoids the unsafe shortcut: Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
Incorrect Answers
A:This is the unsafe shortcut in the Service dependency and restart management scenario, not a justified remediation or diagnostic. Discriminate using: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
C:That option would define supported sync/async replication and failover mechanisms consistent with RPO/RTO; test role promotion and endpoint switching, but it addresses a different concern. A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
D:That option would inspect switch port VLAN/trunk state, ARP tables, interface settings, routing table and path traces, but it addresses a different concern. A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Question 236
A server administrator is investigating a server issue involving service dependency and restart management: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
- Restrict PXE and imaging infrastructure to trusted networks and protect signed, versioned images and unattended-install credentials.
Explanation
Correct Answer
B:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Incorrect Answers
A:That option would configure redundant trusted time sources and verify host, hypervisor and directory time hierarchy with monitored offset, but it addresses a different concern. A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
C:This is the unsafe shortcut in the Service dependency and restart management scenario, not a justified remediation or diagnostic. Incident: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies.
D:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
Question 237
While reviewing the CompTIA Server+ administration incident, a technician learns: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Network boot is a high-trust supply chain; authenticated image provenance and secret protection matter as much as automation speed.
- A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
- Time synchronization is required for trustworthy logs, certificate validation windows and time-sensitive authentication.
- Allocated virtual resources are not guaranteed physically available under contention; vCPU ready and memory reclaim can harm latency.
Explanation
Correct Answer
B:Applying it leads to this operational action: Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
Incorrect Answers
A:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair.
C:This statement concerns NTP time sources and clock skew, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
D:This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
Question 238
Before a server change is approved, the on-call engineer receives this incident report: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Review cluster vote configuration, witness reachability, fencing logs and simulated partition behavior.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
- Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
- Inspect host CPU utilization and ready time, balloon/swap counters, NUMA placement and VM performance curves.
Explanation
Correct Answer
C:These observations investigate the exact Service dependency and restart management failure rather than unrelated components. Incident: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies.
Incorrect Answers
A:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
B:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
D:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. This statement concerns Hypervisor resource overcommit and reservations, a different Server+ technical control.
Question 239
After the team implements a targeted remediation for Service dependency and restart management, the original incident was: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Target latency and throughput hold under representative peak load with monitored headroom.
- All required services start in order after reboot and pass application-level health checks.
- A fresh node installs the approved version reproducibly without credential disclosure or rogue boot sources.
- Inventory and dependency records match deployed assets and can be used to locate each service during incidents.
Explanation
Correct Answer
B:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
Incorrect Answers
A:This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
C:This statement concerns PXE and unattended installation integrity, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
D:This statement concerns Asset inventory and change records, a different Server+ technical control. It does not directly address the reported Service dependency and restart management fault or prove its repair. For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A targeted investigation checks: Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
Question 240
A change board is planning a verified response to this server event: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies. For the Service dependency and restart management issue, which response elements belong in the approved plan? Select TWO answers.
- Target latency and throughput hold under representative peak load with monitored headroom.
- Configure every service to restart infinitely without investigating failed dependencies or resource exhaustion.
- Inspect service manager status, dependency graph, journal or event logs and memory/CPU pressure during startup.
- Correct service startup ordering and resource limits, monitor dependency health and validate controlled restarts.
- Right-size vCPU and RAM allocations using contention telemetry and supportable reservations or resource controls.
Explanation
Correct Answer
C:These observations investigate the exact Service dependency and restart management failure rather than unrelated components. The expected technical relationship is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured.
D:A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. A successful outcome is: All required services start in order after reboot and pass application-level health checks.
Incorrect Answers
A:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. This statement concerns Server resource monitoring and capacity planning, a different Server+ technical control.
B:Incident: A middleware daemon is repeatedly killed by memory pressure, and operators only reboot the host without inspecting service dependencies.
E:For this incident, the relevant principle is: A running OS is not evidence that dependent services, resource budgets and health checks are correctly configured. The desired recovery condition is: All required services start in order after reboot and pass application-level health checks.
