You have an Azure subscription that contains an Azure API Management instance named ContosoAPI1.

The relevant configuration area is Protocols + ciphers . SSL 3.0 is a transport-security protocol , not a certificate configuration. Azure API Management exposes protocol settings for communication between the gateway and clients and between the gateway and backend services. Microsoft documents that protocol configuration is performed from the API Management instance under Security > Protocols + ciphers , where supported frontend and backend protocols can be managed. Microsoft Learn

Microsoft ' s API Management PowerShell documentation specifically recognizes Ssl30 as a configurable backend protocol and frontend protocol setting, confirming that SSL 3.0 belongs to the protocol configuration rather than the Certificates blade. Microsoft Learn

Adding a certificate does not enable a particular SSL/TLS protocol; certificates establish server or client identity and participate in TLS authentication. An API tag only organizes APIs and has no transport-security effect. Changing the pricing tier is also not the first action required merely to locate the SSL protocol setting.

One important operational point is that SSL 3.0 is obsolete and cryptographically unsafe . Microsoft recommends TLS 1.2 or later, and current Azure security guidance treats SSL 3.0, TLS 1.0, and TLS 1.1 as deprecated protocols. The question, however, asks specifically where to configure the requested protocol.

Correct answer: C. From Protocols + ciphers, select a backend protocol.

===============