What is the role of a Cisco APIC when configuring services for the Cisco ACI fabric?
A. It connects physical appliances automatically to the correct EPG
B. It builds a service graph by communicating with switches and routers
C. It provides a single point of provisioning that can accessed via a REST API
D. It communicates with load balancers without using a plug-in
https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-732493.html
Yes C, probably – Figure 3. Cisco APIC Provides the Capability to Configure Services with REST, Scripts, or a GUI
Not D – For Cisco ACI to be able to talk to firewalls or load balancers, it needs to speak to their APIs. The administrator needs to install plug-ins on Cisco APIC that enable this communication.
The C or A are correct.
But in A, it say “physical” but it can also connect virtual (because of Hw abstraction) so, it seems about this, that it is not too much for A.
On the other hand C does not pointing on Service Configuration in concrete.
So you should go on one of them.
The answer is C.
“Appliances don’t need to be placed in any particular place in the fabric. They can run as physical appliances connected to any leaf, or as virtual appliances running on any virtualized server.
Physical appliances can run with multiple virtual contexts as well. Cisco ACI can model this concept in the construction of the policy.
A service graph is a variation of the concept of a contract. In the Cisco ACI policy model, a contract connects two endpoint groups (EPGs). A contract can also offer functions such as traffic filtering, traffic load balancing, and SSL offloading. Cisco ACI locates the devices that provide such functions and inserts them into the path as defined by the service graph policy.”
https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-732493.html