C_C4H62_2408 Exam Dumps : SAP Certified Associate - Implementation Consultant - SAP Customer Data Cloud

In SAP Customer Data Cloud, webhooks can be configured for specific events to trigger notifications to external systems. The following events are supported and can be configured in the Console:

Account registered: Triggered when a new account is created.

Consent granted: Triggered when a user grants consent for data usage.

Account verified: Triggered when an account is successfully verified (e.g., email verification).

The other options are not valid:

C. Account deleted: This event is not supported for webhook configuration in SAP Customer Data Cloud.

E. Subscription updated: While subscription-related events may exist, they are not part of the standard webhook events for SAP Customer Data Cloud.

SAP Customer Data Cloud References:

SAP Customer Data Cloud - Webhooks Configuration.

Supported Webhook Events.

To add dynamic data to a consent record in SAP Customer Data Cloud, the following methods are recommended:

A. Custom field: Custom fields allow you to store additional, dynamic data specific to the consent record. This is useful for capturing unique attributes or metadata related to the consent.

B. Tags: Tags can be used to categorize or label consent records dynamically. They provide flexibility in organizing and retrieving consent data based on predefined criteria.

The other options are incorrect:

C. Entitlements: Entitlements are not used for adding dynamic data to consent records. They are typically associated with user permissions or access rights.

D. Header: Headers are not a mechanism for adding dynamic data to consent records. They are part of API requests or responses.

SAP Customer Data Cloud References:

Consent Management Overview.

Custom Fields and Tags in Consent Records.

In a JSON Web Token (JWT), thesub(subject) claim represents the unique identifier of the user. It is a standard claim defined in the JWT specification (RFC 7519) and is used to identify the principal (user) that is the subject of the token. Thesubclaim is mandatory in many identity protocols, including OpenID Connect (OIDC), where it serves as the UID of the user.

Option A: Incorrect. Thekid(key ID) is used to identify the cryptographic key used to sign the token, not the user.

Option B: Incorrect. Theidclaim is not a standard JWT claim and is not used to represent the UID of the user.

Option C: Incorrect. TheuserKeyis not a standard JWT claim and does not represent the UID of the user.

Option D: Correct. Thesubclaim is the standard attribute in a JWT that represents the UID of the user.

References:

JSON Web Token (JWT) RFC 7519

OpenID Connect Core Specification