To expire user sessions after 1800 seconds (30 minutes) in a mobile app, you should configure the session expiration parameter during SDK initialization. This ensures that the session duration is set correctly at the start of the application.
* A: Setting the session expiration parameter (sessionExpiration) to 1800 seconds during SDK initialization is the correct approach. This configuration applies globally to all sessions created by the SDK.
* B: Cookie settings are not relevant for mobile apps, as cookies are typically used in web-based environments.
* C: Theaccounts.initSessionmethod is not used to set session expiration. It initializes a session but does not allow configuring its duration.
* D: Theaccounts.loginmethod is used for user authentication, not for setting session expiration.
SAP Customer Data Cloud References:
* Mobile SDK Session Management.
* SDK Initialization Parameters.

To fetch a preference object from a customer in SAP Customer Data Cloud, you should use theaccounts.
getPoliciesAPI. This API retrieves the consent and preference policies associated with a user, including their preferences and consent status.
* Option A: Correct. Theaccounts.getPoliciesAPI is specifically designed to retrieve user preferences and consent policies.
* Option B: Incorrect. Theaccounts.getSchemaAPI retrieves the data schema of the account but does not provide information about preferences or consent.
* Option C: Incorrect. Theaccounts.getAccountInfoAPI retrieves general account information but does not include detailed consent or preference data.
* Option D: Incorrect. Theaccounts.getConsentStatementsAPI retrieves the list of available consent statements but does not fetch the specific preferences of a user.
References:
* SAP Customer Data Cloud - Consent Management
* accounts.getPolicies API Documentation