which two ways can the Cisco Application Policy Infrastructure Controller push policies to the leaf nodes?

In which two ways can the Cisco Application Policy Infrastructure Controller push policies to the
leaf nodes? (Choose two.)

In which two ways can the Cisco Application Policy Infrastructure Controller push policies to the
leaf nodes? (Choose two.)

A.
On demand (lazy)

B.
Immediate

C.
Static

D.
Programmed

E.
Scheduled

Explanation:
Reference: http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/applicationcentric-infrastructure/white-paper-c11-731961.html



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Cisco DC

Cisco DC

Yes A & B

When a virtual endpoint is discovered, the policy is pushed and programmed to the leaf nodes based on resolution immediacy and instrumentation immediacy, respectively. In both cases, there is an immediate and on-demand (default) option that is defined when the VMM is associated on Cisco APIC. The on-demand option conserves resources and uses the reserved space in the policy content-addressable memory (CAM) when needed.

Resolution Immediacy

The first option to push a policy is immediately. All policies (VLAN, NVGRE, and VXLAN), bindings, contracts, and filters are pushed to the leaf node when the hypervisor physical NIC (pNIC) is attached. With the on-demand option, policies are pushed to the leaf node when the pNIC and vNIC are attached to the port group (EPG).

Deployment Immediacy

Deployment immediacy defines when the policy is programmed in hardware. If the immediate option is chosen, the policies are programmed in the policy CAM after they are received by Cisco APIC. The on-demand option programs policies in the hardware policy CAM only when reachability is learned through the data path.