100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 591
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. The specific implementation objective is to use advertised schema revisions. Which configuration best meets the stated requirement?
- Mark every compiled payload deployed before sending it
- Select modules and revisions actually implemented by each target
- Embed vendor-specific keys into every upstream business record
- Treat successful JSON serialization as full model validation
Explanation
Correct Answer
B:Model availability varies by platform release.
Incorrect Answers
A:Generation is not delivery.
C:Tight coupling makes cross-platform changes fragile.
D:JSON syntax does not verify YANG validity.
Question 592
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. The specific implementation objective is to validate node constraints. Which design action is most appropriate for this case?
- Embed vendor-specific keys into every upstream business record
- Compile only against a newer lab schema for all devices
- Mark every compiled payload deployed before sending it
- Enforce mandatory keys, ranges and if-feature conditions
Explanation
Correct Answer
D:Schema constraints exist beyond JSON syntax.
Incorrect Answers
A:Tight coupling makes cross-platform changes fragile.
B:Older devices may reject unsupported nodes.
C:Generation is not delivery.
Question 593
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. The specific implementation objective is to separate intent from encoding. What should the engineer implement for this specific objective?
- Treat successful JSON serialization as full model validation
- Keep business intent normalized before rendering platform-specific shapes
- Compile only against a newer lab schema for all devices
- Mark every compiled payload deployed before sending it
Explanation
Correct Answer
B:Clear separation supports multiple device families.
Incorrect Answers
A:JSON syntax does not verify YANG validity.
C:Older devices may reject unsupported nodes.
D:Generation is not delivery.
Question 594
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. The specific implementation objective is to read back operational data. Which adjustment would satisfy this particular constraint?
- Treat successful JSON serialization as full model validation
- Confirm effective leaf values and device-side errors after submission
- Embed vendor-specific keys into every upstream business record
- Compile only against a newer lab schema for all devices
Explanation
Correct Answer
B:Device acceptance and intended operation must agree.
Incorrect Answers
A:JSON syntax does not verify YANG validity.
C:Tight coupling makes cross-platform changes fragile.
D:Older devices may reject unsupported nodes.
Question 595
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. The deployment plan must both (1) validate node constraints and (2) read back operational data. Which TWO actions together satisfy those requirements? Choose TWO.
- Mark every compiled payload deployed before sending it
- Compile only against a newer lab schema for all devices
- Confirm effective leaf values and device-side errors after submission
- Treat successful JSON serialization as full model validation
- Enforce mandatory keys, ranges and if-feature conditions
Explanation
Correct Answers
C:Device acceptance and intended operation must agree.
E:Schema constraints exist beyond JSON syntax.
Incorrect Answers
A:Generation is not delivery.
B:Older devices may reject unsupported nodes.
D:JSON syntax does not verify YANG validity.
Question 596
A Python compiler converts YANG paths into device-specific JSON config for VLAN and interface provisioning. Three conditions must be met: (1) validate node constraints; (2) separate intent from encoding; and (3) read back operational data. Which THREE actions form the narrowest complete plan? Choose THREE.
- Embed vendor-specific keys into every upstream business record
- Keep business intent normalized before rendering platform-specific shapes
- Compile only against a newer lab schema for all devices
- Treat successful JSON serialization as full model validation
- Enforce mandatory keys, ranges and if-feature conditions
- Confirm effective leaf values and device-side errors after submission
Explanation
Correct Answers
B:Clear separation supports multiple device families.
E:Schema constraints exist beyond JSON syntax.
F:Device acceptance and intended operation must agree.
Incorrect Answers
A:Tight coupling makes cross-platform changes fragile.
C:Older devices may reject unsupported nodes.
D:JSON syntax does not verify YANG validity.
Question 597
The generated payload contains a field supported by the model but not the target device release. Independently, reviewers flag this potentially unsafe practice for assessment: 'Compile only against a newer lab schema for all devices'. Which inspection most directly evaluates that practice?
- Inspect API response and operational state
- Treat successful JSON serialization as full model validation
- Review source-of-truth versus output model
- Inspect target module revision
Explanation
Correct Answer
D:Older devices may reject unsupported nodes. The intended behavior is: Model availability varies by platform release.
Incorrect Answers
A:This checks read back operational data, not the named failure. Device acceptance and intended operation must agree.
B:JSON syntax does not verify YANG validity.
C:This checks separate intent from encoding, not the named failure. Clear separation supports multiple device families.
Question 598
The generated payload contains a field supported by the model but not the target device release. Independently, reviewers flag this potentially unsafe practice for assessment: 'Treat successful JSON serialization as full model validation'. What diagnostic evidence should first be collected to assess that practice?
- Inspect validation errors
- Inspect API response and operational state
- Compile only against a newer lab schema for all devices
- Review source-of-truth versus output model
Explanation
Correct Answer
A:JSON syntax does not verify YANG validity. The intended behavior is: Schema constraints exist beyond JSON syntax.
Incorrect Answers
B:This checks read back operational data, not the named failure. Device acceptance and intended operation must agree.
C:Older devices may reject unsupported nodes.
D:This checks separate intent from encoding, not the named failure. Clear separation supports multiple device families.
Question 599
The generated payload contains a field supported by the model but not the target device release. Independently, reviewers flag this potentially unsafe practice for assessment: 'Embed vendor-specific keys into every upstream business record'. Which focused check best tests this specific assumption?
- Mark every compiled payload deployed before sending it
- Inspect target module revision
- Inspect validation errors
- Review source-of-truth versus output model
Explanation
Correct Answer
D:Tight coupling makes cross-platform changes fragile. The intended behavior is: Clear separation supports multiple device families.
Incorrect Answers
A:Generation is not delivery.
B:This checks use advertised schema revisions, not the named failure. Model availability varies by platform release.
C:This checks validate node constraints, not the named failure. Schema constraints exist beyond JSON syntax.
Question 600
The generated payload contains a field supported by the model but not the target device release. Independently, reviewers flag this potentially unsafe practice for assessment: 'Mark every compiled payload deployed before sending it'. Which verification addresses that practice without assuming it caused the incident?
- Inspect API response and operational state
- Inspect validation errors
- Compile only against a newer lab schema for all devices
- Review source-of-truth versus output model
Explanation
Correct Answer
A:Generation is not delivery. The intended behavior is: Device acceptance and intended operation must agree.
Incorrect Answers
B:This checks validate node constraints, not the named failure. Schema constraints exist beyond JSON syntax.
C:Older devices may reject unsupported nodes.
D:This checks separate intent from encoding, not the named failure. Clear separation supports multiple device families.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests