When setting up SAP Customer Data Cloud as a SAML Identity Provider (IdP), two key pages are required:
theAssertion pageand theProxy page.
* Assertion Page: This page is responsible for generating and sending the SAML assertion to the Service Provider (SP). It contains the logic to construct the SAML response, including user attributes and authentication status.
* Proxy Page: The Proxy page acts as an intermediary between the SP and the IdP. It handles the redirection of users during the SAML flow and ensures that the SAML request and response are properly processed.
* Option C: Incorrect. The Error page is optional and is used to display error messages. It is not a key page required for the setup.
* Option D: Incorrect. The Consent page is used for obtaining user consent for data sharing and is not directly related to the SAML setup.
References:
* SAP Customer Data Cloud - SAML Configuration
* SAML Protocol Overview

The authorization framework that supports bothcoarse-grainedandfine-grainedauthorization isaccess control based on attributes. Attribute-based access control (ABAC) uses attributes (e.g., user roles, resource types, environmental conditions) to define policies that can range from broad (coarse-grained) to highly specific (fine-grained).
* Option A: Incorrect. Role-based access control (RBAC) primarily supports coarse-grained authorization and lacks the flexibility for fine-grained control.
* Option B: Incorrect. Access control based on lists and roles combines RBAC with access control lists but still lacks the granularity of ABAC.
* Option C: Correct. Attribute-based access control (ABAC) supports both coarse-grained and fine- grained authorization by leveraging attributes to define dynamic and context-aware policies.
* Option D: Incorrect. Policy-based access control is a broader term and may include ABAC, but it is not inherently designed for both coarse- and fine-grained authorization.
References:
* SAP Customer Data Cloud - Authorization Frameworks
* Attribute-Based Access Control (ABAC)