CompTIA XK0-006 Practice Test 49
Question 480
During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. 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?
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Create a project virtual environment and install pinned project requirements into that isolated environment.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
Explanation
Correct Answer
B:Create a project virtual environment and install pinned project requirements into that isolated environment. This action corrects python application isolation from os packages without substituting an unrelated change. Python virtual environments isolate project packages from the operating system's Python installation. Before acting, verify: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Afterward confirm: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This is a change associated with bash quoted positional arguments, not a targeted repair of python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
C:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.
D:Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is a change associated with symbolic link across filesystems, not a targeted repair of python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.
Question 481
During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
- Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
Explanation
Correct Answer
A:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This action corrects inode exhaustion on linux filesystem without substituting an unrelated change. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Before acting, verify: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Afterward confirm: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This is a change associated with openscap policy scan interpretation, not a targeted repair of inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
C:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This is a change associated with missing storage driver after kernel update, not a targeted repair of inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
D:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is a change associated with incorrect default gateway on dual subnet host, not a targeted repair of inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Question 482
During a repeatability test on an independently built recovery environment, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
Explanation
Correct Answer
C:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This action corrects sensitive data leakage into prompts without substituting an unrelated change. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Before acting, verify: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. Afterward confirm: The troubleshooting prompt reproduces the failure without real customer data or credentials, and the exposed key is revoked.
Incorrect Answers
A:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is a change associated with posix acl mask denies expected access, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. Scenario context: During a repeatability test on an independently built recovery environment, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This is a change associated with ai-generated dependency licensing review, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
D:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This is a change associated with ci pipeline test gate before deployment, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
Question 483
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. 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 an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux. - Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
- Compare current policy artifacts with a version-controlled baseline and correlated
auditd or file integrity events. - Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.
Explanation
Correct Answers
A:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This is the targeted change needed after establishing the fault. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. Pair it with the supporting check: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This supplies the decisive diagnostic observation for the stated fault. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. Pair this evidence with the targeted change: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This choice concerns selinux persistent file context rather than the required diagnosis-and-change pair for secure default umask for sensitive files. Compare the needed evidence (Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.) with the repair (Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. This choice concerns path mtu black-hole in vpn link rather than the required diagnosis-and-change pair for secure default umask for sensitive files. Compare the needed evidence (Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.) with the repair (Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for secure default umask for sensitive files. Compare the needed evidence (Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.) with the repair (Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 484
During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early 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?
- Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Inspect
getfacl, directory mode, ACL mask and the required group principals. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- List archive metadata with
tar -tvf and compare target path ownership and permissions with a known-good backup manifest.
Explanation
Correct Answer
C:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This checks the mechanism behind rebuilding early-boot driver inventory. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Once identified, the targeted correction is: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Confirm by checking: A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This can investigate kernel module dependency loading, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect getfacl, directory mode, ACL mask and the required group principals. This can investigate posix acl restrictive shared directory, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
D:List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This can investigate tar permissions preservation on restore, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
Question 485
During a forensic reproduction of the fault at a secondary Linux test site, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. 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?
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
Explanation
Correct Answer
C:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This action corrects high i/o wait mistaken for cpu saturation without substituting an unrelated change. Linux load can include uninterruptible I/O waiters; high load average is not equivalent to CPU saturation. Before acting, verify: Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. Afterward confirm: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
B:Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This is a change associated with systemd timer activation and calendar, not a targeted repair of high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
D:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is a change associated with bonded nic failover detection, not a targeted repair of high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
Question 486
During a planned automation rollout to a Linux fleet, 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 operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?
readlink -f resolves the expected target and application access works while the link resides on another filesystem.- A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
- The merge commit retains both intended settings and tests pass without unresolved conflict markers.
- An intentionally failing test blocks deployment while the successful branch passes all required gates.
Explanation
Correct Answer
C: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:readlink -f resolves the expected target and application access works while the link resides on another filesystem. This outcome would support symbolic link across filesystems, 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. Scenario context: During a planned automation rollout to a Linux fleet, 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 operator must identify the affected mechanism before approving changes to other services.
B:A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This outcome would support bash quoted positional arguments, but does not establish that the reported 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.
D:An intentionally failing test blocks deployment while the successful branch passes all required gates. This outcome would support ci pipeline test gate before deployment, 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 487
While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
readlink -f resolves the expected target and application access works while the link resides on another filesystem.- A controlled set of files at known modification times yields the expected in-scope list only.
- The container writes the intended test file and the host retains the documented least-privilege owner and label.
- The expected directory account resolves through
getent and an authorized login succeeds without changing local accounts.
Explanation
Correct Answer
B:A controlled set of files at known modification times yields the expected in-scope list only. This is direct acceptance evidence for find modified files without broad recursion rather than a generic process check. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. It validates the correction: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:readlink -f resolves the expected target and application access works while the link resides on another filesystem. This outcome would support symbolic link across filesystems, but does not establish that the reported find modified files without broad recursion problem is resolved. The required direct acceptance test is: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The container writes the intended test file and the host retains the documented least-privilege owner and label. This outcome would support rootless podman bind mount access, but does not establish that the reported find modified files without broad recursion problem is resolved. The required direct acceptance test is: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. This outcome would support sssd central identity lookup, but does not establish that the reported find modified files without broad recursion problem is resolved. The required direct acceptance test is: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 488
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. How should the administrator correct the underlying configuration rather than mask the symptom?
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
Explanation
Correct Answer
D: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 action corrects quoting filenames in shell loops without substituting an unrelated change. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Before acting, verify: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Afterward confirm: 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.
Incorrect Answers
A: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 quoting filenames in shell loops. The described signal instead calls for: 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.
B:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of quoting filenames in shell loops. The described signal instead calls for: 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.
C:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This is a change associated with detecting pci versus usb hardware, not a targeted repair of quoting filenames in shell loops. The described signal instead calls for: 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.
Question 489
During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. 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 merge commit retains both intended settings and tests pass without unresolved conflict markers.
- An intentionally failing test blocks deployment while the successful branch passes all required gates.
- A failing producer causes the job to fail visibly instead of recording a false successful backup result.
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
B:An intentionally failing test blocks deployment while the successful branch passes all required gates. This is direct acceptance evidence for ci pipeline test gate before deployment rather than a generic process check. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. It validates the correction: Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
Incorrect Answers
A:The merge commit retains both intended settings and tests pass without unresolved conflict markers. This outcome would support git conflict resolution without loss, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates.
C:A failing producer causes the job to fail visibly instead of recording a false successful backup result. This outcome would support pipeline exit status propagation, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates.
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported ci pipeline test gate before deployment problem is resolved. The required direct acceptance test is: An intentionally failing test blocks deployment while the successful branch passes all required gates. Scenario context: During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 490
During a planned automation rollout to a Linux fleet, 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 operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
Explanation
Correct Answer
D: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: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 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.
B:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This can investigate ai-generated shell command validation, 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.
C:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, 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 planned automation rollout to a Linux fleet, 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 operator must identify the affected mechanism before approving changes to other services.