Explanation
After you have created an unbound dimension, you can use it just like a bound dimension when creating viewpoints and other user defined data chain objects and properties. You can also create extracts for the dimension, and add permissions, policies, and custom validations. However, you cannot convert an unbound dimension to a bound dimension, because this is not supported by Oracle Enterprise Data Management Cloud.
You cannot create bindings for an unbound dimension, or use it for importing and exporting data, because unbound dimensions are not related to any external applications. References: Working with Unbound Dimensions - Oracle Help Center

Explanation
* C. Use any approval method and do not select "Include Submitter": This option ensures that the
* submitter of the request cannot also be an approver of the request, which enforces the "four-eyes" principle that requires at least two different people to review and approve a request.
* A. Use a serial approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
* B. Use any approval method with at least three different approval groups: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
* D. Use a parallel approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
References:
* https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-approval-policies

Explanation
Application registration is the process of creating an Enterprise Data Management Cloud application by selecting an application type and providing basic information about the application. During application registration, the system generates default data objects such as properties, views, node types, node sets, etc., based on your selections in the registration wizard. You can modify these objects later as needed. You do not generate connections to external applications, import external application data, or load dimension data from flat files during application registration. These tasks are performed after the application is created. References:
Registering Applications - Oracle Help Center3

Explanation
Lookup sets are used to associate source values, or keys, with target values that can be used in expressions for deriving properties or transforming properties in node type converters. You can configure keys and values in a lookup set for one or more applications. Lookup sets are not created during application registration, but rather as separate objects that can be shared acrossapplications. Lookup sets are not used to group and filter nodes, but rather to map values between different applications or perspectives. References: Working with Lookup Sets - Oracle Help Center2

Explanation
When you create a map binding in a dimension, you are creating a mapping relationship between a source node type and a target node type within that dimension. This enables you to transform properties or derive values from source nodes to target nodes when sharing data across applications. When you create a map binding called Account Mapping in the Planning Account dimension, three objects are created in the Planning application: an Account Mapping hierarchy set that contains hierarchies for mapping accounts from GL to Planning; an Account Mapping node set that contains nodes for mapping accounts from GL to Planning; and a node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target that defines how properties are transformed or derived from source nodes to target nodes. A map binding does not create a new dimension or a viewpoint in a view. References: Working with Map Bindings - Oracle Help Center; Working with Node Type Converters - Oracle Help Center