CompTIA SK0-005 Practice Test 71
Question 700
A change board is planning a verified response to this server event: An application repeatedly returns HTTP 500 after a library upgrade because a runtime dependency is missing. For the Application crash and dependency triage issue, which response elements belong in the approved plan? Select THREE answers.
- The application passes functional load tests without repeating its prior exceptions.
- Inspect console boot errors, UEFI order, boot partition, initramfs modules and prior working entries.
- Replace the physical server solely because an application endpoint returns HTTP 500.
- Record symptoms and recent changes, form a testable hypothesis, change one variable at a time and preserve rollback evidence.
- Correlate stack traces, error codes, database connection metrics, package versions and deployment history.
- Trace application errors, dependencies, configuration and resource metrics; restore a supported version or correct the actual limit.
Explanation
Correct Answer
A:Application-level failures can occur with healthy CPU, network and OS; examine logs and service dependencies before hardware replacement. This evidence tests whether the original Application crash and dependency triage weakness has been corrected under realistic conditions.
E:These observations investigate the exact Application crash and dependency triage failure rather than unrelated components. The expected technical relationship is: Application-level failures can occur with healthy CPU, network and OS; examine logs and service dependencies before hardware replacement.
F:Application-level failures can occur with healthy CPU, network and OS; examine logs and service dependencies before hardware replacement. A successful outcome is: The application passes functional load tests without repeating its prior exceptions.
Incorrect Answers
B:That option would inspect console boot errors, UEFI order, boot partition, initramfs modules and prior working entries, but it addresses a different concern. Application-level failures can occur with healthy CPU, network and OS; examine logs and service dependencies before hardware replacement.
C:Incident: An application repeatedly returns HTTP 500 after a library upgrade because a runtime dependency is missing.
D:That option would record symptoms and recent changes, form a testable hypothesis, change one variable at a time and preserve rollback evidence, but it addresses a different concern. Application-level failures can occur with healthy CPU, network and OS; examine logs and service dependencies before hardware replacement.
Question 701
A server administrator is investigating a server issue involving os patch regression and rollback: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Disable all future security updates because one change was incompatible.
- Trace application errors, dependencies, configuration and resource metrics; restore a supported version or correct the actual limit.
- Compare changed package and driver versions, confirm a supported regression and execute an approved rollback or fixed update.
- Restore the supported boot entry or known-good kernel and rebuild boot images as needed using tested recovery media.
Explanation
Correct Answer
C:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. For this case, A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable.
Incorrect Answers
A:This is the unsafe shortcut in the OS patch regression and rollback scenario, not a justified remediation or diagnostic. A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
B:That option would trace application errors, dependencies, configuration and resource metrics; restore a supported version or correct the actual limit, but it addresses a different concern. A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
D:This statement concerns Boot loader and failed update recovery, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 702
While reviewing the CompTIA Server+ administration incident, a technician learns: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Guest CPU and memory counters alone can mask hypervisor scheduling delay and host swapping.
- Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
- Correctable memory errors are early-warning evidence; a rising count can precede uncorrectable failures.
- A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
Explanation
Correct Answer
D:Collect evidence first: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
Incorrect Answers
A:This statement concerns Hypervisor contention causing guest latency, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
B:This statement concerns Write cache battery and storage performance, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
C:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 703
Before a server change is approved, the on-call engineer receives this incident report: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Compare CPU ready, host memory reclaim, NUMA locality, datastore latency and workload peaks.
- Disable all future security updates because one change was incompatible.
- Inspect console boot errors, UEFI order, boot partition, initramfs modules and prior working entries.
- Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
Explanation
Correct Answer
D:These observations investigate the exact OS patch regression and rollback failure rather than unrelated components. Incident: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable.
Incorrect Answers
A:For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
B:This is the unsafe shortcut in the OS patch regression and rollback scenario, not a justified remediation or diagnostic. Discriminate using: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
C:For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
Question 704
After the team implements a targeted remediation for OS patch regression and rollback, the original incident was: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Hardware reports no recurring ECC faults and memory validation passes under representative load.
- The array returns to a healthy redundant state with error-free checks and a verified recovery copy.
- The fault disappears under an approved version with no unrelated security controls disabled.
- The application passes functional load tests without repeating its prior exceptions.
Explanation
Correct Answer
C:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. Incident: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable.
Incorrect Answers
A:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair.
B:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
D:This statement concerns Application crash and dependency triage, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 705
A change board is planning a verified response to this server event: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable. For the OS patch regression and rollback issue, which response elements belong in the approved plan? Select ONE best answer.
- Use host and guest metrics to identify hypervisor resource contention, then right-size or rebalance allocations.
- Disable all future security updates because one change was incompatible.
- Compare changed package and driver versions, confirm a supported regression and execute an approved rollback or fixed update. Then validate the change by confirming: The fault disappears under an approved version with no unrelated security controls disabled.
- Capture baseline symptoms, timeline, recent changes, comparison hosts and test results before modifying production.
Explanation
Correct Answer
C:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. Before modifying systems, gather: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
Incorrect Answers
A:That option would use host and guest metrics to identify hypervisor resource contention, then right-size or rebalance allocations, but it addresses a different concern. A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
B:This is the unsafe shortcut in the OS patch regression and rollback scenario, not a justified remediation or diagnostic. Incident: A host starts dropping VPN sessions after a new network-driver package, while otherwise identical unpatched hosts remain stable.
D:This statement concerns Structured troubleshooting hypothesis and controlled change, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 706
A server administrator is investigating a server issue involving os patch regression and rollback: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Inspect cooling path, heatsink mounting and sensor telemetry, then correct the thermal fault before increasing load.
- Disable all future security updates because one change was incompatible.
- Compare changed package and driver versions, confirm a supported regression and execute an approved rollback or fixed update.
- Back up critical data, inspect controller/media events, replace failed components and rebuild with monitored redundancy.
Explanation
Correct Answer
C:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. For this case, A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin.
Incorrect Answers
A:That option would inspect cooling path, heatsink mounting and sensor telemetry, then correct the thermal fault before increasing load, but it addresses a different concern. A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
B:This is the unsafe shortcut in the OS patch regression and rollback scenario, not a justified remediation or diagnostic. Incident: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin.
D:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 707
While reviewing the CompTIA Server+ administration incident, a technician learns: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
- Repeated authentication failures across accounts require identity threat response and management-plane restriction, not weakened lockout controls.
- Thermal throttling and protective shutdown may result from heat transfer or airflow faults even without high average CPU use.
- Degraded or unstable storage may be one additional fault from data loss; immediate integrity and rebuild priorities matter.
Explanation
Correct Answer
A:Collect evidence first: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
Incorrect Answers
B:This statement concerns Brute-force authentication and account lockout, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
C:This statement concerns Thermal shutdown and heatsink diagnostics, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
D:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair.
Question 708
Before a server change is approved, the on-call engineer receives this incident report: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Disable all future security updates because one change was incompatible.
- Correlate stack traces, error codes, database connection metrics, package versions and deployment history.
- Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
- Inspect source IP patterns, failed/successful sign-ins, privileged access rules and MFA challenges.
Explanation
Correct Answer
C:These observations investigate the exact OS patch regression and rollback failure rather than unrelated components. Incident: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin.
Incorrect Answers
A:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
B:For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
D:For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. This statement concerns Brute-force authentication and account lockout, a different Server+ technical control.
Question 709
After the team implements a targeted remediation for OS patch regression and rollback, the original incident was: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- The fault disappears under an approved version with no unrelated security controls disabled.
- The array returns to a healthy redundant state with error-free checks and a verified recovery copy.
- Clients obtain unique approved addresses and correct gateways without duplicate-IP warnings.
- The host boots the approved OS reliably through several cold boots with disk access intact.
Explanation
Correct Answer
A:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. Incident: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin.
Incorrect Answers
B:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
C:This statement concerns DHCP and IP address conflict isolation, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
D:This statement concerns Boot loader and failed update recovery, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair. For this incident, the relevant principle is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. A targeted investigation checks: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests. The desired recovery condition is: The fault disappears under an approved version with no unrelated security controls disabled.
Question 710
A change board is planning a verified response to this server event: A critical service fails immediately after an OS cumulative update changes a system library and breaks a vendor plugin. For the OS patch regression and rollback issue, which response elements belong in the approved plan? Select TWO answers.
- Disable all future security updates because one change was incompatible.
- Restrict management exposure, enforce MFA and rate limiting and investigate authentication events and compromised credentials.
- Compare changed package and driver versions, confirm a supported regression and execute an approved rollback or fixed update.
- Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
- The host boots the approved OS reliably through several cold boots with disk access intact.
Explanation
Correct Answer
C:A close timeline between change and failure is a hypothesis to test, not automatic proof of cause. Before rollout, confirm the problem with: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
D:These observations investigate the exact OS patch regression and rollback failure rather than unrelated components. The expected technical relationship is: A close timeline between change and failure is a hypothesis to test, not automatic proof of cause.
Incorrect Answers
A:Discriminate using: Inspect change records, kernel and driver logs, known advisories and control-host comparison tests.
B:This statement concerns Brute-force authentication and account lockout, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair.
E:This statement concerns Boot loader and failed update recovery, a different Server+ technical control. It does not directly address the reported OS patch regression and rollback fault or prove its repair.
