100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 370
A runner reports ModuleNotFoundError although the dependency exists on the developer's laptop. Independently, reviewers flag this potentially unsafe practice for assessment: 'Declare fix complete after a single warm-cache rerun'. Which verification addresses that practice without assuming it caused the incident?
- Rely on packages installed globally on one engineer laptop
- Inspect clean runner job log
- Compare image digest and dependency requirements
- Inspect clean-run install step and cache policy
Explanation
Correct Answer
B:A warm cache can hide undeclared dependencies. The intended behavior is: Clean builds demonstrate reproducibility.
Incorrect Answers
A:Local environment does not define runner dependencies.
C:This checks select compatible image, not the named failure. Runtime mismatch can cause reproducible test failures.
D:This checks cache only safe objects, not the named failure. Cache expiration should not break a clean build.
Question 371
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. The specific implementation objective is to pin execution environment. Which configuration best meets the stated requirement?
- Declare the upgrade safe from a successful binary download
- Ignore provider warnings until deployment has started
- Create a fresh unreviewed plan during production deploy
- Use compatible pinned runtime images and providers across relevant stages
Explanation
Correct Answer
D:Uncontrolled tool versions produce inconsistent results.
Incorrect Answers
A:Installation is not deployment compatibility.
B:Late failures increase outage risk.
C:A later plan may contain drift or other changes.
Question 372
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. The specific implementation objective is to share reviewed plan artifact. Which design action is most appropriate for this case?
- Generate and pass the exact approved plan to the designated apply stage when supported
- Declare the upgrade safe from a successful binary download
- Allow build and deploy jobs to use arbitrary latest Terraform binaries
- Ignore provider warnings until deployment has started
Explanation
Correct Answer
A:Plan/apply consistency reduces surprise changes.
Incorrect Answers
B:Installation is not deployment compatibility.
C:Version mismatch can invalidate a reviewed plan.
D:Late failures increase outage risk.
Question 373
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. The specific implementation objective is to validate schema before deploy. What should the engineer implement for this specific objective?
- Declare the upgrade safe from a successful binary download
- Create a fresh unreviewed plan during production deploy
- Allow build and deploy jobs to use arbitrary latest Terraform binaries
- Run terraform validate and relevant provider schema checks early
Explanation
Correct Answer
D:A syntax pass alone does not detect all type mismatches.
Incorrect Answers
A:Installation is not deployment compatibility.
B:A later plan may contain drift or other changes.
C:Version mismatch can invalidate a reviewed plan.
Question 374
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. The specific implementation objective is to retest after version changes. Which adjustment would satisfy this particular constraint?
- Allow build and deploy jobs to use arbitrary latest Terraform binaries
- Ignore provider warnings until deployment has started
- Create a fresh unreviewed plan during production deploy
- Use a controlled staging pipeline when upgrading provider or Terraform
Explanation
Correct Answer
D:Version changes require regression validation.
Incorrect Answers
A:Version mismatch can invalidate a reviewed plan.
B:Late failures increase outage risk.
C:A later plan may contain drift or other changes.
Question 375
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. The deployment plan must both (1) share reviewed plan artifact and (2) retest after version changes. Which TWO actions together satisfy those requirements? Choose TWO.
- Ignore provider warnings until deployment has started
- Declare the upgrade safe from a successful binary download
- Generate and pass the exact approved plan to the designated apply stage when supported
- Use a controlled staging pipeline when upgrading provider or Terraform
- Allow build and deploy jobs to use arbitrary latest Terraform binaries
Explanation
Correct Answers
C:Plan/apply consistency reduces surprise changes.
D:Version changes require regression validation.
Incorrect Answers
A:Late failures increase outage risk.
B:Installation is not deployment compatibility.
E:Version mismatch can invalidate a reviewed plan.
Question 376
A GitLab deployment job uses a Terraform provider version that differs between pipeline stages. Three conditions must be met: (1) pin execution environment; (2) validate schema before deploy; and (3) retest after version changes. Which THREE actions form the narrowest complete plan? Choose THREE.
- Run terraform validate and relevant provider schema checks early
- Allow build and deploy jobs to use arbitrary latest Terraform binaries
- Use compatible pinned runtime images and providers across relevant stages
- Use a controlled staging pipeline when upgrading provider or Terraform
- Declare the upgrade safe from a successful binary download
- Create a fresh unreviewed plan during production deploy
Explanation
Correct Answers
A:A syntax pass alone does not detect all type mismatches.
C:Uncontrolled tool versions produce inconsistent results.
D:Version changes require regression validation.
Incorrect Answers
B:Version mismatch can invalidate a reviewed plan.
E:Installation is not deployment compatibility.
F:A later plan may contain drift or other changes.
Question 377
Prevalidation passes on an old runner image but deployment fails on a newer provider schema. Independently, reviewers flag this potentially unsafe practice for assessment: 'Allow build and deploy jobs to use arbitrary latest Terraform binaries'. Which inspection most directly evaluates that practice?
- Ignore provider warnings until deployment has started
- Compare artifact hash and apply command
- Inspect staging plan and regression tests
- Inspect image tag/digest and provider lock
Explanation
Correct Answer
D:Version mismatch can invalidate a reviewed plan. The intended behavior is: Uncontrolled tool versions produce inconsistent results.
Incorrect Answers
A:Late failures increase outage risk.
B:This checks share reviewed plan artifact, not the named failure. Plan/apply consistency reduces surprise changes.
C:This checks retest after version changes, not the named failure. Version changes require regression validation.
Question 378
Prevalidation passes on an old runner image but deployment fails on a newer provider schema. Independently, reviewers flag this potentially unsafe practice for assessment: 'Create a fresh unreviewed plan during production deploy'. What diagnostic evidence should first be collected to assess that practice?
- Inspect image tag/digest and provider lock
- Compare artifact hash and apply command
- Inspect validation and plan error output
- Declare the upgrade safe from a successful binary download
Explanation
Correct Answer
B:A later plan may contain drift or other changes. The intended behavior is: Plan/apply consistency reduces surprise changes.
Incorrect Answers
A:This checks pin execution environment, not the named failure. Uncontrolled tool versions produce inconsistent results.
C:This checks validate schema before deploy, not the named failure. A syntax pass alone does not detect all type mismatches.
D:Installation is not deployment compatibility.
Question 379
Prevalidation passes on an old runner image but deployment fails on a newer provider schema. Independently, reviewers flag this potentially unsafe practice for assessment: 'Ignore provider warnings until deployment has started'. Which focused check best tests this specific assumption?
- Inspect staging plan and regression tests
- Inspect validation and plan error output
- Inspect image tag/digest and provider lock
- Create a fresh unreviewed plan during production deploy
Explanation
Correct Answer
B:Late failures increase outage risk. The intended behavior is: A syntax pass alone does not detect all type mismatches.
Incorrect Answers
A:This checks retest after version changes, not the named failure. Version changes require regression validation.
C:This checks pin execution environment, not the named failure. Uncontrolled tool versions produce inconsistent results.
D:A later plan may contain drift or other changes.
Question 380
Prevalidation passes on an old runner image but deployment fails on a newer provider schema. Independently, reviewers flag this potentially unsafe practice for assessment: 'Declare the upgrade safe from a successful binary download'. Which verification addresses that practice without assuming it caused the incident?
- Inspect staging plan and regression tests
- Create a fresh unreviewed plan during production deploy
- Inspect image tag/digest and provider lock
- Inspect validation and plan error output
Explanation
Correct Answer
A:Installation is not deployment compatibility. The intended behavior is: Version changes require regression validation.
Incorrect Answers
B:A later plan may contain drift or other changes.
C:This checks pin execution environment, not the named failure. Uncontrolled tool versions produce inconsistent results.
D:This checks validate schema before deploy, not the named failure. A syntax pass alone does not detect all type mismatches.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests