100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 410
The deployment executes an old plan because an artifact path selected the prior pipeline output. Independently, reviewers flag this potentially unsafe practice for assessment: 'Ignore checksum mismatch because file names match'. Which verification addresses that practice without assuming it caused the incident?
- Inspect artifact name and producer job ID
- Compare approved hash and deployed file
- Inspect artifact access and secret redaction
- Reference an artifact from an unrelated project without verification
Explanation
Correct Answer
B:Names do not establish content integrity. The intended behavior is: The deployed bytes must match reviewed bytes.
Incorrect Answers
A:This checks name the reviewed artifact, not the named failure. Stable build identity avoids stale plan selection.
C:This checks restrict artifact access, not the named failure. Network plans may reveal internal topology.
D:Untrusted inputs can change infrastructure.
Question 411
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. The specific implementation objective is to restrict trigger conditions. Which configuration best meets the stated requirement?
- Make destructive device changes an automatic first stage
- Disable all CI on development branches because deployment is restricted
- Treat any successful CI run as an approved maintenance action
- Use rules that keep production deployment on approved refs and change conditions
Explanation
Correct Answer
D:Branch and event conditions bound automated actions.
Incorrect Answers
A:Missing review bypasses risk controls.
B:Missing early tests delays defect detection.
C:Execution does not equal authorization.
Question 412
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. The specific implementation objective is to require human authorization. Which design action is most appropriate for this case?
- Treat any successful CI run as an approved maintenance action
- Deploy to production on every commit to any branch
- Put an approval or manual production job at the appropriate gate
- Disable all CI on development branches because deployment is restricted
Explanation
Correct Answer
C:High-impact changes need accountable approval.
Incorrect Answers
A:Execution does not equal authorization.
B:Unreviewed commits can trigger outage.
D:Missing early tests delays defect detection.
Question 413
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. The specific implementation objective is to keep test execution automatic. What should the engineer implement for this specific objective?
- Run safe validation on ordinary merge requests while withholding live mutation
- Treat any successful CI run as an approved maintenance action
- Deploy to production on every commit to any branch
- Make destructive device changes an automatic first stage
Explanation
Correct Answer
A:Automated testing is useful without deployment rights.
Incorrect Answers
B:Execution does not equal authorization.
C:Unreviewed commits can trigger outage.
D:Missing review bypasses risk controls.
Question 414
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. The specific implementation objective is to record deployment window. Which adjustment would satisfy this particular constraint?
- Deploy to production on every commit to any branch
- Disable all CI on development branches because deployment is restricted
- Make destructive device changes an automatic first stage
- Associate the executed job with authorized time and change ticket
Explanation
Correct Answer
D:Auditability matters for network changes.
Incorrect Answers
A:Unreviewed commits can trigger outage.
B:Missing early tests delays defect detection.
C:Missing review bypasses risk controls.
Question 415
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. The deployment plan must both (1) require human authorization and (2) record deployment window. Which TWO actions together satisfy those requirements? Choose TWO.
- Put an approval or manual production job at the appropriate gate
- Disable all CI on development branches because deployment is restricted
- Associate the executed job with authorized time and change ticket
- Treat any successful CI run as an approved maintenance action
- Make destructive device changes an automatic first stage
Explanation
Correct Answers
A:High-impact changes need accountable approval.
C:Auditability matters for network changes.
Incorrect Answers
B:Missing early tests delays defect detection.
D:Execution does not equal authorization.
E:Missing review bypasses risk controls.
Question 416
A pipeline is approved to alter data-center configuration only during a staffed maintenance window. Three conditions must be met: (1) require human authorization; (2) keep test execution automatic; and (3) record deployment window. Which THREE actions form the narrowest complete plan? Choose THREE.
- Associate the executed job with authorized time and change ticket
- Treat any successful CI run as an approved maintenance action
- Make destructive device changes an automatic first stage
- Deploy to production on every commit to any branch
- Put an approval or manual production job at the appropriate gate
- Run safe validation on ordinary merge requests while withholding live mutation
Explanation
Correct Answers
A:Auditability matters for network changes.
E:High-impact changes need accountable approval.
F:Automated testing is useful without deployment rights.
Incorrect Answers
B:Execution does not equal authorization.
C:Missing review bypasses risk controls.
D:Unreviewed commits can trigger outage.
Question 417
A merge request triggers production deployment overnight because workflow rules are too broad. Independently, reviewers flag this potentially unsafe practice for assessment: 'Deploy to production on every commit to any branch'. Which inspection most directly evaluates that practice?
- Disable all CI on development branches because deployment is restricted
- Check protected environment approval record
- Inspect change window and job timestamps
- Inspect workflow rules and job rules
Explanation
Correct Answer
D:Unreviewed commits can trigger outage. The intended behavior is: Branch and event conditions bound automated actions.
Incorrect Answers
A:Missing early tests delays defect detection.
B:This checks require human authorization, not the named failure. High-impact changes need accountable approval.
C:This checks record deployment window, not the named failure. Auditability matters for network changes.
Question 418
A merge request triggers production deployment overnight because workflow rules are too broad. Independently, reviewers flag this potentially unsafe practice for assessment: 'Make destructive device changes an automatic first stage'. What diagnostic evidence should first be collected to assess that practice?
- Inspect MR test-stage status
- Check protected environment approval record
- Deploy to production on every commit to any branch
- Inspect change window and job timestamps
Explanation
Correct Answer
B:Missing review bypasses risk controls. The intended behavior is: High-impact changes need accountable approval.
Incorrect Answers
A:This checks keep test execution automatic, not the named failure. Automated testing is useful without deployment rights.
C:Unreviewed commits can trigger outage.
D:This checks record deployment window, not the named failure. Auditability matters for network changes.
Question 419
A merge request triggers production deployment overnight because workflow rules are too broad. Independently, reviewers flag this potentially unsafe practice for assessment: 'Disable all CI on development branches because deployment is restricted'. Which focused check best tests this specific assumption?
- Inspect change window and job timestamps
- Inspect MR test-stage status
- Check protected environment approval record
- Deploy to production on every commit to any branch
Explanation
Correct Answer
B:Missing early tests delays defect detection. The intended behavior is: Automated testing is useful without deployment rights.
Incorrect Answers
A:This checks record deployment window, not the named failure. Auditability matters for network changes.
C:This checks require human authorization, not the named failure. High-impact changes need accountable approval.
D:Unreviewed commits can trigger outage.
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.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests