Infrastructure and Automation
350-901 · 60 questions
- Operations wants continuous interface counters from IOS XE civic edge routers without walking MIBs on a timer. Which statement correctly describes model-driven telemetry versus classic polling?
- A network team enables a telemetry subscription toward a host that cannot decode the YANG model or encoding in use. Publications leave the router but nothing useful is stored. Which consumption consideration was missed?
- Cadence telemetry from dozens of civic routers produces timestamped counter samples. Which storage consideration fits model-driven telemetry consumption?
- An IOS XE edge router is configured with a telemetry subscription that names a collector receiver. Which statement describes that configured (dial-out) consumption topology?
- A collector opens a dynamic (dial-in) telemetry subscription to an IOS XE device. After the collector disconnects and the device reloads, no stream resumes until the collector returns. What consumption trait does this illustrate?
- Engineers must choose telemetry publication style for interface counters to graph and for interface admin-state that should wake a consumer only when it flips. Which consumption choice is appropriate?
- High-cadence subscriptions across a large civic router fleet begin filling the telemetry store within days. Which storage consideration should the team address?
- A developer enables a telemetry subscription that streams an entire operational YANG tree “in case we need it later,” though the app only graphs two interface counters. Which consumption consideration applies?
- A proposal claims civic IOS XE switches will “run Grafana themselves” for model-driven telemetry without a separate receiver or store. Which correction reflects proper MDT pipeline roles?
- Study notes list dial-in and dial-out transport names from IOS XE model-driven telemetry docs. For a DEVCOR-style item on telemetry consumption and storage, what should remain the scored focus?
- A municipal network team must push YANG-modeled configuration to a Catalyst switch running IOS XE without opening an interactive SSH session. Which approach correctly uses the official device-config API for this DEVCOR task?
- A city automation script PATCHes an IOS XE interface over RESTCONF. Which Accept/Content-Type media type matches the official YANG-data exchange?
- A parks IT developer must edit interface configuration on an IOS XE switch via RESTCONF. Which URI family is the correct datastore root for that edit?
- A municipal script must change only the description leaf on an existing IOS XE interface without replacing the whole interface resource. Which RESTCONF HTTP verb matches that intent?
- City hall needs GigabitEthernet1/0/10 given an IPv4 address and description through RESTCONF on IOS XE. What is the correct construction focus?
- A developer builds a RESTCONF URI for an IOS XE interface. The device exposes both IETF interfaces and Cisco-IOS-XE-native models. Which practice keeps the request valid?
- Operations wants GigabitEthernet1/0/5 administratively shut and a new description applied on an IOS XE switch via RESTCONF. Which statement is correct?
- A RESTCONF PATCH must update only Loopback100 on an IOS XE router. How should the target interface be identified?
- A library branch needs a static route added on an IOS XE edge router through RESTCONF. Which payload content matches the official static-route resource idea?
- Transit staff must remove a previously added static route on an IOS XE router using RESTCONF. Which action is correct?
- A DEVCOR practice item asks how to add one intended route on IOS XE with RESTCONF. Which answer stays in scope?
- A RESTCONF static-route create on IOS XE includes only 10.40.0.0/16 in the body and omits how packets leave. What is missing for a complete edit?
- City Wi-Fi segregation requires VLAN 40 created on an IOS XE access switch through the official RESTCONF API. Which construction is correct?
- When addressing a VLAN over RESTCONF on IOS XE, what role does the VLAN identifier play versus the display name?
- A DEVCOR item asks how to configure a VLAN object on IOS XE with RESTCONF. Which response stays on the scored idea?
- Blueprint task 5.2 names IOS XE for RESTCONF device configuration. A candidate proposes NX-OS or IOS XR REST as the correct target. Why is that wrong for this item?
- Municipal automation must construct an Ansible workflow that configures network parameters on IOS XE switches. Which artifact matches the intended playbook workflow?
- A playbook must set an interface description, ensure VLAN 20 exists, and add a static route on IOS XE. Which task approach best matches DEVCOR 5.3.a construction?
- A city Ansible play targets group accessswitches, but the repository has no inventory or dynamic source listing those hosts. What is wrong?
- The same Ansible play must configure VLAN ids and interface names for two library sites. Where should that site-specific data live for reuse?
- Operators rerun an Ansible play that should ensure one static route exists on each IOS XE edge. A task always appends the route CLI blindly. What problem does that create?
- Before applying VLAN and interface changes, the city NOC wants operators to preview what Ansible would change. Which approach fits the 5.3.a Ansible workflow?
- How does a typical Ansible-to-IOS-XE playbook workflow reach the switches in DEVCOR 5.3.a?
- A play creates an SVI-style interface that depends on VLAN 55. Which task ordering reflects a correctly constructed Ansible workflow?
- A fair DEVCOR 5.3.a practice item about Ansible network parameters should ask which kind of judgment?
- A municipal campus team must push IOS XE interface and VLAN changes with an agentless playbook that SSHes existing switches. Which tool matches official DEVCOR 5.3.a construction?
- Public-works networking wants IOS XE VLANs and static routes expressed as desired resources rather than an interactive SSH script. Which approach matches Terraform for DEVCOR 5.3.b?
- A city edge stack’s Terraform root lists VLAN and interface resources for IOS XE but never configures how Terraform authenticates to the device. What is missing from the constructed workflow?
- Before changing campus IOS XE routes with Terraform, change control wants a preview of creates, updates, and destroys. Which workflow order satisfies that review?
- After applying VLANs with Terraform, an engineer deletes the state file and runs apply again against the same HCL. What role does state play that this action risks breaking?
- A parks-and-rec access layer needs a new SVI VLAN and a static route declared in Terraform for IOS XE. Which construction matches the intended 5.3.b resources?
- Terraform already owns VLAN 40 on a library branch switch. Operations needs the VLAN renamed. What is the correct Terraform workflow change path?
- Blueprint task 5.3.b asks the team to construct a workflow that configures network parameters with the official v1.1 tool. Which tool is correct?
- The official DEVCOR lab runs Terraform from GitLab CI/CD against IOS XE. A question asks what the 5.3.b construction actually is. What is the right focus?
- A temporary guest VLAN resource must leave a civic center switch that Terraform owns. How should deprovisioning be done in the Terraform workflow?
- A fair DEVCOR item asks which Terraform piece solves a stated need for an IOS XE static route. What kind of answer should candidates expect?
- Requirements: agentless SSH to a large existing IOS XE estate and reuse of a mature play library. Which configuration-management choice best matches that technical constraint?
- Change advisory requires a human-readable plan file of creates/changes/destroys before any VLAN push, and the team will accept a short ramp on a new tool. Which pick best matches that business constraint?
- Transit ops already has hundreds of working Ansible plays and trained operators; leadership asks whether to rip-and-replace with Terraform next quarter for the same VLAN work. What does 5.4 emphasize?
- The stated requirement is: show the delta, then apply, and keep a state file of owned IOS XE objects. Which CM solution identification fits 5.4?
- Requirements: no agent on the device, reuse existing SSH reachability, and express changes as ordered tasks in plays. Which tool identification matches?
- When identifying a configuration-management solution on this DEVCOR v1.1 bank, how should Puppet be treated relative to Ansible and Terraform?
- A water-utility edge switch must run a small monitoring app on the network device itself. Which framework provides that on-box application hosting?
- Official DEVCOR 5.5 names which switch family as a platform that can host applications on the device (alongside other IOx-enabled devices)?
- Operators want a Linux environment on a Catalyst 9000 for scripts and tools without treating Python as an IOS process on the ASIC. What is Guest Shell?
- A new Catalyst 9000 app-hosting attempt fails because IOx services never started. What prerequisite do official hosting docs emphasize?
- IOx is enabled on a Catalyst 9000, but a networked Guest Shell app still has no reachability. What hosting interface concept is missing?
- From a supported IOS XE generation, the team wants a Docker-style app to run on the Catalyst through IOx. What is the 5.5 idea?
- A Catalyst 9000 has only bootflash available. Operators want to host several additional Docker apps beyond Guest Shell. What storage constraint applies?
- A city wants edge scripts and on-device automation to run local to each Catalyst 9000 rather than only in a central VM. What does DEVCOR 5.5 emphasize?