700-702 Dumps Questions With Valid Answers

 Redirect traffic to new VTEP destination

Explanation: Under a normal migration, when a VM moves due to vMotion onto a leaf that
does not have those EPGs and VLANs programmed, the will be deployed immediately.
vCenter/ESXI host will send a GARP to ACI, the old leaf will bounce traffic to the new
location of the endpoint and traffic/learning will occur. The bounce entry will stick around for a bit (about 5 minutes) and then be removed. The EPGs, VLANs, and Default Gateway will
be deployed as soon as the move is detected and there will be little to no downtime (i
usually see 0-1 ping loss, most of the time just increased latency)
https://supportforums.cisco.com/discussion/12394516/importance-your-managementnetwork-
aci-world

40GE
 

Reference: http://thenetworksurgeon.com/cisco-spine-and-leaf-architecture-discussionnexus-
5500-vs-6001/

  Per-tenant admin separation

Explanation: Cisco ACI permits tenant users to modify the parameters and configuration
of the ACI fabric that they own and control. They can also read statistics and monitor faults
and events for the entities (managed objects) that apply to them, such as endpoints, EPGs,
and application profiles. Tenant users can perform configuration changes and read fault
and event logs from the parts of the ACI fabric to which they have access.
The ACI switch operating system includes a role-based access control (RBAC) feature that
allows highly specific access for a given role. This RBAC feature scales to a maximum of
64 unique roles and 256 rules per role. The ACI APIs retrieve data directly from the object
store. A core APIC internal data access control system provides multitenant isolation and
prevents information privacy from being compromised across tenants. Read and write
restrictions prevent any tenant from seeing any other tenant's configuration, statistics,
faults, or event data. Unless the administrator assigns permissions to do so, tenants are
restricted from reading fabric configuration, policies, statistics, faults, and events.
The APIC implements a two-level solution for access control:
• Traditional role-based control: This control level defines the types of objects that a user is
authorized to access. Users are assigned roles (collections of privileges) that govern readonly
or read-write access to managed objects in the system. All managed object classes
have one or more privileges that are assigned to them.
• Domain-based control. This control level defines the domains in which a user is
authorized to access objects.

Server location D CJ physical port D DJ VxLAN number

  VLAN number

Virtual port or port group

4

Reference: http://www.cisco.com/c/en/us/solutions/collateral/data-centervirtualization/
unified-fabric/white-paper-c11-730021.html (effect of replication on reliablity)