You need a routing policy at a specific location without changing other sites. Where should you place the configuration, so inheritance behaves as intended?
A.
Site level for the affected location to override global scope
B.
Device level to force changes up the hierarchy
C.
Site collection level to merge with device level equally
Choose the affected site, associate the correct device function and apply the routing configuration at that scope. The effective configuration is determined by Central's profile association and inheritance rules, including whether an object is shared or local; a site-level adjustment should not be assumed to propagate into other sites. Verify any cross-scope dependencies such as VRFs, interfaces, next hops and named objects. After deployment, compare the site's effective settings and switch routing table with an unaffected location to ensure no unintended global change.
Device scope is more specific but does not propagate “up” the hierarchy. Site collection affects multiple sites if inherited, making it too broad. Site scope retains the global baseline elsewhere while allowing the targeted routing configuration to differ.
Official HPE references | Multi-Level Hierarchy • System Profiles | Study-guide topic: Network Management with HPE Aruba Networking Central
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit