Which two configurations allow for routing traffic between two VDCs? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.AD.
The Virtual Device Context (VDC) feature allows you to partition a physical switch into multiple logical devices, each with its own set of virtualized resources, including interfaces, VLANs, and routing tables. By default, VDCs are isolated from each other and cannot communicate directly. However, there are several ways to enable traffic routing between VDCs, including:
A. Connect the VDCs to an external Layer 3 device: This option involves connecting the VDCs to an external Layer 3 device such as a router or a switch that supports inter-VLAN routing. Each VDC will be connected to a different VLAN on the external device, and the device will route traffic between the VLANs. This option provides maximum flexibility and scalability, but it may also increase complexity and cost.
B. Cross-connect the ports between the VDCs: This option involves physically connecting ports on different VDCs using a cable, effectively creating a "virtual wire" between them. The ports can be configured as Layer 2 or Layer 3 interfaces, and traffic will be forwarded between them without the need for an external device. This option is simple and cost-effective but may not be scalable for large deployments.
C. Create VRF-aware software infrastructure interfaces: This option involves creating Virtual Routing and Forwarding (VRF) instances on the switch and assigning them to software infrastructure interfaces (SII) that span across multiple VDCs. Each VRF will have its own routing table and forwarding decisions, allowing for traffic separation and isolation between VDCs. This option is flexible and scalable, but it requires advanced knowledge of VRFs and SIIs.
D. Create a policy map in the default VDC that routes traffic between the VDCs: This option involves creating a policy map in the default VDC that forwards traffic between the VDCs based on certain criteria such as source/destination IP address or protocol. The policy map can be applied to interfaces in each VDC, effectively enabling traffic routing between them. This option is simple but may not be as flexible or scalable as the other options.
E. Create interfaces in the VDC that can be accessed by another VDC: This option involves creating Layer 3 interfaces in each VDC that can be accessed by the other VDC. The interfaces can be connected using a Layer 2 network such as a VLAN or a VPC domain. Traffic will be forwarded between the interfaces based on their IP addresses and routing table entries. This option is simple but may not be as flexible or scalable as the other options.
In summary, options A, B, and C provide the most flexibility and scalability for inter-VDC routing, while options D and E are simpler but may be sufficient for smaller deployments.