100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 420
A merge request triggers production deployment overnight because workflow rules are too broad. Independently, reviewers flag this potentially unsafe practice for assessment: 'Treat any successful CI run as an approved maintenance action'. Which verification addresses that practice without assuming it caused the incident?
- Disable all CI on development branches because deployment is restricted
- Inspect change window and job timestamps
- Inspect workflow rules and job rules
- Check protected environment approval record
Explanation
Correct Answer
B:Execution does not equal authorization. The intended behavior is: Auditability matters for network changes.
Incorrect Answers
A:Missing early tests delays defect detection.
C:This checks restrict trigger conditions, not the named failure. Branch and event conditions bound automated actions.
D:This checks require human authorization, not the named failure. High-impact changes need accountable approval.
Question 421
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. The specific implementation objective is to separate protected secret scope. Which configuration best meets the stated requirement?
- Mark production secrets protected and limit them to trusted branches/runners
- Print environment variables to troubleshoot a failed network job
- Give lint and test jobs full production administrator rights
- Commit a permanent admin password to .gitlab-ci.yml
Explanation
Correct Answer
A:Trust boundaries restrict credential exposure.
Incorrect Answers
B:Raw environment dumps can reveal secrets.
C:Excess privilege increases CI compromise blast radius.
D:Repository history preserves sensitive secrets.
Question 422
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. The specific implementation objective is to mask sensitive values. Which design action is most appropriate for this case?
- Commit a permanent admin password to .gitlab-ci.yml
- Expose production credentials to arbitrary merge request pipelines
- Give lint and test jobs full production administrator rights
- Use available masked/hidden variable controls and avoid printing credentials
Explanation
Correct Answer
D:Log masking reduces incidental leakage but is not complete protection.
Incorrect Answers
A:Repository history preserves sensitive secrets.
B:Untrusted MR code could exfiltrate secrets.
C:Excess privilege increases CI compromise blast radius.
Question 423
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. The specific implementation objective is to prefer short-lived credentials. What should the engineer implement for this specific objective?
- Print environment variables to troubleshoot a failed network job
- Retrieve temporary tokens from a trusted vault or identity integration
- Expose production credentials to arbitrary merge request pipelines
- Give lint and test jobs full production administrator rights
Explanation
Correct Answer
B:Credential duration narrows compromise window.
Incorrect Answers
A:Raw environment dumps can reveal secrets.
C:Untrusted MR code could exfiltrate secrets.
D:Excess privilege increases CI compromise blast radius.
Question 424
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. The specific implementation objective is to separate job permissions. Which adjustment would satisfy this particular constraint?
- Expose production credentials to arbitrary merge request pipelines
- Use read-only credentials for prevalidation and write rights only for authorized deploy
- Commit a permanent admin password to .gitlab-ci.yml
- Print environment variables to troubleshoot a failed network job
Explanation
Correct Answer
B:Not every stage needs mutation privilege.
Incorrect Answers
A:Untrusted MR code could exfiltrate secrets.
C:Repository history preserves sensitive secrets.
D:Raw environment dumps can reveal secrets.
Question 425
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. The deployment plan must both (1) separate protected secret scope and (2) prefer short-lived credentials. Which TWO actions together satisfy those requirements? Choose TWO.
- Give lint and test jobs full production administrator rights
- Expose production credentials to arbitrary merge request pipelines
- Mark production secrets protected and limit them to trusted branches/runners
- Print environment variables to troubleshoot a failed network job
- Retrieve temporary tokens from a trusted vault or identity integration
Explanation
Correct Answers
C:Trust boundaries restrict credential exposure.
E:Credential duration narrows compromise window.
Incorrect Answers
A:Excess privilege increases CI compromise blast radius.
B:Untrusted MR code could exfiltrate secrets.
D:Raw environment dumps can reveal secrets.
Question 426
A pipeline deploys RESTCONF config to network devices through a protected GitLab runner. Three conditions must be met: (1) separate protected secret scope; (2) mask sensitive values; and (3) separate job permissions. Which THREE actions form the narrowest complete plan? Choose THREE.
- Use available masked/hidden variable controls and avoid printing credentials
- Use read-only credentials for prevalidation and write rights only for authorized deploy
- Print environment variables to troubleshoot a failed network job
- Give lint and test jobs full production administrator rights
- Mark production secrets protected and limit them to trusted branches/runners
- Commit a permanent admin password to .gitlab-ci.yml
Explanation
Correct Answers
A:Log masking reduces incidental leakage but is not complete protection.
B:Not every stage needs mutation privilege.
E:Trust boundaries restrict credential exposure.
Incorrect Answers
C:Raw environment dumps can reveal secrets.
D:Excess privilege increases CI compromise blast radius.
F:Repository history preserves sensitive secrets.
Question 427
A debug job echoes secret variables into logs that can be read by general project users. Independently, reviewers flag this potentially unsafe practice for assessment: 'Expose production credentials to arbitrary merge request pipelines'. Which inspection most directly evaluates that practice?
- Commit a permanent admin password to .gitlab-ci.yml
- Inspect job trace redaction
- Review credentials per job stage
- Inspect protected variable availability
Explanation
Correct Answer
D:Untrusted MR code could exfiltrate secrets. The intended behavior is: Trust boundaries restrict credential exposure.
Incorrect Answers
A:Repository history preserves sensitive secrets.
B:This checks mask sensitive values, not the named failure. Log masking reduces incidental leakage but is not complete protection.
C:This checks separate job permissions, not the named failure. Not every stage needs mutation privilege.
Question 428
A debug job echoes secret variables into logs that can be read by general project users. Independently, reviewers flag this potentially unsafe practice for assessment: 'Print environment variables to troubleshoot a failed network job'. What diagnostic evidence should first be collected to assess that practice?
- Inspect job trace redaction
- Review credentials per job stage
- Commit a permanent admin password to .gitlab-ci.yml
- Inspect protected variable availability
Explanation
Correct Answer
A:Raw environment dumps can reveal secrets. The intended behavior is: Log masking reduces incidental leakage but is not complete protection.
Incorrect Answers
B:This checks separate job permissions, not the named failure. Not every stage needs mutation privilege.
C:Repository history preserves sensitive secrets.
D:This checks separate protected secret scope, not the named failure. Trust boundaries restrict credential exposure.
Question 429
A debug job echoes secret variables into logs that can be read by general project users. Independently, reviewers flag this potentially unsafe practice for assessment: 'Commit a permanent admin password to .gitlab-ci.yml'. Which focused check best tests this specific assumption?
- Review credentials per job stage
- Print environment variables to troubleshoot a failed network job
- Inspect protected variable availability
- Inspect secret source and lifetime
Explanation
Correct Answer
D:Repository history preserves sensitive secrets. The intended behavior is: Credential duration narrows compromise window.
Incorrect Answers
A:This checks separate job permissions, not the named failure. Not every stage needs mutation privilege.
B:Raw environment dumps can reveal secrets.
C:This checks separate protected secret scope, not the named failure. Trust boundaries restrict credential exposure.
Question 430
A debug job echoes secret variables into logs that can be read by general project users. Independently, reviewers flag this potentially unsafe practice for assessment: 'Give lint and test jobs full production administrator rights'. Which verification addresses that practice without assuming it caused the incident?
- Review credentials per job stage
- Expose production credentials to arbitrary merge request pipelines
- Inspect secret source and lifetime
- Inspect job trace redaction
Explanation
Correct Answer
A:Excess privilege increases CI compromise blast radius. The intended behavior is: Not every stage needs mutation privilege.
Incorrect Answers
B:Untrusted MR code could exfiltrate secrets.
C:This checks prefer short-lived credentials, not the named failure. Credential duration narrows compromise window.
D:This checks mask sensitive values, not the named failure. Log masking reduces incidental leakage but is not complete protection.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests