The task is to modify an existing resource, which is the SSID's enabled state. According to REST API conventions, the PUT method is used to update an existing resource. The Meraki Dashboard API follows this standard. The request must target the specific SSID using its network ID and SSID number in the URL path. The parameters for the update, in this case, {"enable": true}, are passed in the request body as a JSON object. Option A correctly combines the PUT method, the correct endpoint structure, and the proper JSON payload format.

B. The POST method is used for creating new resources, not for updating an existing SSID's configuration.

C. While PUT is the correct method, the Meraki API expects update parameters to be in the JSON request body, not as query parameters in the URL.

D. This option is incorrect because it uses the POST method (for creation) and passes data as a query parameter, both of which are wrong for this operation.

1. Cisco Meraki Dashboard API v1 Documentation: The official documentation specifies the method and endpoint for updating an SSID.

Endpoint: updateNetworkSsid

Method & Path: PUT /networks/{networkId}/ssids/{number}

Parameter: The enabled parameter is a boolean value passed in the request body.

Source: Cisco DevNet

Meraki Dashboard API

"Update the attributes of an SSID"

https://developer.cisco.com/meraki/api/v1/#!update-network-ssid (Accessed under the "Wireless > SSIDs" section).

2. REST API Design Principles (General Academic Context): University courseware on web services and API design consistently teaches that PUT is the standard idempotent method for updating or replacing a resource at a known URI.

Source: Fielding

R. T. (2000). Architectural Styles and the Design of Network-based Software Architectures. Doctoral dissertation

University of California

Irvine. Chapter 5

"Representational State Transfer (REST)". This foundational text defines the semantics of HTTP methods like PUT and POST.