A managed provider onboards a retail chain with one Meraki organization, three regions, and mixed MX and MR devices per store. The automation must create isolated networks per store, assign correct device types, and preserve org-wide policies. Which organization to network hierarchy and creating a network approach should the Python script implement for clean onboarding?

Creating one network per store beneath the organization gives each location its own configuration boundary while keeping the organization as the shared parent for organization-wide policies. Setting each network’s type to accommodate its MX and MR devices before claiming those devices supports the intended mixed-device deployment and provides a clean onboarding sequence. A network per region is a common way to organize deployments, but putting multiple stores in the same network does not provide the required per-store isolation. Copying organization-wide policies into network-level overrides may preserve similar behavior initially, but it changes their scope and creates separate copies rather than retaining the policies as organization-wide settings. Selecting only an appliance or wireless network type likewise misses the mixed MX/MR requirement: the network type must support both device classes, rather than merely the predominant one. Exam caveat: Meraki network-type values and supported device combinations depend on the API version and platform behavior, so do not assume that a generic label such as “combined” is valid without checking the current documentation. Practical check: before claiming devices, verify that every store has its own network, that its type supports both required device classes, and that the organization’s shared policies remain configured at the organization level.