Oracle Cloud Platform Data Management 2018 Associate - 1Z1-950 模擬練習

A. Install Oracle DatabaseCreate data, flash recovery area, and redo storageCreate and start an Oracle Database

B. Create a compute nodeInstall Linux OS and Oracle DatabaseCreate networking and securityCreate and start an Oracle database and listener.

C. Create a compute nodeInstall Linux OSCreate data, flash recovery area, and redo storageCreate networking and security

D. Create a compute nodeInstall Linux OS and Oracle DatabaseCreate data, flash recovery area, and redo storageCreate networking and securityCreate and start an Oracle database and listener

E. Create a compute nodeInstall Linux OS and Oracle DatabaseCreate data, flash recovery area, and redo storageCreate and start an Oracle database

A. The DBA has not enabled native Oracle net encryption in the cloud through the CLOUD_ENCRYPTION_SERVER and CLOUD_CRYPTO_CHECKSUM_SERVER parameters in their cloud instance sqlnet.ora file.

B. They've specified an RSA key size that's too small to interface with the cloud.

C. They have explicitly set ENCRYPTION_CLIENT and CRYPTO_CHAECKSUM_CLIENT as
"rejected" in sqlnet.ora. This will create an unencrypted connection, which will automatically fail because it's insecure.

D. There sre no values assigned to the two sqlnet.ora parameters, CLOUD_ENCRYPTION_SERVER and/or CLOUD_CRYPTO_CHECKSUM_SERVER or they don't exist on the client.

E. The DBA has set ENCRYPTION_SERVER and CRYPTO_CHECKSUM_SERVER to "required" in the sqlnet.ora file. This will create an unencrypted connection, which will automatically fail because it's insecure.

A. Solaris cloud-keygen command

B. Windows ssh-rsa.exe command

C. Linux/UNIX ssh-keygen command

D. Putty PuTTYgen command

E. bzip ssh command

A. You forgot to enable port 3306.

B. The 'opc' user can be used to access MySQL only with the created SSH-Key.

C. You forgot to create the correct SSL/TLC certificate during the setup process.

D. The MySQL instance is still in the "Creation" process.

E. Only 'root' is allowed to access from non-localhost.

A. Enable SSH tunnel and access MySQL based on TCP/IP over SSH.

B. Switch to the Compute Cloud Service Dashboard and disable reject: *. public-internet.

C. Create a new SSH key for your ODBC connector.

D. Access to the OS (SSH) and MySQL (3306) are open by default.

E. Enable ora_p2admin_mysql, which opens port 3306 on the Access Rules tab.

A. Use the Database Cloud Service console to access the snapshots for MYDBCS1 and select "Create Database Clone" from the menu for the snapshot you want to use to create a linked clone. Repeat this step to create a second linked clone.

B. Use the Database Cloud Service wizard to create a new database deployment and then link its storage to the storage snapshot from the MYDBCS1 database deployment.

C. Create two storage snapshots of your MYDBCS1 database deployment by using the Database Cloud Service console.

D. Create one storage snapshot of your MYDBCS1 database deployment by using the Database Cloud Service console.

E. Use the Database Cloud Service console to access the snapshots for MYDBCS1 and select "Create Database Clone" from the menu for the snapshot you want to use to create a linked clone. Specify that you want to create two linked clones from the snapshot.

A. Invoke Data Pump Export on the on-premises database host and specify VERSION=12.

B. If the on-premises database is not at release version 11.2.0.3 or later, you must first upgrade it to at least
11.2.0.3

C. Invoke Data Pump Import on the Database Cloud Service compute node and specify VERSION=12.

D. Set all the tablespaces in the on-premises database that you plan to migrate to READ ONLY mode.

E. Set all the tablespaces in the on-premises database to READ ONLY mode regardless of whether they will be migrated or not.