A script that manages a Meraki dashboard creates a new SSID in an existing wireless network each time it runs, so the list of SSIDs keeps growing. The script only needs to change the authentication mode of one SSID that already exists in that network. Which HTTP method and resource URL should it use to make that change?
Select an answer to reveal the explanation.
Short Explanation
To change an existing SSID’s authentication mode, use PUT on that SSID’s resource URL with its identifier, and send the revised settings in the body. It’s like updating a home at its exact address instead of adding another house to the street.
Full Explanation
For this SSID endpoint, POST to the network's SSID collection creates an SSID, while PUT to the URL of an existing SSID updates it. Find the SSID's number with a GET on the network's SSID collection, then PUT the revised settings to that SSID's own path so the change applies to the intended entry. Posting to the collection again creates another SSID rather than updating the existing one. Although PATCH is often used for partial updates, this SSID endpoint does not support PATCH. Exam caveat: confirm the method and path in the current reference for the resource you are changing, because wireless settings are spread across several endpoints. Practical check: read the SSID list, PUT the change, then read it again and confirm the existing entry has the new authentication mode.