OpenID Connect (OIDC) is an identity layer built on top of the OAuth 2.0 protocol, enabling clients to verify the identity of the end-user based on the authentication performed by an authorization server. The following terms are part of OpenID Connect terminology:
* Claims: These are pieces of information about the user (e.g., name, email, etc.) that are returned in the ID token or userinfo response. Claims represent the attributes of the authenticated user and are essential for conveying identity information.
* Scope: This defines the level of access requested by the client application. In OpenID Connect, scopes are used to specify what claims should be returned in the ID token or userinfo response. For example, theopenidscope is required for OpenID Connect authentication, while additional scopes likeprofileor emailcan request more user details.
The other options are not directly part of OpenID Connect terminology:
* Metadata: While metadata exists in the context of OpenID Connect (e.g., provider configuration metadata), it is not a core term within the protocol itself.
* Assertion: This term is more commonly associated with SAML (Security Assertion Markup Language) rather than OpenID Connect.
SAP Customer Data Cloud References:
* SAP Customer Data Cloud supports OpenID Connect as part of its identity management capabilities.
The platform allows integration with OIDC-compliant identity providers.
* Official SAP Documentation:SAP Customer Data Cloud - OpenID Connect Integration.
* OpenID Connect Core Specification:OpenID Connect Core 1.0.

To ensure that theFirst NameandLast Namefields are formatted in lowercase during an account export using dataflows, SAP recommends using therecord.evaluatecomponent with a custom transformation. This approach allows you to apply JavaScript functions (e.g.,toLowerCase) to transform the data as needed.
* Option A: Incorrect. Thefield.renamecomponent is used to rename fields, not to modify their content.
* Option B: Correct. Therecord.evaluatecomponent allows you to write custom JavaScript code to transform field values. For example, you can use thetoLowerCasefunction to format the fields in lowercase.
* Option C: Incorrect. Thedatasource.read.gigya.accountcomponent is used to read account data, but it does not support applying transformations liketoLowerCasedirectly in its parameters.
* Option D: Incorrect. Thefield.flattencomponent is used to flatten nested JSON structures, not to modify field values.
References:
* SAP Customer Data Cloud - Dataflow Transformations
* Record Evaluate Component Documentation

To retrieve users who have subscribed to the "Fitness Newsletter" from email accounts, you need to query the emailAccountstable and filter based on the subscription status. The correct query is:
* D:SELECT * FROM emailAccounts WHERE subscriptions.<Fitness>.email.isSubscribed=true This query checks if the user is subscribed (isSubscribed=true) to the "Fitness" newsletter specifically for email accounts.
The other options are incorrect:
* A:hasFullAccount=trueis unnecessary because the query is focused on email accounts, not full accounts.
* B: AddinghasFullAccount=trueis redundant and incorrect for this use case.
* C: QueryingfullAccountsis irrelevant because the requirement specifies retrieving users fromemail accounts, not full accounts.
SAP Customer Data Cloud References:
* SAP Customer Data Cloud - Query Language.
* Subscription Management.