A. There is no payload option in MCS that guarantees delivery. You need to find a different way to implement your requirement.

B. You define the message payload by using the MCS template and utilize the "alert" keyword in the message.. You send individual notifications to APNs, GCM, and WINS, and use the "alert" keyword in the message.

C. You send a unified payload object that addresses the APNs, GCM, and WINS services, and use the "alert" keyword in the message.

A. The MCS custom API Node implementation includes a server-side Node SDK that inherently supports transaction management for connector API calls.

B. You may nest the second connector call in the callback of the first connector call, or include third party node modules, such as Bluebird, to provide synchronous capabilities.

C. Within the MCS UI, you can define a hierarchical relationship between connectors such that, when called from Node, the call order is implicitly set so that the parent connector is called first and the child is called next.

D. Because of the asynchronous nature of Node.js, there is no way to guarantee that the connectors will be called in a defined order. You must handle an incorrect outcome in an exception handler.

A. Each user interaction is automatically logged as an analytic event by the SDK and sent to MCS.

B. Custom analytic events cannot be defined through the SDKs.

C. Analytic events are dispatched to MCS via an appropriate notification platform such as GCM for Android or APNs for iOS.

D. Analytic events are defined as name/value pairs that are logged in code, and then flushed to MCS via an SDK call.

E. Analytic events are read from a configuration file.

A. The application instance on the mobile device can send push notifications through MCS that are then dispatched to all mobile clients registered for the application in MCS.

B. Push messages can be received only if a valid token is provided with the MCS device registration that was previously obtained from APNs, GCM, or WINS.

C. MCS can schedule notifications to be sent to the application instance on the device and messages are routed via push delivery networks such as APNs, GCM, or WINS.

D. MCS can send push messages directly to the application on the device by using a web socket connection that is kept open until the device unregisters from MCS.

A. Publish the realm role collection.

B. Assign the MCS role to the relevant Oracle Cloud user groups.

C. Do nothing because roles are deployed automatically with any object that references them.

D. Create a new version of the involved user realm and publish it.

E. Create a new version of the involved collection or API and publish.

A. The application on the mobile device could not register to MCS.

B. An MCS team member blocked the user account from receiving push notification messages.

C. The push provider's certificate settings in the mobile backend client application configuration have expired and need to be renewed.

D. The user has disabled notifications for the application by using the mobile device settings.

A. It associates a log entry with a specific mobile use case.

B. It identifies all log entries that are written for a single request regardless of which log files hold the information.

C. It associates logs written for a specific application with a device.

D. It identifies the regional location of a request in the log entry.

A. It offers configurable mappings through XSLT.

B. It is recommended, but it is possible to bypass it if needed.

C. It is mandatory because the SOAP connector APIs cannot bypass it.

D. It offers a comprehensive mapping between JSON and XML, but some limitations exist.

E. It provides a perfect mapping between JSON and XML.