100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 40
A decommissioned router still receives automation because stale inventory metadata marked it as production. Independently, reviewers flag this potentially unsafe practice for assessment: 'Discard resolved inventory after the playbook returns success'. Which verification addresses that practice without assuming it caused the incident?
- Treat every previously managed device as permanently in service
- Compare inventory serials and lifecycle status to asset records
- Compare logged inventory revision and actual hosts touched
- Inspect resolved variable precedence for a sample device
Explanation
Correct Answer
C:Later responders cannot reconstruct intended targets. The intended behavior is: Provenance ties configuration results to a defined cohort.
Incorrect Answers
A:A stale target may be unreachable or owned by another team.
B:This checks choose an authoritative device list, not the named failure. A current source of truth reduces stale device targeting.
D:This checks separate host and group variables, not the named failure. Uncontrolled variable overrides produce wrong configuration.
Question 41
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. The specific implementation objective is to pin compatible provider releases. Which configuration best meets the stated requirement?
- Hard-code controller administrator tokens in HCL committed to Git
- Delete the lock file before every apply to force new versions
- Declare tested provider version constraints in the root module
- Approve a provider upgrade from a successful download alone
Explanation
Correct Answer
C:Explicit constraints protect compatibility between engineers.
Incorrect Answers
A:Credential leakage grants unauthorized infrastructure control.
B:Uncontrolled resolution undermines reproducibility.
D:Installation success does not prove safe plan results.
Question 42
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. The specific implementation objective is to preserve dependency lock. Which design action is most appropriate for this case?
- Hard-code controller administrator tokens in HCL committed to Git
- Commit the provider dependency lockfile for consistent checksum-based selection
- Approve a provider upgrade from a successful download alone
- Allow unrestricted automatic upgrades in production CI
Explanation
Correct Answer
B:The lockfile records selected provider versions and hashes.
Incorrect Answers
A:Credential leakage grants unauthorized infrastructure control.
C:Installation success does not prove safe plan results.
D:Untested upgrades can change schema or behavior.
Question 43
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. The specific implementation objective is to separate secret settings. What should the engineer implement for this specific objective?
- Delete the lock file before every apply to force new versions
- Allow unrestricted automatic upgrades in production CI
- Approve a provider upgrade from a successful download alone
- Use protected runtime variables or a secret store for API tokens
Explanation
Correct Answer
D:Credentials must not be embedded in Terraform source.
Incorrect Answers
A:Uncontrolled resolution undermines reproducibility.
B:Untested upgrades can change schema or behavior.
C:Installation success does not prove safe plan results.
Question 44
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. The specific implementation objective is to validate after upgrade. Which adjustment would satisfy this particular constraint?
- Delete the lock file before every apply to force new versions
- Hard-code controller administrator tokens in HCL committed to Git
- Allow unrestricted automatic upgrades in production CI
- Run initialization, validation and a reviewed plan in staging before any production apply
Explanation
Correct Answer
D:A new provider needs schema and behavior verification.
Incorrect Answers
A:Uncontrolled resolution undermines reproducibility.
B:Credential leakage grants unauthorized infrastructure control.
C:Untested upgrades can change schema or behavior.
Question 45
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. The deployment plan must both (1) pin compatible provider releases and (2) separate secret settings. Which TWO actions together satisfy those requirements? Choose TWO.
- Declare tested provider version constraints in the root module
- Delete the lock file before every apply to force new versions
- Use protected runtime variables or a secret store for API tokens
- Allow unrestricted automatic upgrades in production CI
- Hard-code controller administrator tokens in HCL committed to Git
Explanation
Correct Answers
A:Explicit constraints protect compatibility between engineers.
C:Credentials must not be embedded in Terraform source.
Incorrect Answers
B:Uncontrolled resolution undermines reproducibility.
D:Untested upgrades can change schema or behavior.
E:Credential leakage grants unauthorized infrastructure control.
Question 46
A team uses Terraform to manage a tested network-controller provider and wants repeatable runs across workstations. Three conditions must be met: (1) pin compatible provider releases; (2) separate secret settings; and (3) validate after upgrade. Which THREE actions form the narrowest complete plan? Choose THREE.
- Run initialization, validation and a reviewed plan in staging before any production apply
- Use protected runtime variables or a secret store for API tokens
- Delete the lock file before every apply to force new versions
- Declare tested provider version constraints in the root module
- Approve a provider upgrade from a successful download alone
- Hard-code controller administrator tokens in HCL committed to Git
Explanation
Correct Answers
A:A new provider needs schema and behavior verification.
B:Credentials must not be embedded in Terraform source.
D:Explicit constraints protect compatibility between engineers.
Incorrect Answers
C:Uncontrolled resolution undermines reproducibility.
E:Installation success does not prove safe plan results.
F:Credential leakage grants unauthorized infrastructure control.
Question 47
A Terraform run fails after a provider upgrade silently changes a resource attribute. Independently, reviewers flag this potentially unsafe practice for assessment: 'Allow unrestricted automatic upgrades in production CI'. Which inspection most directly evaluates that practice?
- Inspect init, validate and plan outputs against staging baseline
- Review variable injection and credential exposure in state/logs
- Delete the lock file before every apply to force new versions
- Inspect provider constraints and lock file
Explanation
Correct Answer
D:Untested upgrades can change schema or behavior. The intended behavior is: Explicit constraints protect compatibility between engineers.
Incorrect Answers
A:This checks validate after upgrade, not the named failure. A new provider needs schema and behavior verification.
B:This checks separate secret settings, not the named failure. Credentials must not be embedded in Terraform source.
C:Uncontrolled resolution undermines reproducibility.
Question 48
A Terraform run fails after a provider upgrade silently changes a resource attribute. Independently, reviewers flag this potentially unsafe practice for assessment: 'Delete the lock file before every apply to force new versions'. What diagnostic evidence should first be collected to assess that practice?
- Compare locked provider hashes across runners
- Inspect provider constraints and lock file
- Hard-code controller administrator tokens in HCL committed to Git
- Inspect init, validate and plan outputs against staging baseline
Explanation
Correct Answer
A:Uncontrolled resolution undermines reproducibility. The intended behavior is: The lockfile records selected provider versions and hashes.
Incorrect Answers
B:This checks pin compatible provider releases, not the named failure. Explicit constraints protect compatibility between engineers.
C:Credential leakage grants unauthorized infrastructure control.
D:This checks validate after upgrade, not the named failure. A new provider needs schema and behavior verification.
Question 49
A Terraform run fails after a provider upgrade silently changes a resource attribute. Independently, reviewers flag this potentially unsafe practice for assessment: 'Hard-code controller administrator tokens in HCL committed to Git'. Which focused check best tests this specific assumption?
- Inspect init, validate and plan outputs against staging baseline
- Inspect provider constraints and lock file
- Review variable injection and credential exposure in state/logs
- Delete the lock file before every apply to force new versions
Explanation
Correct Answer
C:Credential leakage grants unauthorized infrastructure control. The intended behavior is: Credentials must not be embedded in Terraform source.
Incorrect Answers
A:This checks validate after upgrade, not the named failure. A new provider needs schema and behavior verification.
B:This checks pin compatible provider releases, not the named failure. Explicit constraints protect compatibility between engineers.
D:Uncontrolled resolution undermines reproducibility.
Question 50
A Terraform run fails after a provider upgrade silently changes a resource attribute. Independently, reviewers flag this potentially unsafe practice for assessment: 'Approve a provider upgrade from a successful download alone'. Which verification addresses that practice without assuming it caused the incident?
- Allow unrestricted automatic upgrades in production CI
- Review variable injection and credential exposure in state/logs
- Compare locked provider hashes across runners
- Inspect init, validate and plan outputs against staging baseline
Explanation
Correct Answer
D:Installation success does not prove safe plan results. The intended behavior is: A new provider needs schema and behavior verification.
Incorrect Answers
A:Untested upgrades can change schema or behavior.
B:This checks separate secret settings, not the named failure. Credentials must not be embedded in Terraform source.
C:This checks preserve dependency lock, not the named failure. The lockfile records selected provider versions and hashes.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests