350-901 · Question #87
An engineer must enable an SSID in a Meraki network. Which request accomplishes this task?
The correct answer is A. PUT /networks/{networkId}/ssids/{number}, {"enable": true}. To enable an existing Meraki SSID, a PUT request is sent to the specific SSID's API endpoint with a JSON payload containing {"enabled": true}.
Question
Options
- APUT /networks/{networkId}/ssids/{number}, {"enable": true}
- BPOST /networks/{networkId}/ssids/{number} {"enable"=true}
- CPUT /networks/{networkId}/ssids/{number}?enabled=true
- DPOST /networks/{networkId}/ssids/{number}?enabled=true
How the community answered
(51 responses)- A92% (47)
- B4% (2)
- C2% (1)
- D2% (1)
Why each option
To enable an existing Meraki SSID, a PUT request is sent to the specific SSID's API endpoint with a JSON payload containing `{"enabled": true}`.
The PUT HTTP method is appropriate for updating an existing resource, such as enabling an SSID identified by its network ID and number. The JSON payload `{"enable": true}` correctly specifies the desired state for the `enabled` attribute.
POST is typically used for creating new resources, not for updating existing ones, and the payload syntax `{"enable"=true}` is incorrect JSON.
While PUT is the correct method, passing the `enabled` parameter as a query string (`?enabled=true`) is not the standard way to send configuration data for a Meraki SSID; configuration changes are sent in the request body as a JSON object.
POST is incorrect for updating an existing resource, and passing `enabled` as a query parameter is not the standard method for Meraki API configuration updates.
Concept tested: Meraki API for SSID management and HTTP PUT method
Source: https://developer.cisco.com/meraki/api-v1/#!update-network-ssid
Topics
Community Discussion
No community discussion yet for this question.