In theCustomer Identity policiessection of SAP Customer Data Cloud, you can define the following password attributes:
* Option A: Incorrect. Themaximum password lengthis not configurable in the Customer Identity policies. Only the minimum length is enforced.
* Option B: Correct. Thepassword reset token expiration timecan be configured to determine how long a password reset link remains valid.
* Option C: Incorrect. The concept ofmax character groups(e.g., requiring a mix of uppercase, lowercase, numbers, and symbols) is not a configurable attribute in the policies.
* Option D: Correct. Theminimum password lengthcan be defined to enforce strong password requirements.
References:
* SAP Customer Data Cloud - Password Policies
* Password Reset Token Configuration

To launch the Delegated Administration console in SAP CIAM for B2B, you need to use the openDelegatedAdminLoginendpoint and pass theorgIDparameter. This combination ensures that the Delegated Admin function is opened for the specified organization.
* Option A: Incorrect. Theemailparameter is not sufficient to identify the organization in the context of delegated administration.
* Option B: Incorrect. TheUIDparameter identifies the user but does not specify the organization for delegated administration.
* Option C: Incorrect. TheorganizationContextendpoint is not used to launch the Delegated Admin console.
* Option D: Correct. TheopenDelegatedAdminLoginendpoint, combined with theorgIDparameter, is required to open the Delegated Admin function for a specific organization.
References:
* SAP CIAM for B2B - Delegated Administration
* Delegated Admin Console Documentation

To capture multiple consent statements during registration and support the reconsent process, the following screens need to be mapped to the consent statements:
* Option A: Incorrect. TheProfile Updatescreen is used for updating user profiles after registration and is not directly involved in capturing consent during registration.
* Option B: Correct. TheRegistration Completionscreen is used to finalize the registration process and can include consent statements that users must agree to before completing registration.
* Option C: Correct. TheRegistrationscreen is the primary screen where users enter their details and can also include consent statements as part of the registration flow.
* Option D: Incorrect. TheLoginscreen is used for authentication and is not typically used to capture consent statements.
References:
* SAP Customer Data Cloud - Screen-Sets
* Consent Statements in Registration

To check the session status in theiOS Swift SDK, you should use thegigya.isSessionAlive()method. This method determines whether the current session is active and valid.
* Option A: Correct. Thegigya.isSessionAlive()method checks if the session is still valid by verifying the session token and its expiration time.
* Option B: Incorrect. Thegigya.isLoggedIn()method checks if the user is logged in but does not verify the session's validity.
* Option C: Incorrect.gigya.sessionExpirationTimestampprovides the timestamp of when the session expires but does not actively check the session status.
* Option D: Incorrect.gigya.sharedInstance().sessionExpirationTimestampis similar to Option C and only provides the expiration timestamp without verifying the session.
References:
* SAP Customer Data Cloud - iOS SDK
* Session Management in iOS SDK