Arista ACE-S Automation (Foundations) study plan
Arista ACE-S Automation (Foundations) · Give each week a clear focus.
8 weeks · About 6 hours per week
Arista EOS and CloudVision Fundamentals
Map the EOS architecture: describe the sysdb, state and configuration models, and how CLI commands map to running-config vs startup-config
Configure and verify baseline EOS features on a virtual or lab device: management interface, users, AAA basics, and logging
Differentiate CloudVision's role (management plane aggregation, change control, telemetry) from device-level EOS configuration
Explain the CloudVision cluster components (CVP nodes, the telemetry/state pipeline, and how devices onboard via terminattr)
Your checkpoint
A one-page diagram plus written notes explaining the EOS-to-CloudVision relationship and the terminattr onboarding path, self-checked against EOS/CloudVision documentation
Arista EOS and CloudVision Fundamentals & Automation and Programmability Tooling
Practice EOS CLI configuration workflows: interfaces, VLANs, MLAG, and BGP, verifying each with show commands
Compare eAPI (JSON-RPC over HTTPS) with the CLI and with SNMP, listing when each is appropriate
Enable eAPI on a lab device and issue a working JSON-RPC request (e.g., run a show command) from curl or Python
Identify the EOS configuration session model (config sessions, rollback) and explain why it matters for automation safety
Your checkpoint
A working Python script that authenticates to eAPI and returns structured JSON output from at least two show commands
Automation and Programmability Tooling
Write Python using pyeapi or raw requests to configure and then verify an interface setting end to end
Distinguish idempotent vs non-idempotent automation and demonstrate a repeatable playbook or script run
Use a version-controlled repo (git) to store automation scripts with a README documenting usage
Explain the role of Ansible/collections for EOS and when to choose it over custom scripts
Your checkpoint
A git repository containing an idempotent script or playbook that configures and verifies at least one EOS feature, with run instructions
Automation and Programmability Tooling & CloudVision Automation and Provisioning Workflows
Describe CloudVision's change-control workflow: configlets, containers, tasks, and change approvals
Build a configlet and assign it to a container in a lab, then execute a change and confirm the task result
Explain device onboarding to CloudVision (terminattr, registration, and device tags) and list prerequisites
Compare CloudVision Studio/automation workflows with manual configlet assignment
Your checkpoint
A documented lab run: onboard (or simulate onboarding) a device, push a configlet via container, and capture the task log confirming success
CloudVision Automation and Provisioning Workflows
Use the CloudVision APIs (resource APIs and/or the cvprac library) to query device inventory and container membership programmatically
Automate a configlet deployment via API and verify the resulting change-control task status
Explain compliance and reconciliation: how CloudVision detects config drift and how to remediate it
Describe role-based access and change approval controls in CloudVision workflows
Your checkpoint
A script using cvprac (or raw REST calls) that lists devices, assigns a configlet to a container, and reports task completion status
Network Telemetry, Monitoring, and Observability
Explain the difference between streaming telemetry (push) and polling (SNMP/poll-based), and when each is used
Configure and verify an OpenConfig/gNMI or EOS streaming telemetry subscription on a lab device
Enumerate key telemetry metrics to monitor (interface counters, queue depth, CPU/memory, BGP session state)
Describe how CloudVision ingests and visualizes telemetry and where to find device health dashboards
Your checkpoint
A table of at least 10 telemetry metrics with their source (gNMI path or show command), meaning, and a sample alert threshold rationale
Network Telemetry, Monitoring, and Observability & Arista EOS and CloudVision Fundamentals
Interpret CloudVision telemetry dashboards and identify an anomaly from sample data
Write a basic alert/notification rule concept and explain event correlation in CloudVision
Review the EOS and CloudVision fundamentals you found weakest in weeks 1-2 and re-test those areas
Trace a device event from EOS log through telemetry to a CloudVision alert
Your checkpoint
A written incident walkthrough (one or two pages) tracing a simulated interface-down event from device log to CloudVision alert, with the telemetry and dashboard evidence described
Arista EOS and CloudVision Fundamentals & Automation and Programmability Tooling & CloudVision Automation and Provisioning Workflows & Network Telemetry, Monitoring, and Observability
Take a timed practice assessment across all four domains and score each domain separately
Re-study the two lowest-scoring domain areas and re-test them
Consolidate your scripts, notes, and lab outputs into a single reviewable study repository
Write a short summary of key commands, APIs, and workflows you will review the day before the exam
Your checkpoint
A scored practice assessment with domain breakdown and a remediation log showing improvement on your two weakest domains
Milestones
Week 2: Can explain EOS eAPI vs CLI vs SNMP and demonstrate a working JSON-RPC call returning structured output
Week 4: Can execute a CloudVision change-control workflow (configlet to container to task) and explain the approval model
Week 6: Can describe streaming telemetry vs polling and list the key metrics you would monitor, with configured subscription evidence
Week 8: Practice assessment shows at least 70% overall with no domain below 60% after remediation