CompTIA XK0-006 Practice Test 67
Question 660
While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
- Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - 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.
Explanation
Correct Answers
A:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair it with the supporting check: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
B:Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair this evidence with the targeted change: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
Incorrect Answers
C:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.).
D:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E: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 choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.).
Question 661
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Check enforcement status,
ls -Z for the content, and AVC audit messages for the web daemon type. - Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access.
Explanation
Correct Answers
B:Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This supplies the decisive diagnostic observation for the stated fault. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Pair this evidence with the targeted change: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This is the targeted change needed after establishing the fault. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Pair it with the supporting check: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This choice concerns high i/o wait mistaken for cpu saturation rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 662
While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
Explanation
Correct Answer
B:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This action corrects rootless podman bind mount access without substituting an unrelated change. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Before acting, verify: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Afterward confirm: The container writes the intended test file and the host retains the documented least-privilege owner and label. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 a change associated with local account lock versus password expiration, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This is a change associated with container port publishing scope, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
Question 663
During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. 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.
- Inspect component exit statuses and reproduce the failing pipeline with and without
set -o pipefail under Bash. - Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word.
Explanation
Correct Answers
A:Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This supplies the decisive diagnostic observation for the stated fault. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Pair this evidence with the targeted change: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This is the targeted change needed after establishing the fault. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Pair it with the supporting check: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
C:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 664
During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. 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.
- Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
- Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure.
Explanation
Correct Answers
A:Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. Pair this evidence with the targeted change: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
B:Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. Pair it with the supporting check: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
Incorrect Answers
C:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This choice concerns service health-check signal versus process running rather than the required diagnosis-and-change pair for snmp polling versus traps. Compare the needed evidence (Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.) with the repair (Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.).
D:Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This choice concerns default home-directory skeleton rather than the required diagnosis-and-change pair for snmp polling versus traps. Compare the needed evidence (Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.) with the repair (Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for snmp polling versus traps. Compare the needed evidence (Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.) with the repair (Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 665
During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status. - Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
Explanation
Correct Answers
A:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. Pair it with the supporting check: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
C:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. Pair this evidence with the targeted change: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
Incorrect Answers
B:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This choice concerns text filtering with grep and awk rather than the required diagnosis-and-change pair for slo burn-rate alert selection. Compare the needed evidence (Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.) with the repair (Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This choice concerns missing storage driver after kernel update rather than the required diagnosis-and-change pair for slo burn-rate alert selection. Compare the needed evidence (Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.) with the repair (Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This choice concerns service health-check signal versus process running rather than the required diagnosis-and-change pair for slo burn-rate alert selection. Compare the needed evidence (Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.) with the repair (Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.).
Question 666
During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. 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?
- A test privileged command produces an attributable event with acting user, command, time and success or failure.
- The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision.
- A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
Explanation
Correct Answer
A:A test privileged command produces an attributable event with acting user, command, time and success or failure. This is direct acceptance evidence for sudo action auditing rather than a generic process check. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. It validates the correction: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. This outcome would support systemd enable versus start, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure.
C:A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This outcome would support pam failed-login lockout configuration, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure.
D:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure.
Question 667
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. 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.
- Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive. - Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository.
Explanation
Correct Answers
A:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is the targeted change needed after establishing the fault. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Pair it with the supporting check: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This supplies the decisive diagnostic observation for the stated fault. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Pair this evidence with the targeted change: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
C:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. 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 choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This choice concerns filesystem hierarchy standard log location rather than the required diagnosis-and-change pair for sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 668
During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. 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.
- Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Create a project virtual environment and install pinned project requirements into that isolated environment.
- Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies.
Explanation
Correct Answers
A:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This supplies the decisive diagnostic observation for the stated fault. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Pair this evidence with the targeted change: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
E:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is the targeted change needed after establishing the fault. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Pair it with the supporting check: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Create a project virtual environment and install pinned project requirements into that isolated environment. This choice concerns python application isolation from os packages rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
C:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This choice concerns find modified files without broad recursion rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
D:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Question 669
While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. 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 supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
- Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
Explanation
Correct Answer
B:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This action corrects graceful process shutdown signal without substituting an unrelated change. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Before acting, verify: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Afterward confirm: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
Incorrect Answers
A:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is a change associated with bonded nic failover detection, not a targeted repair of graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
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 graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
Question 670
During a compliance review of a production Linux endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
Explanation
Correct Answer
A:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This action corrects tls server certificate name mismatch without substituting an unrelated change. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Before acting, verify: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Afterward confirm: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
Incorrect Answers
B:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
C:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This is a change associated with mfa for administrative shell entry, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
D:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This is a change associated with graceful process shutdown signal, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.