Which option best describes Aruba best practices for Central design when you need GUI configuration for gateways and APs but template configuration for switches?

Which option best describes Aruba best practices for Central design when you need GUI configuration for gateways and APs but template configuration for switches?

• A. Create separate groups for each device type and assign devices to locations
• B. Create a single group for all devices and a unique site for each location
• C. Create a single group for switches and a separate group for APs and gateways
• D. Create multiple sites with no device grouping

Answer: (B)

In Aruba Central, you want to separate how you configure devices by what fits best for the type of configuration you’re applying. Use a single management group for all devices so you can reuse templates for switches across the board, and create a unique site for each location to handle location-specific GUI configurations for gateways and APs. This setup keeps centralized control simple (one group where switch configurations come from templates) while allowing per-location customization for endpoints like APs and gateways through the GUI. Sites give you the means to apply different site-specific settings without duplicating the entire template structure, which would happen if you split devices into separate groups. Other approaches tend to fragment template management or blur location-specific differences, making it harder to maintain consistency and scale.

In Aruba Central, you want to separate how you configure devices by what fits best for the type of configuration you’re applying. Use a single management group for all devices so you can reuse templates for switches across the board, and create a unique site for each location to handle location-specific GUI configurations for gateways and APs. This setup keeps centralized control simple (one group where switch configurations come from templates) while allowing per-location customization for endpoints like APs and gateways through the GUI. Sites give you the means to apply different site-specific settings without duplicating the entire template structure, which would happen if you split devices into separate groups. Other approaches tend to fragment template management or blur location-specific differences, making it harder to maintain consistency and scale.