CompTIA XK0-006 Practice Test 26
Question 250
During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. 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.
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]].
Explanation
Correct Answers
B:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is the targeted change needed after establishing the fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair it with the supporting check: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This supplies the decisive diagnostic observation for the stated fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair this evidence with the targeted change: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
C:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This choice concerns name-resolution failure versus route failure rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
D:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This choice concerns pipeline exit status propagation rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Question 251
During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. 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?
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- Other contributors can fetch the agreed release head without unexpected rewritten public commits.
- Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
- The merge commit retains both intended settings and tests pass without unresolved conflict markers.
Explanation
Correct Answer
D:The merge commit retains both intended settings and tests pass without unresolved conflict markers. This is direct acceptance evidence for git conflict resolution without loss rather than a generic process check. Git conflicts require semantic reconciliation of competing edits, not automatically discarding a whole side. It validates the correction: Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
Incorrect Answers
A:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This outcome would support python dependency lock reproducibility, but does not establish that the reported git conflict resolution without loss problem is resolved. The required direct acceptance test is: The merge commit retains both intended settings and tests pass without unresolved conflict markers.
B: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 git conflict resolution without loss problem is resolved. The required direct acceptance test is: The merge commit retains both intended settings and tests pass without unresolved conflict markers.
C:Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported git conflict resolution without loss problem is resolved. The required direct acceptance test is: The merge commit retains both intended settings and tests pass without unresolved conflict markers.
Question 252
During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Inspect
vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. - Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
- Extend the correct logical volume using free VG extents and grow its ext4 filesystem with
resize2fs after LV growth. - Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.
Explanation
Correct Answers
A:Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This supplies the decisive diagnostic observation for the stated fault. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Pair this evidence with the targeted change: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
D:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is the targeted change needed after establishing the fault. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Pair it with the supporting check: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This choice concerns cpu throttling under cgroup quota rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
C:Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. This choice concerns ext4 logical-volume expansion rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This choice concerns bonded nic failover detection rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
Question 253
During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. 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.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
- Inspect the service account, systemd
User= setting, file ownership and required syscall/filesystem access. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service.
Explanation
Correct Answers
C:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is the targeted change needed after establishing the fault. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Pair it with the supporting check: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This supplies the decisive diagnostic observation for the stated fault. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Pair this evidence with the targeted change: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
B:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This choice concerns pam failed-login lockout configuration rather than the required diagnosis-and-change pair for least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
Question 254
During an ordinary maintenance shift on a multi-user Linux service 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 operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Inspect the container's published-port mapping and host listening sockets with
ss -ltnp plus firewall exposure. - Compare
systemctl is-active, is-enabled, unit install metadata and boot journal. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.
Explanation
Correct Answer
C:Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This checks the mechanism behind systemd enable versus start. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Once identified, the targeted correction is: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Confirm by checking: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. Scenario context: During an ordinary maintenance shift on a multi-user Linux service 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 operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to systemd enable versus start. It is not the most decisive first evidence here. The discriminating test is: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Scenario context: During an ordinary maintenance shift on a multi-user Linux service 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 operator must identify the affected mechanism before approving changes to other services.
B:Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to systemd enable versus start. It is not the most decisive first evidence here. The discriminating test is: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Scenario context: During an ordinary maintenance shift on a multi-user Linux service 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 operator must identify the affected mechanism before approving changes to other services.
D:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to systemd enable versus start. It is not the most decisive first evidence here. The discriminating test is: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Scenario context: During an ordinary maintenance shift on a multi-user Linux service 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 operator must identify the affected mechanism before approving changes to other services.
Question 255
During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services. 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. - Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
Explanation
Correct Answer
A:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This action corrects file existence conditional in bash without substituting an unrelated change. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Before acting, verify: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Afterward confirm: A missing test file takes the expected error branch while a regular test file is processed. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
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 file existence conditional in bash. The described signal instead calls for: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
C:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This is a change associated with pipeline exit status propagation, not a targeted repair of file existence conditional in bash. The described signal instead calls for: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
D:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of file existence conditional in bash. The described signal instead calls for: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Question 256
During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
- Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.
Explanation
Correct Answer
D:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This checks the mechanism behind network interface mtu configuration. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Once identified, the targeted correction is: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Confirm by checking: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This can investigate kubernetes configmap versus secret handling, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This can investigate degraded software raid detection, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
Question 257
During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. 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?
- Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
- Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
- Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
Explanation
Correct Answer
C:Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. This action corrects cloud-init initialization boundary without substituting an unrelated change. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. Before acting, verify: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Afterward confirm: New clones receive unique instance configuration without retaining another host's credentials in the base image. Scenario context: During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 cloud-init initialization boundary. The described signal instead calls for: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
B: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 cloud-init initialization boundary. The described signal instead calls for: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
D:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This is a change associated with pipeline exit status propagation, not a targeted repair of cloud-init initialization boundary. The described signal instead calls for: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
Question 258
During a production incident affecting a Linux application node, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
Explanation
Correct Answer
D:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This action corrects cpu throttling under cgroup quota without substituting an unrelated change. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Before acting, verify: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. Afterward confirm: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
Incorrect Answers
A:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is a change associated with firewalld zone and interface binding, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
B:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is a change associated with swapping-induced application latency, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
C:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This is a change associated with selinux avc denial versus unix mode, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. Scenario context: During a production incident affecting a Linux application node, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The operator must identify the affected mechanism before approving changes to other services.
Question 259
During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- The intended group can read the directory and unrelated users remain denied according to the ACL.
- Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal.
- A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
- The service performs the authorized operation with the intended label and no matching AVC denial remains.
Explanation
Correct Answer
D:The service performs the authorized operation with the intended label and no matching AVC denial remains. This is direct acceptance evidence for selinux avc denial versus unix mode rather than a generic process check. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. It validates the correction: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The intended group can read the directory and unrelated users remain denied according to the ACL. This outcome would support posix acl mask denies expected access, but does not establish that the reported selinux avc denial versus unix mode problem is resolved. The required direct acceptance test is: The service performs the authorized operation with the intended label and no matching AVC denial remains.
B:Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. This outcome would support dhcp lease and address conflict, but does not establish that the reported selinux avc denial versus unix mode problem is resolved. The required direct acceptance test is: The service performs the authorized operation with the intended label and no matching AVC denial remains.
C:A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret. This outcome would support kubernetes configmap versus secret handling, but does not establish that the reported selinux avc denial versus unix mode problem is resolved. The required direct acceptance test is: The service performs the authorized operation with the intended label and no matching AVC denial remains.
Question 260
During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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.
- Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.
Explanation
Correct Answers
B:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is the targeted change needed after establishing the fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair it with the supporting check: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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 supplies the decisive diagnostic observation for the stated fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair this evidence with the targeted change: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This choice concerns persistent networkmanager static address rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This choice concerns luks2 encrypted block-volume opening rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.