Based on this scenario, identify the three things that will happen when the development setup imported to production.

Your company has been working with Fusion in development for some time and has decided to
move to production. After configuring part of the production setup data, your supervisor decides to
import the setup data from development. Because two separate teams were working on
development and production, not all of the configurations match.
1. Industry is configured in development but not in production.
2. Tax Regime is configured in production but not in development
3. Territories are configured in both development and production, but they were configured
differently.
Based on this scenario, identify the three things that will happen when the development setup
imported to production.

A.
Industry in production will remain unchanged.

B.
Industry In production will be updated with values from development.

C.
Tax in production will remain unchanged.

D.
Tax In production will be deleted.

E.
Territory will be synchronized between development and production.

F.
Territory in production will be updated with the values from development.

G.
Territory in production will remain unchanged.

Explanation:
Import
In the target application instance, the setup import process will insert all new data from the source
configuration package that does not already exist and update any existing data with changes from
the source. Setup data that exists in the target instance but not in source will remain unchanged.
Note:Almost all Oracle Fusion application implementations require moving functional setup data
from one instance into another at various points in the lifecycle of the applications. For example,
one of the typical cases in any enterprise application implementation is to first implement in a

development or test application instance and then deploy to a production application instance after
thorough testing.
OracleFusion Applications Sales Implementation Guide,Exporting and Importing Setup
Data: Explained