If a Fusion Cloud Application test environment is refreshed from production and you connect to it from FDI using password-based authentication, what step is required?

If a Fusion Cloud Application test environment is refreshed from production and you connect to it from FDI using password-based authentication, what step is required?

• A. You must update the applicable user's credentials if the passwords aren't the same in all environments.
• B. You must reset all passwords to a common value
• C. You must switch to OAuth
• D. You must disable environment isolation

Answer: (A)

After refreshing a Fusion Cloud test environment from production, the passwords for user accounts often don’t carry over identically. When you connect to the test environment from FDI using password-based authentication, you must have the correct password for the user in that refreshed environment. If the passwords aren’t the same across environments, authentication will fail, so you need to update the applicable user’s credentials in the test environment to match (or otherwise ensure they are in sync). This keeps the login working smoothly for FDI. The other options aren’t required here: resetting all passwords to a common value isn’t typically appropriate or secure, switching to OAuth changes the authentication method rather than solving a drifted password issue, and disabling environment isolation isn’t related to fixing login credentials.

After refreshing a Fusion Cloud test environment from production, the passwords for user accounts often don’t carry over identically. When you connect to the test environment from FDI using password-based authentication, you must have the correct password for the user in that refreshed environment. If the passwords aren’t the same across environments, authentication will fail, so you need to update the applicable user’s credentials in the test environment to match (or otherwise ensure they are in sync). This keeps the login working smoothly for FDI.

The other options aren’t required here: resetting all passwords to a common value isn’t typically appropriate or secure, switching to OAuth changes the authentication method rather than solving a drifted password issue, and disabling environment isolation isn’t related to fixing login credentials.