100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 720
Traffic fails after renewal because an intermediate certificate was not installed. Independently, reviewers flag this potentially unsafe practice for assessment: 'Restart all critical API gateways blindly without handshake tests'. Which verification addresses that practice without assuming it caused the incident?
- Inspect pre/post handshake success and rollback readiness
- Inspect served chain and issuer sequence
- Inspect expiry inventory and alert lead time
- Reuse the server private key as a shared client identity for every device
Explanation
Correct Answer
A:Widespread failures can result. The intended behavior is: Trust-path changes need compatibility checks.
Incorrect Answers
B:This checks validate renewal chain, not the named failure. Chain completeness is required for trust.
C:This checks monitor expiry, not the named failure. Early notice prevents surprise outages.
D:Shared identity undermines attribution.
Question 721
A service account configures branch ACLs through a protected CI pipeline. The specific implementation objective is to remove embedded credentials. Which configuration best meets the stated requirement?
- Delete token string from newest commit and consider exposure resolved
- Enable HTTP debugging that prints Authorization headers to a shared console
- Use one unrestricted admin token across monitoring and deployment
- Use a trusted secret manager or protected job variables for runtime retrieval
Explanation
Correct Answer
D:Centralized secret controls reduce exposure.
Incorrect Answers
A:Old revisions and copied tokens may remain usable.
B:Logs may become an attack vector.
C:Shared broad credentials widen impact.
Question 722
A service account configures branch ACLs through a protected CI pipeline. The specific implementation objective is to rotate compromised tokens. Which design action is most appropriate for this case?
- Enable HTTP debugging that prints Authorization headers to a shared console
- Keep API secrets in ordinary committed configuration files
- Use one unrestricted admin token across monitoring and deployment
- Revoke exposed credentials and issue scoped replacements under change control
Explanation
Correct Answer
D:Removing text alone does not revoke active tokens.
Incorrect Answers
A:Logs may become an attack vector.
B:Repository history can disclose credentials.
C:Shared broad credentials widen impact.
Question 723
A service account configures branch ACLs through a protected CI pipeline. The specific implementation objective is to minimize privilege. What should the engineer implement for this specific objective?
- Delete token string from newest commit and consider exposure resolved
- Keep API secrets in ordinary committed configuration files
- Give each service identity only the supported commands and resource scope it needs
- Enable HTTP debugging that prints Authorization headers to a shared console
Explanation
Correct Answer
C:Least privilege limits compromise impact.
Incorrect Answers
A:Old revisions and copied tokens may remain usable.
B:Repository history can disclose credentials.
D:Logs may become an attack vector.
Question 724
A service account configures branch ACLs through a protected CI pipeline. The specific implementation objective is to avoid log leaks. Which adjustment would satisfy this particular constraint?
- Use one unrestricted admin token across monitoring and deployment
- Delete token string from newest commit and consider exposure resolved
- Keep API secrets in ordinary committed configuration files
- Redact auth headers, secrets and encoded credentials from all diagnostics
Explanation
Correct Answer
D:Central logging often has wider readership than vault.
Incorrect Answers
A:Shared broad credentials widen impact.
B:Old revisions and copied tokens may remain usable.
C:Repository history can disclose credentials.
Question 725
A service account configures branch ACLs through a protected CI pipeline. The deployment plan must both (1) remove embedded credentials and (2) minimize privilege. Which TWO actions together satisfy those requirements? Choose TWO.
- Enable HTTP debugging that prints Authorization headers to a shared console
- Keep API secrets in ordinary committed configuration files
- Delete token string from newest commit and consider exposure resolved
- Use a trusted secret manager or protected job variables for runtime retrieval
- Give each service identity only the supported commands and resource scope it needs
Explanation
Correct Answers
D:Centralized secret controls reduce exposure.
E:Least privilege limits compromise impact.
Incorrect Answers
A:Logs may become an attack vector.
B:Repository history can disclose credentials.
C:Old revisions and copied tokens may remain usable.
Question 726
A service account configures branch ACLs through a protected CI pipeline. Three conditions must be met: (1) remove embedded credentials; (2) rotate compromised tokens; and (3) avoid log leaks. Which THREE actions form the narrowest complete plan? Choose THREE.
- Redact auth headers, secrets and encoded credentials from all diagnostics
- Use a trusted secret manager or protected job variables for runtime retrieval
- Keep API secrets in ordinary committed configuration files
- Enable HTTP debugging that prints Authorization headers to a shared console
- Revoke exposed credentials and issue scoped replacements under change control
- Use one unrestricted admin token across monitoring and deployment
Explanation
Correct Answers
A:Central logging often has wider readership than vault.
B:Centralized secret controls reduce exposure.
E:Removing text alone does not revoke active tokens.
Incorrect Answers
C:Repository history can disclose credentials.
D:Logs may become an attack vector.
F:Shared broad credentials widen impact.
Question 727
A contractor finds production tokens hard-coded into a YAML file committed months ago. Independently, reviewers flag this potentially unsafe practice for assessment: 'Keep API secrets in ordinary committed configuration files'. Which inspection most directly evaluates that practice?
- Use one unrestricted admin token across monitoring and deployment
- Review revocation and token-use logs
- Inspect config and commit history
- Inspect sanitized request traces
Explanation
Correct Answer
C:Repository history can disclose credentials. The intended behavior is: Centralized secret controls reduce exposure.
Incorrect Answers
A:Shared broad credentials widen impact.
B:This checks rotate compromised tokens, not the named failure. Removing text alone does not revoke active tokens.
D:This checks avoid log leaks, not the named failure. Central logging often has wider readership than vault.
Question 728
A contractor finds production tokens hard-coded into a YAML file committed months ago. Independently, reviewers flag this potentially unsafe practice for assessment: 'Delete token string from newest commit and consider exposure resolved'. What diagnostic evidence should first be collected to assess that practice?
- Use one unrestricted admin token across monitoring and deployment
- Inspect config and commit history
- Inspect sanitized request traces
- Review revocation and token-use logs
Explanation
Correct Answer
D:Old revisions and copied tokens may remain usable. The intended behavior is: Removing text alone does not revoke active tokens.
Incorrect Answers
A:Shared broad credentials widen impact.
B:This checks remove embedded credentials, not the named failure. Centralized secret controls reduce exposure.
C:This checks avoid log leaks, not the named failure. Central logging often has wider readership than vault.
Question 729
A contractor finds production tokens hard-coded into a YAML file committed months ago. Independently, reviewers flag this potentially unsafe practice for assessment: 'Use one unrestricted admin token across monitoring and deployment'. Which focused check best tests this specific assumption?
- Keep API secrets in ordinary committed configuration files
- Review revocation and token-use logs
- Inspect role scopes and API permissions
- Inspect sanitized request traces
Explanation
Correct Answer
C:Shared broad credentials widen impact. The intended behavior is: Least privilege limits compromise impact.
Incorrect Answers
A:Repository history can disclose credentials.
B:This checks rotate compromised tokens, not the named failure. Removing text alone does not revoke active tokens.
D:This checks avoid log leaks, not the named failure. Central logging often has wider readership than vault.
Question 730
A contractor finds production tokens hard-coded into a YAML file committed months ago. Independently, reviewers flag this potentially unsafe practice for assessment: 'Enable HTTP debugging that prints Authorization headers to a shared console'. Which verification addresses that practice without assuming it caused the incident?
- Inspect sanitized request traces
- Inspect config and commit history
- Delete token string from newest commit and consider exposure resolved
- Inspect role scopes and API permissions
Explanation
Correct Answer
A:Logs may become an attack vector. The intended behavior is: Central logging often has wider readership than vault.
Incorrect Answers
B:This checks remove embedded credentials, not the named failure. Centralized secret controls reduce exposure.
C:Old revisions and copied tokens may remain usable.
D:This checks minimize privilege, not the named failure. Least privilege limits compromise impact.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests