Option A is incorrect because rclone is not a tool provided by Object Storage.It is a third-party command-line program that can sync files to and from various cloud storage providers, including Object Storage1.

Option B is incorrect because contiguous numbers are not required for each part.Object Storage constructs the object by ordering part numbers in ascending order only if they are not specified in the commit operation1.

Option C is correct because after initiating a multipart upload, you need to explicitly commit or abort it.Otherwise, it remains active until it expires after 24 hours1.

Option D is incorrect because Object Storage does not provide APIs to split a file into multiple parts.You need to use your own tools or programs to do that1.

Option E is correct because you can list all parts that have been uploaded for an active multipart upload by using the ListMultipartUploadParts API or CLI command.However, you cannot list information for an individual object part by using the GetObject API or CLI command1.

Option A is correct because using multiple OCI Data Transfer Appliances to transfer data to OCI is the most effective service to use to migrate the data to OCI given the time constraints. This option can securely move terabytes or petabytes of data between on-premises data centers and the cloud in days instead of weeks or months.It also avoids using the public internet, which can be slow, unreliable, and expensive45.

Option B is incorrect because setting up an OCI Storage Gateway to connect your data center and your VCN and uploading all data to OCI is not effective given the time constraints. This option requires using the public internet, which can be intermittent due to the damages caused by the hurricane.It also requires installing and configuring a software appliance on your premises, which can add complexity and overhead6.

Option C is incorrect because setting up a hybrid network by launching a 1Gbps FastConnect virtual circuit between your data center and OCI and using OCI Object Storage multipart upload tool to automate the migration of your data to OCI is not feasible given the time constraints. This option requires provisioning a FastConnect circuit, which can take several days or weeks depending on your network provider. It also requires using a public internet backup path, which can be unreliable due to the hurricane .

Option D is incorrect because setting up an OCI Storage Gateway to connect your data center and your VCN and uploading all data to OCI using OCI Storage Gateway Cloud Sync tool is not effective given the time constraints. This option requires using the public internet, which can be intermittent due to the damages caused by the hurricane.It also requires installing and configuring a software appliance on your premises, which can add complexity and overhead6.

Option E is incorrect because uploading the data to OCI using OCI Object Storage multipart upload tool is not effective given the time constraints. This option requires using the public internet, which can be slow, unreliable, and expensive due to the hurricane and the large amount of data involved

Option A is correct because creating a FastConnect virtual circuit with Microsoft Azure as the provider to establish a private interconnect between the application tier running in the Azure Virtual Network and the OCI VCN that contains the Oracle Databases is the most-fault tolerant and secure solution for this customer. This option provides low latency, high throughput, and consistent network performance across the clouds.It also avoids exposing the traffic to the public internet, which enhances security and reliability12.

Option B is incorrect because creating an encrypted, Virtual Private Network connection between the Microsoft Azure Virtual Network that contains the application tier and the OCI Virtual Cloud Network (VCN) that contains the Oracle Databases is not as fault-tolerant and secure as option A.This option relies on the public internet for connectivity, which can introduce latency, bandwidth limitations, and security risks12.

Option C is incorrect because using an OCI Virtual Cloud Network remote peering connection to create a remote network connection between the application tier running in Microsoft Azure Virtual Network and Oracle Databases running in the OCI Virtual Cloud Network (VCN) is not possible. Remote peering connections can only be used to connect two VCNs within the same region or across regions within OCI.They cannot be used to connect a VCN with a VNet in another cloud provider3.

Option A is correct because deploying a Virtual Machine RAC DB system on OCI and using the ZDM tool for the database migration is a method that can minimize the impact on the application. ZDM is a software solution that allows you to directly and seamlessly migrate your on-premises Oracle Databases to the Oracle Cloud, whether in OCI or ExaCC.ZDM supports a wide range of Oracle Database versions, and ensures that there is minimal to no production downtime during the migration1.ZDM also supports migrating RAC databases to RAC databases on OCI2.

Option B is incorrect because deploying an Autonomous Transaction Processing Database on OCI and using the MV2ADB tool for the database migration is not a suitable method for this scenario. MV2ADB is a command-line tool that allows migrating data from an Oracle database on-premise to Oracle Autonomous Database in ''one-click''.It is based on Oracle Data Pump export and import utility3.However, MV2ADB does not support migrating RAC databases to Autonomous Database, nor does it support migrating Enterprise Edition databases to Autonomous Database4.

Option C is incorrect because deploying an Exadata Cloud Service Base rack and using Oracle Data Pump tool to migrate the data from customer on-premises to OCI is not a method that can minimize the impact on the application.Oracle Data Pump is a technology that enables you to move data and metadata from one database to another5. However, Oracle Data Pump requires intermediate storage for the dump files, which can add complexity and overhead. It also requires downtime during the export and import operations, which can affect the availability of the application.

To complete the task of creating a public API Gateway and invoking a private function in OCI, you can follow these steps:

To create a new public API Gateway in your compartment named exam-gateway, follow these steps:

In the OCI Console, go toDeveloper Servicesand clickAPI Gateway.

Select your assigned compartment from the list on the left.

ClickCreate Gateway.

Enterexam-gatewayas theNameand selectPublicas theType. You can also add a description for the gateway if you want.

Select your previously created VCN from theVCNdropdown menu and select any subnet from theSubnetdropdown menu. You can also enable logging for the gateway if you want.

ClickCreate. This will create a new public API Gateway in your compartment that can expose your functions to the internet.

To create a new API Deployment named exam-deployment using /v1 as the path prefix in exam-gateway, follow these steps:

In the OCI Console, go toDeveloper Servicesand clickAPI Gateway.

Select your assigned compartment from the list on the left and click on your previously created gateway (exam-gateway).

ClickDeploymentson the left panel and then clickCreate Deployment.

Enterexam-deploymentas theNameand selectFrom Scratchas theSpecification Type. You can also add a description for the deployment if you want.

Enter /v1 as thePath Prefixand leave the other fields as default. ClickNext.

To create a new route by using /hello as the path and GET as the method, follow these steps:

In the Create Deployment dialog box, clickAdd Route.

Enter /hello as thePath, select GET as theMethod, and select Oracle Functions as theType.

Select your previously created function (hello-python) from theFunction Namedropdown menu and leave the other fields as default. ClickSave Changes. This will create a new route that will invoke your function when you send a GET request to /v1/hello.

To create a new stateful CIDR Ingress Rule that allows for TCP HTTPS traffic (port 443) from all IP addresses and ports in the default Security List for exam-vcn, follow these steps:

In the OCI Console, go toNetworkingand clickVirtual Cloud Networks.

Select your assigned compartment from the list on the left and click on your previously created VCN (exam-vcn).

ClickSecurity Listson the left panel and then click on the default security list for your VCN.

ClickEdit All Rulesand then clickAdd Ingress Ruleunder the Ingress Rules section.

Enter 0.0.0.0/0 as theSource CIDR, select TCP as theIP Protocol, and enter 443 as both theSource Port Rangeand theDestination Port Range. You can also add a description for the rule if you want.

ClickSave Security List Rules. This will create a new stateful CIDR Ingress Rule that will allow HTTPS traffic from any source to reach your API Gateway.

To use curl to call the function via your API Gateway deployment, follow these steps:

In the OCI Console, go toDeveloper Servicesand clickAPI Gateway.

Select your assigned compartment from the list on the left and click on your previously created gateway (exam-gateway).

ClickDeploymentson the left panel and then click on your previously created deployment (exam-deployment).

Copy the value of the Endpoint URL field. This is the base URL for your API Deployment.

In a terminal window, enter the following command:

curl -k -X GET {deployment-endpoint}/v1/hello

where {deployment-endpoint} is the base URL that you copied.

For example, if your deployment endpoint is https://abc123xyz456.apigateway.us-ashburn-1.oci.customer-oci.com, your command would be:

curl -k -X GET https://abc123xyz456.apigateway.us-ashburn-1.oci.customer-oci.com/v1/hello

This will send a GET request to your API Deployment and invoke your function. You should see a response similar to this:

{'message': 'Hello World!'}

Topic 2, Multiple Choice Questions