D.

  With the CLI
 

D.

 When an endpoint detaches from the Cisco ACI fabric, the Cisco APIC can notify the
Layer 4 to Layer 7 service to dynamically remove configuration.

E.

 When a new endpoint attaches to the Cisco ACI fabric, the Cisco APIC can notify the
Layer 4 to Layer 7 service to dynamically add additional configuration.

Explanation: Endpoint and Network Event APIs
The following APIs are called when an endpoint or a network configuration changes for
endpoint groups (EPGs) that are associated with the graph:
def attachEndpoint( device, configuration, endpoints )
def detachEndpoint( device, configuration, endpoints )
def attachNetwork( device, configuration, networks)
def detachNetwork( device, configuration, networks )
These APIs are called only if the device specification supports an endpoint or network
attach notification and you have enabled a notification on the function connector. The
AttachEndpoint and DetachEndpoint events are called when an endpoint within an EPG
attaches or detaches. The network APIs are called when you modify the subnet
configuration under the bridge domain or EPG. These APIs provide information to enable
the automation of any service function configuration that should be modified on an endpoint
or network configuration change. An example would be if you dynamically add and remove
a server from a pool that is attached to a load balancer or dynamically update a subnet
within an access list defined for a firewall. The device specification file can define an empty
function that returns success in the return format that is required by the APIC. It is not
mandatory to support endpoint or network event handling functionality.

A.

A Layer 4 to Layer 7 appliance can program the Cisco APIC.
 

B.

 The Cisco APIC controls and automatically configures Layer 4 to Layer 7 services via
device packages
 

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/acifundamentals/
b_ACIFundamentals/
b_ACI_Fundamentals_BigBook_chapter_01000.html#concept_CEBBC56D6
5A0476991F381F4C1DDDF9E

A.

Virtual switch

E.

End point groups

A.

Application connectivity requirements
 

Reference: http://www.cisco.com/c/en/us/solutions/collateral/data-centervirtualization/
application-centric-infrastructure/white-paper-c11-731630.html (ACI
Application network profile)

D.

 Count the number of packets received

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-
x/troubleshooting/b_APIC_Troubleshooting/b_APIC_Troubleshooting_chapter_01.html
(About atomic counters)

B.

 The application profile is created in Windows Azure Pack Management Portal and
pushed to the Cisco APIC.
 

Explanation: http://www.cisco.com/c/en/us/solutions/collateral/data-centervirtualization/
application-centric-infrastructure/white-paper-c11-732080.html

A.

enables VM mobility between VMMs
 

B.

  can contain multiple virtual machines
 

E.

  can span multiple VMMs
 

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/acifundamentals/
b_ACI-Fundamentals/b_ACI_Fundamentals_BigBook_chapter_0111.pdf