Enabling or disabling Remote API provides what, and who can configure it?

Enabling or disabling Remote API provides what, and who can configure it?

• A. Provides REST and GraphQL APIs; any admin can configure
• B. Provides XML-RPC and SOAP remote APIs. Requires System Admin permission to configure
• C. Provides XML-RPC only; system administrators are not required
• D. Provides no remote access APIs

Answer: (B)

Enabling or disabling Remote API controls external programmatic access to Confluence, allowing or blocking lines of communication from external apps. In this context, the remote API provides XML-RPC and SOAP endpoints, not REST or GraphQL. Because these APIs can access and manipulate Confluence data, configuring their availability is a system-wide security decision, and only a System Administrator has the permission to turn them on or off. This explains why the correct choice notes XML-RPC and SOAP and requires System Admin permission to configure. The other options don’t fit because REST/GraphQL aren’t part of this Remote API, and access isn’t governed by a lower-level admin role, while saying there are no remote APIs isn’t accurate.

Enabling or disabling Remote API controls external programmatic access to Confluence, allowing or blocking lines of communication from external apps. In this context, the remote API provides XML-RPC and SOAP endpoints, not REST or GraphQL. Because these APIs can access and manipulate Confluence data, configuring their availability is a system-wide security decision, and only a System Administrator has the permission to turn them on or off. This explains why the correct choice notes XML-RPC and SOAP and requires System Admin permission to configure. The other options don’t fit because REST/GraphQL aren’t part of this Remote API, and access isn’t governed by a lower-level admin role, while saying there are no remote APIs isn’t accurate.