* This option is correct because when the approval method is parallel and one approval per group is not selected, the approvers from different groups can approve in any order and the request is approved when the total required number of approvals is met, regardless of which groups they belong to.

Explanation
In a maintenance view for mappings, you can compare the source and mapping viewpoints to identify nodes that exist in the source but have not been mapped to the target. The next step to define mappings is to create a request, then drag and drop nodes from the source to the mapping viewpoint. This way, you can create new nodes in the mapping viewpoint that have properties derived or transformed from the source nodes using the node type converter and map binding. You do not need to use an Excel mapping file, run a mapping utility, or open a request and add nodes to the target viewpoint, because these are not supported methods for defining mappings in Oracle Enterprise Data Management Cloud. References: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center2

Explanation
A custom validation is a validation that checks whether nodes meet certain criteria based on their actions or properties using an expression that returns a Boolean value. To enable a custom validation, you need to meet the following conditions: define a valid expression and a failure message for the custom validation; configure at least one trigger action and/or a trigger property for a node set or hierarchy set that uses the custom validation. You do not need to define a derived property of the Custom Validation node type or an expression that returns a Boolean value and a failure message, because these are not supported by Oracle Enterprise Data Management Cloud. References: Working with Custom Validations - Oracle Help Center

* You need the Data Manager or Owner permission to the application to export its dimensions and mappings: This option is correct because the Data Manager or Owner permission is required to export enterprise data from an application to an external application or a file.
* For Planning and Universal applications, you can export enterprise data using either a connection or a comma-delimited file: This option is correct because Planning and Universal applications support both methods of exporting enterprise data.

Explanation
An alternate viewpoint is a viewpoint that lets you see enterprise data organized in a different way. Nodes can be aggregated, rolled up, or summarized using a hierarchy that differs from the hierarchy in the bound viewpoint. An alternate viewpoint can be in an unbound state or a partially bound state. The following statements are true about an alternate viewpoint in an unbound state: the alternate viewpoint is not used in a binding and all of the data chain objects that it contains have a binding status of Unbound; unbound data objects in an alternate viewpoint enable you to model and evaluate potential changes to dimensions in cases where the changes would not conform to a dimension's current binding rules; the alternate viewpoint may be partially bound if it shares data chain objects with a bound viewpoint. The following statements are false about an alternate viewpoint in an unbound state: the alternate viewpoint is not used in a binding, but all of the data chain objects that it contains have a binding status of Bound; you cannot use the alternate viewpoint to construct a what-if scenario that is isolated from production. An unbound alternate viewpoint does not have any bound data objects, because it is not related to any external applications. You can use an unbound alternate viewpoint to construct a what-if scenario that is isolated from production, because it does not affect the bound viewpoint or the external applications. References: Defining AlternateViewpoints - Oracle Help Center1; Understanding Bindings and Bound Data Objects - Oracle Help Center2