An engineer automates onboarding for a new branch office in the Meraki dashboard. The account manages one organization that already holds several networks, and the new site needs both a switch and an access point from day one. The script must place the new network inside the organization hierarchy and declare its hardware up front. Which API request should the script send to create this network?
Select an answer to reveal the explanation.
Short Explanation
Meraki builds its world as organizations containing networks, so the network must be created from the organization endpoint. Declaring product types at creation also tells the dashboard which licensing and inventory apply. You wouldn't write into a filing drawer that doesn't exist yet.
Full Explanation
Meraki mirrors the dashboard hierarchy in the API, and networks exist only as children of an organization, so creation happens at the organization scope rather than the network scope. The POST to that organization's networks collection needs the network name together with the product types that declare which hardware families the site will use, because those types drive licensing, inventory and the dashboard view from the moment the network appears. A standalone networks collection at the top level does not exist in the Meraki API, so creating a network elsewhere and binding it afterwards never places it inside the hierarchy. Leaving out productTypes makes the creation request incomplete, and registering devices before the network exists inverts the order of operations, since a device can only join a network that is already there. Exam caveat: confirm the required field set against the current Meraki API documentation before you script it. A practical check is to list the organization's networks afterwards and verify the new name appears with its product types intact.