CompTIA XK0-006 Practice Test 74
Question 730
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
- The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available.
- The expected
/dev/mapper device appears and the existing encrypted filesystem mounts with intact files. - A test privileged command produces an attributable event with acting user, command, time and success or failure.
Explanation
Correct Answer
D:A test privileged command produces an attributable event with acting user, command, time and success or failure. This is direct acceptance evidence for sudo action auditing rather than a generic process check. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. It validates the correction: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a 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:A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This outcome would support pam failed-login lockout configuration, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure.
B:The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. This outcome would support corrupted fstab mount at boot, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure.
C:The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. This outcome would support luks2 encrypted block-volume opening, but does not establish that the reported sudo action auditing problem is resolved. The required direct acceptance test is: A test privileged command produces an attributable event with acting user, command, time and success or failure. 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 731
During a planned automation rollout to a Linux fleet, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. 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?
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. - 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
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 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:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This is a change associated with python subprocess invocation safety, 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 planned automation rollout to a Linux fleet, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. 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 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.
C:Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This is a change associated with supplementary group membership append, 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 planned automation rollout to a Linux fleet, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. The operator must identify the affected mechanism before approving changes to other services.
Question 732
While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Create a project virtual environment and install pinned project requirements into that isolated environment.
- Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
Explanation
Correct Answers
A:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This supplies the decisive diagnostic observation for the stated fault. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Pair this evidence with the targeted change: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is the targeted change needed after establishing the fault. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Pair it with the supporting check: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Create a project virtual environment and install pinned project requirements into that isolated environment. This choice concerns python application isolation from os packages rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for distribution package dependency resolution. Compare the needed evidence (Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.) with the repair (Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 733
During a repeatability test on an independently built recovery environment, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
- Inspect
cloud-init status, user-data logs, image customization stages and credential handling.
Explanation
Correct Answer
C:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This checks the mechanism behind opentofu plan and state protection. IaC tools reconcile declared and recorded state; plan review and state protection prevent unintended destructive changes. Once identified, the targeted correction is: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. Confirm by checking: The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
Incorrect Answers
A: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 opentofu plan and state protection. It is not the most decisive first evidence here. The discriminating test is: Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. Scenario context: During a repeatability test on an independently built recovery environment, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to opentofu plan and state protection. It is not the most decisive first evidence here. The discriminating test is: Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
D:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This can investigate cloud-init initialization boundary, but the given incident points to opentofu plan and state protection. It is not the most decisive first evidence here. The discriminating test is: Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. Scenario context: During a repeatability test on an independently built recovery environment, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 734
During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- 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.
- Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Inspect
ip route show default, ip route get for a real destination, and per-connection route metrics.
Explanation
Correct Answers
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 the targeted change needed after establishing the fault. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Pair it with the supporting check: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
D:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This supplies the decisive diagnostic observation for the stated fault. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Pair this evidence with the targeted change: 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: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This choice concerns bootloader versus initramfs stages rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
B:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This choice concerns route metrics for preferred uplink rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
Question 735
During a planned automation rollout to a Linux fleet, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- 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 and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
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 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 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 planned automation rollout to a Linux fleet, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The operator must identify the affected mechanism before approving changes to other services.
C: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 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 planned automation rollout to a Linux fleet, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The operator must identify the affected mechanism before approving changes to other services.
D: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.
Question 736
During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. 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?
- Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- 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.
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
Explanation
Correct Answer
D:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This action corrects kvm virtual networking bridge selection without substituting an unrelated change. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Before acting, verify: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Afterward confirm: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This is a change associated with qemu overlay disk and backing file, not a targeted repair of kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
B:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
C: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 kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
Question 737
During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.
Explanation
Correct Answer
C:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This checks the mechanism behind xfs online filesystem growth. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Once identified, the targeted correction is: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Confirm by checking: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This can investigate network interface mtu configuration, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.
B:Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.
D: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 xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.
Question 738
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 TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive.
Explanation
Correct Answers
B:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is the targeted change needed after establishing the fault. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Pair it with the supporting check: 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.
E:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This supplies the decisive diagnostic observation for the stated fault. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Pair this evidence with the targeted change: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. 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
A:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). 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:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This choice concerns tls server certificate name mismatch rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). 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:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). 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 739
During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. 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?
- Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
- Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line.
Explanation
Correct Answer
B:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This checks the mechanism behind cloud-init initialization boundary. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. Once identified, the targeted correction is: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. Confirm by checking: New clones receive unique instance configuration without retaining another host's credentials in the base image. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This can investigate opentofu plan and state protection, but the given incident points to cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This can investigate bash parameter expansion default, but the given incident points to cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
Question 740
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. Which outcome provides the strongest confirmation that the intended behavior is restored?
- A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
- A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
Explanation
Correct Answer
A:A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret. This is direct acceptance evidence for kubernetes configmap versus secret handling rather than a generic process check. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. It validates the correction: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
Incorrect Answers
B:A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This outcome would support rebuilding early-boot driver inventory, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
C:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
D:The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.