A customer is adding load balancers to route S3 traffic across multiple storage nodes. What StorageGRID component should they deploy?

A customer is adding load balancers to route S3 traffic across multiple storage nodes. What StorageGRID component should they deploy?

• A. Admin Node
• B. API Node
• C. Gateway Node
• D. TSM Node

Answer: (C)

Gateway Nodes serve as the S3/Swift API entry point and handle the data path that routes object requests across the StorageGRID storage nodes. They are designed to sit in front of the storage layer, receiving client traffic, applying routing logic, and distributing load to the underlying storage nodes to achieve scalable throughput. This role makes them the right component when you want to use load balancers to spread S3 traffic across multiple storage nodes. Admin Nodes are for management tasks, API Nodes host the management API, and TSM Nodes handle tiered storage management; none of these primarily handle the S3 data path routing like gateway nodes do.

Gateway Nodes serve as the S3/Swift API entry point and handle the data path that routes object requests across the StorageGRID storage nodes. They are designed to sit in front of the storage layer, receiving client traffic, applying routing logic, and distributing load to the underlying storage nodes to achieve scalable throughput. This role makes them the right component when you want to use load balancers to spread S3 traffic across multiple storage nodes. Admin Nodes are for management tasks, API Nodes host the management API, and TSM Nodes handle tiered storage management; none of these primarily handle the S3 data path routing like gateway nodes do.