Data Center Automation, Orchestration, and Management
Domain 5 - Data Center Automation, Orchestration, and Management
This domain tests intent-based automation, configuration management, telemetry, and lifecycle operations for Juniper data center fabrics. Expect Apstra, Junos PyEZ, NETCONF/YANG, REST, ZTP, and streaming telemetry.
Core rules
- Apstra is intent-based: you describe the desired blueprint (roles, tags, policies), and Apstra renders device configurations and continuously validates against intent. It is not a one-time template push.
- Junos supports NETCONF, REST, gNMI, and Junos PyEZ. YANG models define the data; commit confirmed and rollback are safety mechanisms.
- ZTP uses DHCP options to deliver an image and configuration; secure it with signed images and restricted management access.
- Streaming telemetry (JTI or gNMI) is push-based and more scalable than periodic SNMP polling.
- Treat automation as idempotent and test in a lab; validate post-change state, not just successful configuration commit.
Worked example
A new QFX leaf boots with no configuration. DHCP options point to a ZTP server. The device fetches a signed Junos image, installs it, then retrieves a bootstrap configuration that sets management addressing and an Apstra agent. Apstra discovers the device, assigns it to a blueprint, and renders the leaf role. Validation checks BGP sessions and EVPN routes. If the bootstrap configuration is wrong, the device remains reachable via console and the ZTP process is logged.
Traps
- Equating orchestration with templating; Apstra continuously validates intent.
- Forgetting idempotency in scripts.
- Pushing changes without commit confirmed.
- Relying on SNMP polling for high-scale telemetry.
- Leaving ZTP unauthenticated.