ENAUTO 300-435 flashcards
ENAUTO 300-435 · Build recall with a focused review session.
36 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Idempotent HTTP methods
- GET, PUT, and DELETE are idempotent: repeating the same request leaves the resource in the same state. POST is not idempotent because it typically creates a new resource or triggers an action each time.
- Declarative vs imperative
- Declarative automation states the desired end state and lets the tool decide the steps, enabling idempotency. Imperative automation lists explicit steps in order and can reapply changes unintentionally.
- HTTP 401 vs 403
- 401 Unauthorized means credentials are missing or invalid, so authentication failed. 403 Forbidden means the client authenticated successfully but lacks permission for the requested resource or operation.
- Git staging area
- The index between working tree and repository. git add copies changes into the index, git commit records the index as a snapshot, and git push publishes commits to a remote repository.
- JSON data types
- JSON supports objects (key-value maps), arrays, strings, numbers, booleans true and false, and null. It does not support comments, and keys must be double-quoted strings.
- Base64 in authentication
- HTTP Basic authentication encodes username:password in base64 and places it in the Authorization header. Base64 is encoding, not encryption, so it must run over TLS.
- CI/CD validation gate
- A pipeline stage that runs linting, unit tests, and configuration or model validation before deployment. A failure stops the pipeline, preventing broken configuration from reaching production devices.
- RESTCONF transport and port
- RESTCONF maps YANG models to HTTP methods and normally runs over HTTPS on TCP 443, using media type application/yang-data+json or +xml for request and response bodies.
- NETCONF port and encoding
- NETCONF runs over SSH on TCP 830 and encodes messages in XML inside rpc and rpc-reply elements. Operations include get, get-config, edit-config, lock, and close-session.
- NETCONF datastores
- The running datastore holds active configuration, candidate holds uncommitted edits that can be committed or discarded, and startup holds configuration loaded at boot. Not every platform supports all three.
- edit-config operation attributes
- The operation attribute on edit-config elements can be merge (default), replace, create, delete, or remove. Merge adds or updates, replace overwrites the subtree, and remove deletes only if present.
- gNMI RPCs
- gNMI defines Capabilities, Get, Set, and Subscribe over gRPC. Set supports replace, update, and delete paths, while Subscribe supports ONCE, POLL, and STREAM modes for telemetry.
- SNMPv3 security levels
- noAuthNoPriv provides neither authentication nor encryption, authNoPriv adds USM authentication (MD5 or SHA), and authPriv adds encryption (DES or AES) for confidentiality of the payload.
- SNMP trap vs inform
- A trap is an unacknowledged notification sent to UDP 162. An inform is acknowledged by the manager and retransmitted if no response arrives, trading reliability for more overhead.
- YANG container and list
- A container groups related nodes without a key and exists at most once. A list holds multiple entries, each identified by one or more key leaves, similar to a table.
- YANG augment and grouping
- A grouping defines reusable node sets included with uses. An augment adds nodes into another module's existing hierarchy, letting vendors extend standard models without editing them.
- API rate limiting and backoff
- Servers return 429 Too Many Requests when a client exceeds limits. Clients should retry with exponential backoff and jitter, and only retry idempotent operations to avoid duplicate changes.
- OAuth 2.0 bearer token
- The client obtains a token from an authorization server and sends it in the Authorization header as Bearer <token>. Tokens expire and must be refreshed rather than reusing credentials per call.
- IOS XE guest shell
- A Linux container on the device that runs Python scripts and standard tooling. It is entered with the guestshell command and enables on-box automation without an external server.
- EEM event detector types
- EEM applets trigger on syslog patterns, timers, CLI events, SNMP objects, interface counters, or configuration changes. The detector selects the event; the action runs CLI or scripts.
- PnP DHCP option 43
- Plug and Play devices learn the controller address from DHCP option 43 or a DNS record, contact the PnP server, and receive day-0 configuration and image information automatically.
- POAP on NX-OS
- PowerOn Auto Provisioning uses DHCP to give the switch a script server address, downloads a Python script over TFTP or HTTP, and applies image and configuration on first boot.
- pyang model validation
- pyang parses YANG modules, checks syntax and semantic rules, resolves imports, and can render a tree diagram or HTML documentation, making it a standard pre-deployment validation tool.
- Streaming telemetry vs SNMP polling
- Streaming telemetry pushes structured data continuously from the device on change or at intervals. SNMP polling pulls scalar values repeatedly, giving coarser resolution and more device overhead.
- Ansible network_cli connection
- A connection plugin that opens SSH sessions to network devices and runs CLI-based modules such as ios_command and ios_config, using persistent connections and privilege escalation settings.
- Confirmed commit
- A NETCONF commit with a confirm-timeout that is automatically rolled back unless a confirming commit arrives in time, protecting against losing management connectivity during changes.
- DNA Center token authentication
- POST credentials with Basic auth to /dna/system/api/v1/auth/token. The response contains a token valid for about one hour, sent on later calls in the X-Auth-Token header.
- DNA Center discovery API
- POST to /dna/intent/api/v1/discovery with IP ranges and credentials starts device discovery using CDP, LLDP, or SNMP. The call returns a task ID to poll for results.
- DNA Center Command Runner
- POST /network-device-poller/cli/read-request with device UUIDs and CLI commands returns a task ID. The task result references a file containing each device's command output.
- DNA Center task polling
- Most write operations return a taskId. Poll GET /dna/intent/api/v1/task/{taskId} until endTime is populated, then check isError and the progress field before proceeding.
- SD-WAN vBond role
- vBond is the orchestration point that authenticates devices, performs NAT traversal, and redirects each device to its assigned vSmart controllers and vManage for configuration.
- OMP and TLOC
- OMP runs between SD-WAN routers and vSmart to distribute routes, TLOCs, and policies. A TLOC identifies a WAN interface by system IP, color, and encapsulation for path selection.
- vManage API session login
- POST j_username and j_password to /dataservice/j_security_check. A successful login returns a JSESSIONID cookie that must be included in subsequent API requests.
- SD-WAN application-aware routing
- AAR steers traffic by matching applications to SLA classes defined by latency, loss, and jitter thresholds, then selecting the best available path or falling back per policy.
- SD-WAN device templates
- Feature templates configure individual features and are combined into a device template, which is attached to devices. Variables make templates reusable across sites and devices.
- SD-WAN centralized policy types
- Centralized policies are topology (hub-and-spoke, full mesh, custom), traffic-routing (application-aware routing, cflowd, data policies), and cflowd for flow visibility and export.