Which client protocols are supported by the Confluent Schema Registry?

Which client protocols are supported by the Confluent Schema Registry?

• A. TCP
• B. WebSocket
• C. HTTP, HTTPS
• D. UDP

Answer: (C)

Confluent Schema Registry is accessed through a RESTful HTTP(S) API. Clients interact by sending HTTP requests to predefined endpoints to register schemas, look them up by subject or id, and manage compatibility rules. Because the API is defined in terms of HTTP methods and URIs, the supported client protocols are HTTP and its secure variant HTTPS. HTTPS provides TLS encryption for secure communication, which is commonly used in production. While HTTP runs over TCP, the registry’s interface is not a raw TCP or UDP connection, and it does not use WebSocket endpoints. So HTTP/HTTPS is the appropriate protocol family for clients to communicate with the Confluent Schema Registry.

Confluent Schema Registry is accessed through a RESTful HTTP(S) API. Clients interact by sending HTTP requests to predefined endpoints to register schemas, look them up by subject or id, and manage compatibility rules. Because the API is defined in terms of HTTP methods and URIs, the supported client protocols are HTTP and its secure variant HTTPS. HTTPS provides TLS encryption for secure communication, which is commonly used in production. While HTTP runs over TCP, the registry’s interface is not a raw TCP or UDP connection, and it does not use WebSocket endpoints. So HTTP/HTTPS is the appropriate protocol family for clients to communicate with the Confluent Schema Registry.