CompTIA XK0-006 Practice Test 56
Question 550
During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Other contributors can fetch the agreed release head without unexpected rewritten public commits.
- An intentionally failing test blocks deployment while the successful branch passes all required gates.
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
Explanation
Correct Answer
B:An intentionally failing test blocks deployment while the successful branch passes all required gates. This is direct acceptance evidence for ci pipeline test gate before deployment rather than a generic process check. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. It validates the correction: Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
Incorrect Answers
A:Other contributors can fetch the agreed release head without unexpected rewritten public commits. This outcome would support git history rewrite on shared branch, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates.
C:The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates.
D:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates.
Question 551
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
- The container writes the intended test file and the host retains the documented least-privilege owner and label.
- New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.
- The import completes under the service account and cannot modify unrelated root-owned directories.
Explanation
Correct Answer
A:A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This is direct acceptance evidence for pam password history policy rather than a generic process check. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. It validates the correction: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:The container writes the intended test file and the host retains the documented least-privilege owner and label. This outcome would support rootless podman bind mount access, but does not establish that the reported pam password history policy problem is resolved. The required direct acceptance test is: A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
C:New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. This outcome would support secure default umask for sensitive files, but does not establish that the reported pam password history policy problem is resolved. The required direct acceptance test is: A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
D:The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported pam password history policy problem is resolved. The required direct acceptance test is: A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
Question 552
During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?
- Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal.
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
- Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
- The import completes under the service account and cannot modify unrelated root-owned directories.
Explanation
Correct Answer
B:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This is direct acceptance evidence for dns resolution versus tcp connectivity fault rather than a generic process check. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. It validates the correction: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
Incorrect Answers
A:Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. This outcome would support dhcp lease and address conflict, but does not establish that the reported dns resolution versus tcp connectivity fault problem is resolved. The required direct acceptance test is: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
C:Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This outcome would support high i/o wait mistaken for cpu saturation, but does not establish that the reported dns resolution versus tcp connectivity fault problem is resolved. The required direct acceptance test is: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
D:The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported dns resolution versus tcp connectivity fault problem is resolved. The required direct acceptance test is: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
Question 553
During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Apply the approved password aging settings to the specific account with
chage and verify the new dates.
Explanation
Correct Answers
C:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This is the targeted change needed after establishing the fault. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Pair it with the supporting check: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
D:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This supplies the decisive diagnostic observation for the stated fault. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Pair this evidence with the targeted change: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This choice concerns kernel module dependency loading rather than the required diagnosis-and-change pair for local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This choice concerns symbolic link across filesystems rather than the required diagnosis-and-change pair for local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
E:Apply the approved password aging settings to the specific account with chage and verify the new dates. This choice concerns user password expiry visibility rather than the required diagnosis-and-change pair for local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
Question 554
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Compare current policy artifacts with a version-controlled baseline and correlated
auditd or file integrity events. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Explanation
Correct Answers
A:Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This supplies the decisive diagnostic observation for the stated fault. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Pair this evidence with the targeted change: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is the targeted change needed after establishing the fault. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Pair it with the supporting check: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 555
While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. 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 the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Use a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths.
Explanation
Correct Answer
C:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This action corrects apt package origin pinning without substituting an unrelated change. APT chooses candidates using versions and pin priorities; a repository being configured does not mean it is the only eligible source. Before acting, verify: Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. Afterward confirm: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is a change associated with distribution package dependency resolution, not a targeted repair of apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
D:Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This is a change associated with find modified files without broad recursion, not a targeted repair of apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 556
During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- The intended group can read the directory and unrelated users remain denied according to the ACL.
lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.- Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
- Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
Explanation
Correct Answer
A:The intended group can read the directory and unrelated users remain denied according to the ACL. This is direct acceptance evidence for posix acl mask denies expected access rather than a generic process check. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. It validates the correction: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. This outcome would support open deleted log consumes disk, but does not establish that the reported posix acl mask denies expected access problem is resolved. The required direct acceptance test is: The intended group can read the directory and unrelated users remain denied according to the ACL. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This outcome would support host firewall rejects container port, but does not establish that the reported posix acl mask denies expected access problem is resolved. The required direct acceptance test is: The intended group can read the directory and unrelated users remain denied according to the ACL.
D:Throughput improves and lock-wait time drops without relying solely on adding CPU cores. This outcome would support thread contention versus raw cpu capacity, but does not establish that the reported posix acl mask denies expected access problem is resolved. The required direct acceptance test is: The intended group can read the directory and unrelated users remain denied according to the ACL.
Question 557
During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. 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
virsh domiflist, the libvirt network type, bridge membership, and guest addressing. - Correlate the AVC source/target contexts and the expected service policy using
ausearch and ls -Z. - Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records. - Inspect
vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.
Explanation
Correct Answer
B:Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This checks the mechanism behind selinux avc denial versus unix mode. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. Once identified, the targeted correction is: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Confirm by checking: The service performs the authorized operation with the intended label and no matching AVC denial remains. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to selinux avc denial versus unix mode. It is not the most decisive first evidence here. The discriminating test is: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This can investigate ssh login denied by account lock policy, but the given incident points to selinux avc denial versus unix mode. It is not the most decisive first evidence here. The discriminating test is: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This can investigate swapping-induced application latency, but the given incident points to selinux avc denial versus unix mode. It is not the most decisive first evidence here. The discriminating test is: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 558
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
Explanation
Correct Answer
A:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This action corrects firewalld zone and interface binding without substituting an unrelated change. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Before acting, verify: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Afterward confirm: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This is a change associated with bash parameter expansion default, not a targeted repair of firewalld zone and interface binding. The described signal instead calls for: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is a change associated with stateful nftables established connections, not a targeted repair of firewalld zone and interface binding. The described signal instead calls for: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is a change associated with sssd central identity lookup, not a targeted repair of firewalld zone and interface binding. The described signal instead calls for: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
Question 559
During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. 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.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
- Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
Explanation
Correct Answers
B:Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This supplies the decisive diagnostic observation for the stated fault. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Pair this evidence with the targeted change: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
D:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This is the targeted change needed after establishing the fault. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Pair it with the supporting check: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
C:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
E: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 missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
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.