Public App Integration describes which of the following?

Public App Integration describes which of the following?

• A. It requires a client secret to be stored securely
• B. It is for server-side integrations only
• C. It allows applications that can't securely store a client secret to integrate with Marketing Cloud on behalf of an end user
• D. It is deprecated

Answer: (C)

Public App Integration is designed for client-side or public applications that cannot securely store a client secret. It uses an OAuth flow that does not require a secret (often using PKCE) and grants access on behalf of an end user, enabling the app to act with the user’s permissions. This matches the described option precisely. In contrast, confidential server-side apps typically rely on a client secret and enable server-to-server or user-independent access, and the idea of deprecation isn’t part of the standard distinction.

Public App Integration is designed for client-side or public applications that cannot securely store a client secret. It uses an OAuth flow that does not require a secret (often using PKCE) and grants access on behalf of an end user, enabling the app to act with the user’s permissions. This matches the described option precisely.

In contrast, confidential server-side apps typically rely on a client secret and enable server-to-server or user-independent access, and the idea of deprecation isn’t part of the standard distinction.