CCIE Data Center key terms

The inter-peer connection serving specific vPC synchronization and forwarding roles, distinct from the separate peer-liveliness function of the keepalive path.

The process of obtaining a usable forwarding next hop for selected reachability, not guaranteed merely by an established routing session.

A forwarding lookup rule selecting the most specific matching usable prefix, distinct from route preference comparisons among alternatives for the same prefix.

A reverse-path check comparing packet arrival with expected tree or source reachability, relevant independently of receiver membership state.

An ACI forwarding construct defining Layer 2 scope and related properties, associated with a routing context and distinct from endpoint policy grouping.

A policy classification construct for endpoints whose membership and contract relationships must be reconciled with actual attachment and forwarding context.

The connected interface, policy-group, AEP, domain, pool, and endpoint-binding relationships needed for the intended ACI physical attachment.

A set of matching service criteria used within applicable ACI policy relationships, not equivalent to routing reachability or a descriptive contract name.

A VXLAN tunnel endpoint that encapsulates or decapsulates traffic and depends on usable underlay reachability to other relevant tunnel endpoints.

A route attribute used in intended import and export membership policy, serving a different purpose from route uniqueness supplied by a distinguisher.

A VXLAN identifier associated with tenant routed overlay context in the applicable design, distinguished from the identifier for a bridged segment.

Delivery behavior for broadcast, unknown-unicast, and multicast traffic, requiring the relevant replication or multicast membership and transport state.

A UCS configuration abstraction combining identity and policy relationships for a server, whose deployment, compatibility, and activation must be verified.

A UCS Manager service-profile template type that propagates later changes to associated profiles, requiring attention to dependency and activation impact.

A managed allocation source for values such as MAC addresses or WWPNs, whose capacity and uniqueness must match actual profile requirements.

A supported host mechanism coordinating alternate storage paths to the same device, not created merely by presenting multiple unrelated volume instances.

The effective set of FC zones for the relevant VSAN, distinguished from additional configured zoning entries that are not currently active.

Storage-side control of volume presentation to initiators, separate from the fabric permission allowing communication with a target port.

A Fibre Channel virtualization capability allowing multiple N-port identities on a suitable connection, relevant to upstream support for an NPV edge.

Ethernet link-level pause behavior for selected priorities, distinct from encryption, global fairness, or end-to-end source-rate control.

Control-plane policing that classifies and regulates CPU-directed traffic under configured policy, distinct from simply increasing data-interface physical capacity.

Encapsulated remote traffic mirroring requiring an appropriate transport path and collector, with interpretation dependent on selected sources and directions.

A short traffic surge capable of causing transient queue pressure or drops while remaining obscured within a longer utilization average.

The decision about which operations an authenticated identity may perform, requiring appropriate role and attribute mapping rather than merely a successful login.

The intended convergence property that repeating an operation against already desired state does not accumulate additional unintended changes, subject to actual implementation semantics.

Checking that an operation returned the expected objects, values, and result, beyond confirming only syntactic validity or HTTP transport success.

A difference between managed intended state and observed configuration, requiring clear ownership and reconciliation behavior across controller and manual changes.

An accepted operation that can continue after its initial response, requiring completion tracking and resulting-state validation rather than immediate success assumptions.