Free SAP C_C4H620_34 Practice Exam with Questions & Answers | Set: 3

To expire user sessions after 1800 seconds in a mobile app using SAP Customer Data Cloud, you should set the sessionExpiration parameter to 1800 seconds when callingaccounts.login.

Setting Session Expiration:

When implementing the login functionality, ensure that you include the sessionExpiration parameter in your API call.

Example API call:accounts.login({"sessionExpiration": 1800, ...}).

This will ensure that the user sessions expire after 1800 seconds of inactivity.

References

SAP Customer Data Cloud API Documentation

In a schema field within SAP Customer Data Cloud, you can set various properties to define its behavior and characteristics. The properties include:

Whether the field is encrypted: This property ensures the data stored in the field is encrypted for security purposes.

The field's type: This property defines the data type of the field (e.g., string, integer, boolean).

The field's name: This property assigns a unique name to the field for identification and reference within the schema.

These properties help in customizing and securing the data structure within the system.

References

SAP Customer Data Cloud Schema Field Documentation

When you require custom logic for real-time data synchronization after installing the GConnector, the recommended approach is to use custom hooks. Custom hooks allow you to inject your own logic at specific points in the data processing workflow.

Custom Hooks: These are custom functions that can be executed during the synchronization process to handle specific business requirements or data transformation needs.

Implementation: You can define custom hooks in the configuration of your GConnector to execute custom logic when certain events occur or data needs to be processed in a particular way.

This approach ensures that you can tailor the synchronization process to meet specific business needs without altering the core functionality of the GConnector.

References

SAP Customer Data Cloud GConnector Documentation

The recommended approach to make a native API call, such asgetAccountinfo, from an Android client is to:

Use internal SDK method Gigya.getInstance().send to call the API method with an application key and secret (D): This method allows you to securely call the API using the provided application key and secret.

References

SAP Customer Data Cloud Android SDK Documentation

SAP Help Portal on Native API Calls