In which way does a spine-and-leaf architecture allow for scalability in a network when additional access ports are required?
- A spine switch and a leaf switch can be added with redundant connections between them.
- A spine switch can be added with at least 40 GB uplinks.
- A leaf switch can be added with connections to every spine switch.
- A leaf switch can be added with a single connection to a core spine switch.
Answer(s): C
Explanation:
Spine-leaf architecture is typically deployed as two layers: spines (such as an aggregation layer), and leaves (such as an access layer). Spine-leaf topologies provide high-bandwidth, low-latency, nonblocking server-to-server connectivity.
Leaf (aggregation) switches are what provide devices access to the fabric (the network of spine and leaf switches) and are typically deployed at the top of the rack. Generally, devices connect to the leaf switches. Devices can include servers, Layer 4-7 services (firewalls and load balancers), and WAN or Internet routers.
Leaf switches do not connect to other leaf switches. In spine-and-leaf architecture, every leaf should connect to every spine in a full mesh.
Spine (aggregation) switches are used to connect to all leaf switches and are typically deployed at the end or middle of the row. Spine switches do not connect to other spine switches.
Reference:
https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/guide-c07-733228.html