A retail company is opening a fifth store, and its Meraki organization already holds four store networks with their own MX firewalls and MR access points. Automation must add the new store network through the REST API so its hardware can be assigned to it afterwards, sitting alongside the existing four in the same organization. Which API call creates the network at the correct level of the Meraki hierarchy?
Select an answer to reveal the explanation.
Short Explanation
You’ve got the hierarchy right: organizations hold networks, and networks hold devices. Create the fifth store as a sibling of the existing networks with both product types on the organization resource; hardware assignment happens afterward.
Full Explanation
The correct call creates a network directly under the organization, the required level in the Meraki hierarchy. Supplying both appliance and wireless in productTypes configures the network for the store’s MX firewall and MR access points, so it sits alongside the four existing networks and can receive hardware afterward. Creating the network with only wireless uses the organization-level endpoint but omits the product type needed for the MX appliance. Creating it with only appliance also uses that endpoint but omits the wireless product type needed for the MR access points. Both calls leave out one of the two product types required by the scenario. Creating the network with both product types under a separate organization has the right product types but puts it in the wrong organization, so it will not sit alongside the company’s four existing networks. Exam caveat: creating a network and claiming or assigning hardware are separate operations; inventory does not create the network automatically. Practical check: after creation, confirm the network’s organization ID and product types in the API response before assigning the MX and MR devices.