CompTIA XK0-006 Practice Test 32
Question 310
During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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?
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Apply the approved password aging settings to the specific account with
chage and verify the new dates.
Explanation
Correct Answer
D:Apply the approved password aging settings to the specific account with chage and verify the new dates. This action corrects user password expiry visibility without substituting an unrelated change. Existing account aging values do not automatically change when global defaults are modified for future accounts. Before acting, verify: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Afterward confirm: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 user password expiry visibility. The described signal instead calls for: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
B:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of user password expiry visibility. The described signal instead calls for: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
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 user password expiry visibility. The described signal instead calls for: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Question 311
During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
list-timers shows an expected next trigger and a controlled firing records a successful service run.- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
- Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
- The service performs the authorized operation with the intended label and no matching AVC denial remains.
Explanation
Correct Answer
C:Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures. This is direct acceptance evidence for path mtu black-hole in vpn link rather than a generic process check. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. It validates the correction: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
Incorrect Answers
A:list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, but does not establish that the reported path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
D:The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
Question 312
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. 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?
- An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
- A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
- Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
- Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
Explanation
Correct Answer
A:An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. This is direct acceptance evidence for ufw least-privilege inbound port rather than a generic process check. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. It validates the correction: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
Incorrect Answers
B:A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This outcome would support pam password history policy, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
C:Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
D:Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This outcome would support firewalld zone and interface binding, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
Question 313
During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. - Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events.
Explanation
Correct Answer
A:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This checks the mechanism behind gpg artifact signature validation. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Once identified, the targeted correction is: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. Confirm by checking: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. Scenario context: During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This can investigate ext4 logical-volume expansion, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This can investigate tls server certificate name mismatch, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services.
Question 314
While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Compare
systemctl is-active, is-enabled, unit install metadata and boot journal. - Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list. - Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
Explanation
Correct Answers
A:Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This supplies the decisive diagnostic observation for the stated fault. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Pair this evidence with the targeted change: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This is the targeted change needed after establishing the fault. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Pair it with the supporting check: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This choice concerns default home-directory skeleton rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This choice concerns systemd journal correlation rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 315
During a repeatability test on an independently built recovery environment, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. 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?
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path.
Explanation
Correct Answer
C:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This action corrects kubernetes configmap versus secret handling without substituting an unrelated change. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. Before acting, verify: Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. Afterward confirm: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
Incorrect Answers
A:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of kubernetes configmap versus secret handling. The described signal instead calls for: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
B:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This is a change associated with quoting filenames in shell loops, not a targeted repair of kubernetes configmap versus secret handling. The described signal instead calls for: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. Scenario context: During a repeatability test on an independently built recovery environment, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 kubernetes configmap versus secret handling. The described signal instead calls for: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. Scenario context: During a repeatability test on an independently built recovery environment, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 316
During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs.
Explanation
Correct Answer
D:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This action corrects secure default umask for sensitive files without substituting an unrelated change. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. Before acting, verify: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Afterward confirm: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. Scenario context: During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services.
B:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services.
C: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 secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services.
Question 317
During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.- A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.
- The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.
- Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Explanation
Correct Answer
B:A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. This is direct acceptance evidence for quoting filenames in shell loops rather than a generic process check. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. It validates the correction: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This outcome would support ext4 logical-volume expansion, but does not establish that the reported quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
C:The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.
D:Other contributors can fetch the agreed release head without unexpected rewritten public commits. This outcome would support git history rewrite on shared branch, but does not establish that the reported quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.
Question 318
During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Inspect
getfacl output including the mask:: entry and #effective permissions for the named group.
Explanation
Correct Answers
C:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is the targeted change needed after establishing the fault. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Pair it with the supporting check: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This supplies the decisive diagnostic observation for the stated fault. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Pair this evidence with the targeted change: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This choice concerns ssh login denied by account lock policy rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This choice concerns slo burn-rate alert selection rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 319
During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
Explanation
Correct Answer
B:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This checks the mechanism behind ai-generated shell command validation. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Once identified, the targeted correction is: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Confirm by checking: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. This can investigate sensitive data leakage into prompts, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This can investigate container image provenance by digest, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This can investigate ansible idempotent package management, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
Question 320
During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. 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 fresh test account receives the intended starter files without overwriting settings of existing accounts.
id in the new session includes both the old supplemental groups and the newly granted group.systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events.- Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
Explanation
Correct Answer
B:id in the new session includes both the old supplemental groups and the newly granted group. This is direct acceptance evidence for supplementary group membership append rather than a generic process check. -G sets the supplementary-group list; -aG appends without removing existing groups. It validates the correction: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:A fresh test account receives the intended starter files without overwriting settings of existing accounts. This outcome would support default home-directory skeleton, but does not establish that the reported supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
C:systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. This outcome would support systemd journal correlation, but does not establish that the reported supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
D:Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This outcome would support host firewall rejects container port, but does not establish that the reported supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.