CompTIA XK0-006 Practice Test 54
Question 530
While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. 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?
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
- Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- 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.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path.
Explanation
Correct Answer
B:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This action corrects network interface mtu configuration without substituting an unrelated change. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Before acting, verify: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Afterward confirm: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This is a change associated with route metrics for preferred uplink, not a targeted repair of network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
C: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 network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
D:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 531
While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
- The destination image opens without missing backing-file errors and boots with expected guest data.
- The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
- Timestamped events from the daemon appear in its configured journal or log destination for the test request.
Explanation
Correct Answer
D:Timestamped events from the daemon appear in its configured journal or log destination for the test request. This is direct acceptance evidence for filesystem hierarchy standard log location rather than a generic process check. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. It validates the correction: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This outcome would support bash quoted positional arguments, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:The destination image opens without missing backing-file errors and boots with expected guest data. This outcome would support qemu overlay disk and backing file, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This outcome would support bootloader versus initramfs stages, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 532
During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Two subsequent deployments resolve the same digest and reproduce the approved package version.
- The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
- The container writes the intended test file and the host retains the documented least-privilege owner and label.
id in the new session includes both the old supplemental groups and the newly granted group.
Explanation
Correct Answer
A:Two subsequent deployments resolve the same digest and reproduce the approved package version. This is direct acceptance evidence for container image provenance by digest rather than a generic process check. An image tag can be retargeted; a content digest identifies a specific image manifest. It validates the correction: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly. This outcome would support opentofu plan and state protection, but does not establish that the reported container image provenance by digest problem is resolved. The required direct acceptance test is: Two subsequent deployments resolve the same digest and reproduce the approved package version. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
C: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 container image provenance by digest problem is resolved. The required direct acceptance test is: Two subsequent deployments resolve the same digest and reproduce the approved package version. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
D:id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported container image provenance by digest problem is resolved. The required direct acceptance test is: Two subsequent deployments resolve the same digest and reproduce the approved package version. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Question 533
While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. 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?
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
- The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes.
Explanation
Correct Answer
D:The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This is direct acceptance evidence for persistent grub kernel arguments rather than a generic process check. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. It validates the correction: 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. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This outcome would support bootloader versus initramfs stages, but does not establish that the reported persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. This outcome would support incorrect default gateway on dual subnet host, but does not establish that the reported persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 534
During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. 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?
- The service name resolves to the intended address and both name-based and IP-based connectivity work.
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
A:The service name resolves to the intended address and both name-based and IP-based connectivity work. This is direct acceptance evidence for name-resolution failure versus route failure rather than a generic process check. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. It validates the correction: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Incorrect Answers
B:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
C:A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This outcome would support bash quoted positional arguments, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work.
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
Question 535
During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. 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.
- Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records.
Explanation
Correct Answers
A:Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This is the targeted change needed after establishing the fault. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. Pair it with the supporting check: Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This supplies the decisive diagnostic observation for the stated fault. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. Pair this evidence with the targeted change: Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This choice concerns posix acl mask denies expected access rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 536
During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. 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
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line. - Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
Explanation
Correct Answer
B:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This checks the mechanism behind bash parameter expansion default. Bash ${name:-word} substitutes a default when a variable is unset or null, unlike an unguarded expansion under nounset. Once identified, the targeted correction is: Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. Confirm by checking: The script handles the unset optional variable with the documented default and still fails for missing required settings. Scenario context: During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This can investigate file existence conditional in bash, but the given incident points to bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This can investigate ci pipeline test gate before deployment, but the given incident points to bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 537
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. How should the administrator correct the underlying configuration rather than mask the symptom?
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
Explanation
Correct Answer
B:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This action corrects sudo action auditing without substituting an unrelated change. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Before acting, verify: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Afterward confirm: A test privileged command produces an attributable event with acting user, command, time and success or failure. 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
A:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of sudo action auditing. The described signal instead calls for: 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.
C:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of sudo action auditing. The described signal instead calls for: 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:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This is a change associated with tls server certificate name mismatch, not a targeted repair of sudo action auditing. The described signal instead calls for: 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 538
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. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
- Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
Explanation
Correct Answers
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This is the targeted change needed after establishing the fault. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Pair it with the supporting check: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. 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.
C:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This supplies the decisive diagnostic observation for the stated fault. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Pair this evidence with the targeted change: 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:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This choice concerns tar permissions preservation on restore rather than the required diagnosis-and-change pair for pam password history policy. Compare the needed evidence (Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.) with the repair (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.
D:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for pam password history policy. Compare the needed evidence (Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.) with the repair (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.
E:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This choice concerns least privilege for service processes rather than the required diagnosis-and-change pair for pam password history policy. Compare the needed evidence (Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.) with the repair (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.
Question 539
While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. 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.
- Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Use a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths. - Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
Explanation
Correct Answers
A:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This supplies the decisive diagnostic observation for the stated fault. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Pair this evidence with the targeted change: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This is the targeted change needed after establishing the fault. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Pair it with the supporting check: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
C:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This choice concerns stateful nftables established connections rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This choice concerns distribution package dependency resolution rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This choice concerns open deleted log consumes disk rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 540
During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. 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 a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
Explanation
Correct Answer
B:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This action corrects ai-generated dependency licensing review without substituting an unrelated change. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Before acting, verify: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Afterward confirm: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
Incorrect Answers
A: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 ai-generated dependency licensing review. The described signal instead calls for: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This is a change associated with sensitive data leakage into prompts, not a targeted repair of ai-generated dependency licensing review. The described signal instead calls for: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
D:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This is a change associated with kubernetes configmap versus secret handling, not a targeted repair of ai-generated dependency licensing review. The described signal instead calls for: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.