100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 580
The API database port was accidentally published to an external interface instead of restricted to the Compose network. Independently, reviewers flag this potentially unsafe practice for assessment: 'Assume a successful Compose start means ports are secure'. Which verification addresses that practice without assuming it caused the incident?
- Publish administrative debug ports to all interfaces
- Inspect ports and networks definitions
- Inspect volume definitions and permissions
- Scan published ports from allowed and denied networks
Explanation
Correct Answer
D:Startup does not prove network isolation. The intended behavior is: A file-only review may miss external exposure.
Incorrect Answers
A:Debug interfaces may leak privileged controls.
B:This checks use private service networking, not the named failure. Private networking reduces exposed services.
C:This checks protect persistent volumes, not the named failure. Data should survive container recreation without exposure.
Question 581
A GitLab CE network automation job installs Python dependencies from a package registry. The specific implementation objective is to pin trusted dependency versions. Which configuration best meets the stated requirement?
- Reinstall arbitrary newest dependencies during deployment
- Run package installation with full controller administrator secrets exposed
- Treat a successful import as proof the package is trustworthy
- Use reviewed package versions and hashes where supported
Explanation
Correct Answer
D:Locking versions improves integrity and reproducibility.
Incorrect Answers
A:Deployment may differ from tested code.
B:Dependency code could misuse privileged secrets.
C:Import success says nothing about supply-chain risk.
Question 582
A GitLab CE network automation job installs Python dependencies from a package registry. The specific implementation objective is to separate build from production secrets. Which design action is most appropriate for this case?
- Treat a successful import as proof the package is trustworthy
- Build and test packages without production API tokens
- Install unbounded latest versions in a privileged deploy job
- Reinstall arbitrary newest dependencies during deployment
Explanation
Correct Answer
B:Untrusted dependencies should not inherit write credentials.
Incorrect Answers
A:Import success says nothing about supply-chain risk.
C:New dependencies can introduce malicious code.
D:Deployment may differ from tested code.
Question 583
A GitLab CE network automation job installs Python dependencies from a package registry. The specific implementation objective is to scan package changes. What should the engineer implement for this specific objective?
- Run package installation with full controller administrator secrets exposed
- Install unbounded latest versions in a privileged deploy job
- Review dependency diffs and run appropriate security checks
- Reinstall arbitrary newest dependencies during deployment
Explanation
Correct Answer
C:A dependency update can change execution behavior.
Incorrect Answers
A:Dependency code could misuse privileged secrets.
B:New dependencies can introduce malicious code.
D:Deployment may differ from tested code.
Question 584
A GitLab CE network automation job installs Python dependencies from a package registry. The specific implementation objective is to promote exact verified artifact. Which adjustment would satisfy this particular constraint?
- Treat a successful import as proof the package is trustworthy
- Run package installation with full controller administrator secrets exposed
- Deploy the package bytes produced by protected successful build
- Install unbounded latest versions in a privileged deploy job
Explanation
Correct Answer
C:Consistency prevents untested repackaging.
Incorrect Answers
A:Import success says nothing about supply-chain risk.
B:Dependency code could misuse privileged secrets.
D:New dependencies can introduce malicious code.
Question 585
A GitLab CE network automation job installs Python dependencies from a package registry. The deployment plan must both (1) pin trusted dependency versions and (2) scan package changes. Which TWO actions together satisfy those requirements? Choose TWO.
- Install unbounded latest versions in a privileged deploy job
- Use reviewed package versions and hashes where supported
- Treat a successful import as proof the package is trustworthy
- Run package installation with full controller administrator secrets exposed
- Review dependency diffs and run appropriate security checks
Explanation
Correct Answers
B:Locking versions improves integrity and reproducibility.
E:A dependency update can change execution behavior.
Incorrect Answers
A:New dependencies can introduce malicious code.
C:Import success says nothing about supply-chain risk.
D:Dependency code could misuse privileged secrets.
Question 586
A GitLab CE network automation job installs Python dependencies from a package registry. Three conditions must be met: (1) pin trusted dependency versions; (2) scan package changes; and (3) promote exact verified artifact. Which THREE actions form the narrowest complete plan? Choose THREE.
- Use reviewed package versions and hashes where supported
- Review dependency diffs and run appropriate security checks
- Deploy the package bytes produced by protected successful build
- Install unbounded latest versions in a privileged deploy job
- Reinstall arbitrary newest dependencies during deployment
- Treat a successful import as proof the package is trustworthy
Explanation
Correct Answers
A:Locking versions improves integrity and reproducibility.
B:A dependency update can change execution behavior.
C:Consistency prevents untested repackaging.
Incorrect Answers
D:New dependencies can introduce malicious code.
E:Deployment may differ from tested code.
F:Import success says nothing about supply-chain risk.
Question 587
A compromised dependency release appears under the expected package name. Independently, reviewers flag this potentially unsafe practice for assessment: 'Install unbounded latest versions in a privileged deploy job'. Which inspection most directly evaluates that practice?
- Compare dependency lock and artifact hash
- Treat a successful import as proof the package is trustworthy
- Review job environment variables and privilege stages
- Inspect locked dependencies and provenance
Explanation
Correct Answer
D:New dependencies can introduce malicious code. The intended behavior is: Locking versions improves integrity and reproducibility.
Incorrect Answers
A:This checks promote exact verified artifact, not the named failure. Consistency prevents untested repackaging.
B:Import success says nothing about supply-chain risk.
C:This checks separate build from production secrets, not the named failure. Untrusted dependencies should not inherit write credentials.
Question 588
A compromised dependency release appears under the expected package name. Independently, reviewers flag this potentially unsafe practice for assessment: 'Run package installation with full controller administrator secrets exposed'. What diagnostic evidence should first be collected to assess that practice?
- Review job environment variables and privilege stages
- Treat a successful import as proof the package is trustworthy
- Compare dependency lock and artifact hash
- Inspect locked dependencies and provenance
Explanation
Correct Answer
A:Dependency code could misuse privileged secrets. The intended behavior is: Untrusted dependencies should not inherit write credentials.
Incorrect Answers
B:Import success says nothing about supply-chain risk.
C:This checks promote exact verified artifact, not the named failure. Consistency prevents untested repackaging.
D:This checks pin trusted dependency versions, not the named failure. Locking versions improves integrity and reproducibility.
Question 589
A compromised dependency release appears under the expected package name. Independently, reviewers flag this potentially unsafe practice for assessment: 'Treat a successful import as proof the package is trustworthy'. Which focused check best tests this specific assumption?
- Review job environment variables and privilege stages
- Install unbounded latest versions in a privileged deploy job
- Inspect SBOM/advisory results and code changes
- Compare dependency lock and artifact hash
Explanation
Correct Answer
C:Import success says nothing about supply-chain risk. The intended behavior is: A dependency update can change execution behavior.
Incorrect Answers
A:This checks separate build from production secrets, not the named failure. Untrusted dependencies should not inherit write credentials.
B:New dependencies can introduce malicious code.
D:This checks promote exact verified artifact, not the named failure. Consistency prevents untested repackaging.
Question 590
A compromised dependency release appears under the expected package name. Independently, reviewers flag this potentially unsafe practice for assessment: 'Reinstall arbitrary newest dependencies during deployment'. Which verification addresses that practice without assuming it caused the incident?
- Compare dependency lock and artifact hash
- Inspect SBOM/advisory results and code changes
- Inspect locked dependencies and provenance
- Run package installation with full controller administrator secrets exposed
Explanation
Correct Answer
A:Deployment may differ from tested code. The intended behavior is: Consistency prevents untested repackaging.
Incorrect Answers
B:This checks scan package changes, not the named failure. A dependency update can change execution behavior.
C:This checks pin trusted dependency versions, not the named failure. Locking versions improves integrity and reproducibility.
D:Dependency code could misuse privileged secrets.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests