mcAfee Secure Website
23

CompTIA XK0-006 Bundle

Exam Code: XK0-006

Exam Name CompTIA Linux+

Certification Provider: CompTIA

Corresponding Certification: CompTIA Linux+

XK0-006 Training Materials $19.99

Reliable & Actual Study Materials for XK0-006 Exam Success

The Latest XK0-006 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    XK0-006 Questions & Answers

    160 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • exam =30
    Study Guide

    XK0-006 Study Guide

    1297 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

CompTIA Linux+ (XK0-006) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable CompTIA Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $154.98
Bundle Price: $134.99

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    160 Questions

    $124.99
    exam =35
  • exam =36
    Study Guide

    Study Guide

    1297 PDF Pages

    $29.99

CompTIA XK0-006 Practice Test 54

Question 530

A Linux administrator evaluates: A reviewer wants to roll back one risky commit without removing unrelated later improvements. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Use reviewed Git revert or other history-preserving corrective workflow for shared branches, and prevent secrets from being tracked through appropriate controls.
  2. Unquoted paths with whitespace or empty variables can split arguments, select unintended files or target a dangerous default.
  3. A test directory with spaces and unusual characters processes the intended set of files exactly once.
  4. A new corrective commit restores the intended configuration and secret scanning finds no active credential in tracked content.
  5. Create a project Python virtual environment and install reviewed dependencies inside it without changing the system package-manager Python environment.

Explanation

Correct Answers

A:

The observed Linux condition is: A reviewer wants to roll back one risky commit without removing unrelated later improvements. The recommended direct administrative response is: Use reviewed Git revert or other history-preserving corrective workflow for shared branches, and prevent secrets from being tracked through appropriate controls. The relevant failure or security risk is: Force-resetting published history or adding credentials to Git can break collaborators and expose reusable secrets in prior commits. Validate success with: A new corrective commit restores the intended configuration and secret scanning finds no active credential in tracked content.

D:

For the specific observation (A reviewer wants to roll back one risky commit without removing unrelated later improvements), the acceptance evidence is: A new corrective commit restores the intended configuration and secret scanning finds no active credential in tracked content. This verifies the action (Use reviewed Git revert or other history-preserving corrective workflow for shared branches, and prevent secrets from being tracked through appropriate controls.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Force-resetting published history or adding credentials to Git can break collaborators and expose reusable secrets in prior commits.

Incorrect Answers

B:

Safe Bash parameter expansion and quoting (4.2) would demonstrate or implement: Unquoted paths with whitespace or empty variables can split arguments, select unintended files or target a dangerous default. This choice can be useful for that problem, but it does not establish the Git safe rollback and protected secrets control being assessed here.

C:

Safe loops and file names in Bash (4.2) would demonstrate or implement: A test directory with spaces and unusual characters processes the intended set of files exactly once. This case instead tests Git safe rollback and protected secrets; the choice measures or changes another part of the system.

E:

Python virtual environments and dependencies (4.3) addresses another technical failure: Installing packages globally can break OS-managed Python tools or cause incompatible versions between applications. The paired-answer requirement concerns Git safe rollback and protected secrets; this alternative does not provide the matching intervention and separate acceptance evidence.

Question 531

A Linux administrator investigates: An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately. Which action BEST addresses the specific Linux technical requirement?

  1. Iterate over files using appropriately quoted arrays or null-delimited find output rather than splitting arbitrary file paths on whitespace.
  2. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.
  3. Use Kubernetes Deployments to manage replicated application pods and ConfigMaps for nonsensitive configuration, keeping credentials in approved secret management.
  4. Choose an appropriate supported unattended provisioning method such as cloud-init for cloud-instance first boot or Kickstart for compatible Linux OS installation.

Explanation

Correct Answer

B:

The observed Linux condition is: An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Safe loops and file names in Bash (4.2) addresses another technical failure: A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines. The case states: An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately. The most direct diagnosis is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

C:

Kubernetes Deployment and ConfigMap boundaries (4.1) addresses another technical failure: Placing passwords inside publicly readable ConfigMaps or editing disposable pods directly can leak data and lose changes at reconciliation. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

D:

First-boot provisioning with cloud-init and Kickstart (4.1) addresses another technical failure: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. The required diagnosis concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 532

In the post-change validation, the team sees: An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. A newly provisioned test machine applies the approved user, package and network setup during the intended lifecycle phase.
  2. A second Ansible run makes no unintended changes and reports the same desired service configuration on all intended hosts.
  3. An intentionally failed command triggers a nonzero job result and stops the dependent publication or deletion step.
  4. The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Explanation

Correct Answer

D:

For the specific observation (An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately), the acceptance evidence is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials. This verifies the action (Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.

Incorrect Answers

A:

First-boot provisioning with cloud-init and Kickstart (4.1) would demonstrate or implement: A newly provisioned test machine applies the approved user, package and network setup during the intended lifecycle phase. The case states: An assistant proposes rm -rf with a constructed path and the operator wants to run it on production immediately. The most direct evidence is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

B:

Idempotent configuration with Ansible (4.1) would demonstrate or implement: A second Ansible run makes no unintended changes and reports the same desired service configuration on all intended hosts. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

C:

Shell exit status and fail-fast pipelines (4.2) would demonstrate or implement: An intentionally failed command triggers a nonzero job result and stops the dependent publication or deletion step. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

Question 533

A change review on a Linux server identifies: A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode. Which action BEST addresses the specific Linux technical requirement?

  1. Choose an appropriate supported unattended provisioning method such as cloud-init for cloud-instance first boot or Kickstart for compatible Linux OS installation.
  2. Use an Ansible inventory and declarative tasks or roles that converge hosts to approved state, with check mode and repeat-run validation.
  3. Check command exit codes and use supported shell error handling such as explicit if tests and pipefail where appropriate to prevent false success.
  4. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

Explanation

Correct Answer

D:

The observed Linux condition is: A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

First-boot provisioning with cloud-init and Kickstart (4.1) addresses another technical failure: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. The case states: A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode. The most direct corrective action is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

B:

Idempotent configuration with Ansible (4.1) addresses another technical failure: Ad hoc scripts that repeatedly append configuration can create duplicate entries and uncontrolled drift across servers. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

C:

Shell exit status and fail-fast pipelines (4.2) addresses another technical failure: A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

Question 534

A Linux administrator reviews a reported issue: A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode. Which failure mode or risk is MOST relevant to this condition?

  1. Editing the main branch directly or merging without a review can deploy untested configuration to production.
  2. A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer.
  3. Ad hoc scripts that repeatedly append configuration can create duplicate entries and uncontrolled drift across servers.
  4. Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.

Explanation

Correct Answer

D:

The reported situation (A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode) most directly creates this failure risk: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. The corresponding safe response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. An appropriate outcome check is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Git branch workflow and reviewed merging (4.4) would demonstrate or implement: Editing the main branch directly or merging without a review can deploy untested configuration to production. The case states: A generated Ansible playbook uses an unsupported option that passes casual reading but fails in check mode. The most direct risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.

B:

Shell exit status and fail-fast pipelines (4.2) would demonstrate or implement: A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

C:

Idempotent configuration with Ansible (4.1) would demonstrate or implement: Ad hoc scripts that repeatedly append configuration can create duplicate entries and uncontrolled drift across servers. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

Question 535

A production incident ticket states: A Bash snippet from an AI tool includes a broad firewall exception unrelated to the user’s original request. Which action BEST addresses the specific Linux technical requirement?

  1. Check command exit codes and use supported shell error handling such as explicit if tests and pipefail where appropriate to prevent false success.
  2. Use an Ansible inventory and declarative tasks or roles that converge hosts to approved state, with check mode and repeat-run validation.
  3. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.
  4. Create a feature branch, commit coherent changes, review a diff and merge the approved branch into the intended base with a clear history.

Explanation

Correct Answer

C:

The observed Linux condition is: A Bash snippet from an AI tool includes a broad firewall exception unrelated to the user’s original request. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Shell exit status and fail-fast pipelines (4.2) addresses another technical failure: A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer. The case states: A Bash snippet from an AI tool includes a broad firewall exception unrelated to the user’s original request. The most direct corrective action is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

B:

Idempotent configuration with Ansible (4.1) addresses another technical failure: Ad hoc scripts that repeatedly append configuration can create duplicate entries and uncontrolled drift across servers. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

D:

Git branch workflow and reviewed merging (4.4) addresses another technical failure: Editing the main branch directly or merging without a review can deploy untested configuration to production. The required corrective action concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 536

An infrastructure engineer checks a specific situation: A Bash snippet from an AI tool includes a broad firewall exception unrelated to the user’s original request. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.
  2. An intentionally failed command triggers a nonzero job result and stops the dependent publication or deletion step.
  3. A newly provisioned test machine applies the approved user, package and network setup during the intended lifecycle phase.
  4. A second Ansible run makes no unintended changes and reports the same desired service configuration on all intended hosts.

Explanation

Correct Answer

A:

For the specific observation (A Bash snippet from an AI tool includes a broad firewall exception unrelated to the user’s original request), the acceptance evidence is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials. This verifies the action (Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.

Incorrect Answers

B:

Shell exit status and fail-fast pipelines (4.2) would demonstrate or implement: An intentionally failed command triggers a nonzero job result and stops the dependent publication or deletion step. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

C:

First-boot provisioning with cloud-init and Kickstart (4.1) would demonstrate or implement: A newly provisioned test machine applies the approved user, package and network setup during the intended lifecycle phase. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

D:

Idempotent configuration with Ansible (4.1) would demonstrate or implement: A second Ansible run makes no unintended changes and reports the same desired service configuration on all intended hosts. The required evidence concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 537

An authorized Linux operations assessment observes: An AI-generated regular expression matches far more log fields than intended and needs fixture testing. Which action BEST addresses the specific Linux technical requirement?

  1. Check command exit codes and use supported shell error handling such as explicit if tests and pipefail where appropriate to prevent false success.
  2. Choose an appropriate supported unattended provisioning method such as cloud-init for cloud-instance first boot or Kickstart for compatible Linux OS installation.
  3. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.
  4. Use an Ansible inventory and declarative tasks or roles that converge hosts to approved state, with check mode and repeat-run validation.

Explanation

Correct Answer

C:

The observed Linux condition is: An AI-generated regular expression matches far more log fields than intended and needs fixture testing. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Shell exit status and fail-fast pipelines (4.2) addresses another technical failure: A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer. The case states: An AI-generated regular expression matches far more log fields than intended and needs fixture testing. The most direct corrective action is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

B:

First-boot provisioning with cloud-init and Kickstart (4.1) addresses another technical failure: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

D:

Idempotent configuration with Ansible (4.1) addresses another technical failure: Ad hoc scripts that repeatedly append configuration can create duplicate entries and uncontrolled drift across servers. The required corrective action concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 538

In a controlled system validation, the observation is: An AI-generated regular expression matches far more log fields than intended and needs fixture testing. Which failure mode or risk is MOST relevant to this condition?

  1. Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.
  2. Force-resetting published history or adding credentials to Git can break collaborators and expose reusable secrets in prior commits.
  3. Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration.
  4. A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines.

Explanation

Correct Answer

A:

The reported situation (An AI-generated regular expression matches far more log fields than intended and needs fixture testing) most directly creates this failure risk: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. The corresponding safe response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. An appropriate outcome check is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

B:

Git safe rollback and protected secrets (4.4) would demonstrate or implement: Force-resetting published history or adding credentials to Git can break collaborators and expose reusable secrets in prior commits. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

C:

First-boot provisioning with cloud-init and Kickstart (4.1) would demonstrate or implement: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

D:

Safe loops and file names in Bash (4.2) would demonstrate or implement: A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines. The required evidence concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 539

During a planned service review, engineers find: An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it. Which action BEST addresses the specific Linux technical requirement?

  1. Use reviewed Git revert or other history-preserving corrective workflow for shared branches, and prevent secrets from being tracked through appropriate controls.
  2. Choose an appropriate supported unattended provisioning method such as cloud-init for cloud-instance first boot or Kickstart for compatible Linux OS installation.
  3. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.
  4. Iterate over files using appropriately quoted arrays or null-delimited find output rather than splitting arbitrary file paths on whitespace.

Explanation

Correct Answer

C:

The observed Linux condition is: An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Git safe rollback and protected secrets (4.4) addresses another technical failure: Force-resetting published history or adding credentials to Git can break collaborators and expose reusable secrets in prior commits. The case states: An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it. The most direct evidence is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

B:

First-boot provisioning with cloud-init and Kickstart (4.1) addresses another technical failure: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. This choice can be useful for that problem, but it does not establish the AI-generated administration code review and execution safety control being assessed here.

D:

Safe loops and file names in Bash (4.2) addresses another technical failure: A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines. The required evidence concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.

Question 540

A Linux administrator evaluates: An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines.
  2. The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.
  3. Check command exit codes and use supported shell error handling such as explicit if tests and pipefail where appropriate to prevent false success.
  4. The script returns correct values for normal, missing-key and invalid-JSON fixtures while logging actionable errors.
  5. Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.

Explanation

Correct Answers

B:

For the specific observation (An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it), the acceptance evidence is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials. This verifies the action (Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure.

E:

The observed Linux condition is: An engineer receives a plausible infrastructure diff and must confirm its actual target resources before applying it. The recommended direct administrative response is: Treat AI-generated shell or infrastructure code as untrusted draft; perform manual review, static checks, tests and least-privilege dry runs before deployment. The relevant failure or security risk is: Executing unreviewed generated commands can delete unintended data, weaken security or modify the wrong infrastructure. Validate success with: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

Incorrect Answers

A:

Safe loops and file names in Bash (4.2) would demonstrate or implement: A naïve for loop over command-substitution output can mis-handle filenames with spaces or newlines. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The proposed automation passes source review and bounded tests without touching unauthorized paths or credentials.

C:

Shell exit status and fail-fast pipelines (4.2) addresses another technical failure: A pipeline that returns the last successful command status can hide an earlier failed backup or data transfer. This case instead tests AI-generated administration code review and execution safety; the choice measures or changes another part of the system.

D:

Python JSON data extraction and structured error handling (4.3) would demonstrate or implement: The script returns correct values for normal, missing-key and invalid-JSON fixtures while logging actionable errors. The required paired action and test concerns AI-generated administration code review and execution safety; a passing result for this alternative could leave that requirement unresolved.