Cisco DCAUTO 300-635 flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

NETCONF transport port

NETCONF runs over SSH on TCP port 830 by default (RFC 6242), though some implementations also allow port 22. It carries XML-encoded RPCs over a persistent session.

RESTCONF HTTP verbs

GET reads, POST creates, PUT replaces, PATCH merges, DELETE removes. Data is returned as application/yang-data+json or +xml, keyed to YANG models.

YANG config false

A leaf or container marked config false holds state data that can be read but not written. Configuration data (config true) is writable via edit-config or RESTCONF.

gNMI Subscribe mode

gNMI Subscribe supports STREAM (continuous updates), ONCE (single snapshot), and POLL (on demand). STREAM with a sample interval powers streaming telemetry.

Idempotent automation

An operation is idempotent when repeating it yields the same end state without creating duplicates or errors. Declarative modules are idempotent; raw CLI sequences usually are not.

NETCONF candidate datastore

The candidate datastore holds uncommitted edits. A <commit> operation copies candidate to running, enabling validation and rollback before changes take effect.

Nexus Dashboard Orchestrator scope

NDO manages multi-site ACI and multi-cloud policy. Templates defined once are deployed to one or more sites, either per-site or stretched across sites.

NDFC former name

Nexus Dashboard Fabric Controller was previously called Data Center Network Manager (DCNM). It manages NX-OS LAN VXLAN EVPN and SAN MDS fabrics.

NDI assurance method

Nexus Dashboard Insights uses streaming telemetry and flow data to baseline fabric behavior and raise anomalies, rather than relying only on periodic SNMP polling.

ND API token auth

Nexus Dashboard APIs require a login call that returns a token or cookie. Subsequent requests must include it in headers, and expired tokens must be refreshed.

NDFC API path prefix

NDFC REST endpoints are served under /appcenter/cisco/ndfc/api/v1/ and return JSON. The exact path varies by release and feature area.

ND fabric onboarding

Switches join Nexus Dashboard fabrics via in-band or out-of-band management connectivity, using supplied credentials and either POAP or manual discovery and configuration.

Multi-cluster NDO

A single Nexus Dashboard Orchestrator can federate multiple Nexus Dashboard clusters, each representing a site, and push consistent policy across them.

Ansible playbook structure

A playbook is a list of plays; each play names target hosts and lists tasks. Each task calls a module with arguments and can use conditionals and loops.

Ansible network_cli

network_cli is the Ansible connection plugin for SSH CLI access to network devices. It requires ansible_network_os to select the correct device-specific plugin.

Ansible handlers

Handlers are tasks that run only when notified by a changed task, typically at the end of a play. They are used for restarts or deferred actions.

Terraform init

terraform init downloads required providers and modules and initializes the backend. It must run before plan or apply in a new working directory.

Terraform state file

The state file maps declared resources to real infrastructure. Remote backends with locking allow teams to share state safely and detect drift.

Terraform plan output

terraform plan shows a diff of create, update, and destroy actions without changing infrastructure. Apply executes that plan against the provider APIs.

Ansible register variable

The register keyword stores a task's result in a variable, which can then be inspected with when conditionals or referenced in later tasks.

CI pipeline network stages

Typical stages are lint and validate, plan or preview, approval gate, apply or deploy, and post-deploy verification. Secrets come from a vault, not the repository.

Terraform module inputs

A module is a directory of .tf files exposing input variables and outputs. The module block instantiates it, and terraform.tfvars supplies variable values.

ACI distinguished name

Every ACI object has a class and a DN, a slash-separated path such as uni/tn-Prod/BD-Web. The DN uniquely locates the object for REST operations.

ACI aaaLogin endpoint

POST /api/aaaLogin.json with aaaUser attributes name and pwd returns an APIC-Cookie. Include that cookie in subsequent requests and log out when finished.

ACI query-target subtree

Adding query-target=subtree to a REST call returns all children of the target object, avoiding many separate requests when reading a hierarchy.

ACI rsp-subtree-class filter

rsp-subtree-class limits returned children to a named class, such as fvBD or faultInst, reducing payload size and simplifying parsing.

ACI fault severity filter

query-target-filter=eq(faultInst.severity,"critical") returns only critical faults. Severity values are critical, major, minor, warning, and info.

NX-API ins_api payload

NX-API requests POST JSON with an ins_api object containing type, chunk, version, input, and output_format. Type cli_show runs show commands and returns JSON.

NX-API cli_conf type

The cli_conf message type sends configuration commands through NX-API, as opposed to cli_show and cli_show_ascii, which run read-only show commands.

Enable NX-API feature

The command feature nxapi enables the NX-API HTTP and HTTPS endpoints, which listen on ports 80 and 443 by default.

Enable NX-OS NETCONF

The command feature netconf enables the NETCONF server on NX-OS. YANG model coverage depends on the software release and should be verified.

ACI imdata response array

ACI REST responses wrap results in an imdata array of objects, each keyed by class name with an attributes map. Scripts must iterate imdata, not assume a flat object.