CompTIA XK0-006 Practice Test 57
Question 560
While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
Explanation
Correct Answer
B:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This action corrects systemd enable versus start without substituting an unrelated change. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Before acting, verify: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Afterward confirm: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This is a change associated with slo burn-rate alert selection, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This is a change associated with rootless podman bind mount access, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 561
During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?
- Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
- Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
Explanation
Correct Answer
A:Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. This action corrects python dependency lock reproducibility without substituting an unrelated change. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Before acting, verify: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. Afterward confirm: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
Incorrect Answers
B:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
C:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
D:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
Question 562
During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry.
Explanation
Correct Answers
A:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This supplies the decisive diagnostic observation for the stated fault. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Pair this evidence with the targeted change: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
B:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is the targeted change needed after establishing the fault. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Pair it with the supporting check: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
C:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
D:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This choice concerns xfs online filesystem growth rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
E:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This choice concerns one-time versus recurring scheduling rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
Question 563
During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
Explanation
Correct Answers
D:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This supplies the decisive diagnostic observation for the stated fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair this evidence with the targeted change: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
E:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is the targeted change needed after establishing the fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair it with the supporting check: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This choice concerns snmp polling versus traps rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
B:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This choice concerns mfa for administrative shell entry rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
C:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This choice concerns bonded nic failover detection rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
Question 564
While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Create a project virtual environment and install pinned project requirements into that isolated environment.
Explanation
Correct Answer
B:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This action corrects distribution package dependency resolution without substituting an unrelated change. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Before acting, verify: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Afterward confirm: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This is a change associated with ai-generated shell command validation, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is a change associated with process scheduling priority adjustment, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Create a project virtual environment and install pinned project requirements into that isolated environment. This is a change associated with python application isolation from os packages, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 565
During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Use the absolute executable path or set a minimal explicit safe
PATH for the scheduled job rather than relying on a login profile. - Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
- Correct the mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a. - Inspect boot journal and
systemctl --failed for the mount unit plus fstab options and network reachability.
Explanation
Correct Answers
D:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This is the targeted change needed after establishing the fault. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Pair it with the supporting check: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This supplies the decisive diagnostic observation for the stated fault. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Pair this evidence with the targeted change: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This choice concerns path in noninteractive jobs rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This choice concerns slo burn-rate alert selection rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
C:Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
Question 566
While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
- A test privileged command produces an attributable event with acting user, command, time and success or failure.
- The task executes once at the planned time and is absent from subsequent recurring schedules.
- Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct.
Explanation
Correct Answer
C:The task executes once at the planned time and is absent from subsequent recurring schedules. This is direct acceptance evidence for one-time versus recurring scheduling rather than a generic process check. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. It validates the correction: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The process exits normally, committed work persists, and no crash-recovery warning appears on restart. This outcome would support graceful process shutdown signal, but does not establish that the reported one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
B:A test privileged command produces an attributable event with acting user, command, time and success or failure. This outcome would support sudo action auditing, but does not establish that the reported one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
D:Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. This outcome would support atomic file replacement and ownership, but does not establish that the reported one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
Question 567
During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list. - Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Inspect
getfacl, directory mode, ACL mask and the required group principals.
Explanation
Correct Answer
D:Inspect getfacl, directory mode, ACL mask and the required group principals. This checks the mechanism behind posix acl restrictive shared directory. ACLs extend permissions to named users/groups without granting access to every user on the host. Once identified, the targeted correction is: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Confirm by checking: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This can investigate default home-directory skeleton, but the given incident points to posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
C:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This can investigate pam password history policy, but the given incident points to posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Question 568
During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
- A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.
apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin.- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This is direct acceptance evidence for persistent networkmanager static address rather than a generic process check. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. It validates the correction: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, but does not establish that the reported persistent networkmanager static address problem is resolved. The required direct acceptance test is: The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
B:A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This outcome would support text filtering with grep and awk, but does not establish that the reported persistent networkmanager static address problem is resolved. The required direct acceptance test is: The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
C:apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. This outcome would support apt package origin pinning, but does not establish that the reported persistent networkmanager static address problem is resolved. The required direct acceptance test is: The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Question 569
During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
- Inspect
vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. - Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements.
Explanation
Correct Answer
C:Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This checks the mechanism behind swapping-induced application latency. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Once identified, the targeted correction is: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. Confirm by checking: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to swapping-induced application latency. It is not the most decisive first evidence here. The discriminating test is: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This can investigate cpu throttling under cgroup quota, but the given incident points to swapping-induced application latency. It is not the most decisive first evidence here. The discriminating test is: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, but the given incident points to swapping-induced application latency. It is not the most decisive first evidence here. The discriminating test is: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
Question 570
While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - List archive metadata with
tar -tvf and compare target path ownership and permissions with a known-good backup manifest. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.
Explanation
Correct Answer
D:Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This checks the mechanism behind rsync source trailing slash semantics. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Once identified, the targeted correction is: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Confirm by checking: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This can investigate quoting filenames in shell loops, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This can investigate tar permissions preservation on restore, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.