A company runs a public-facing application that uses a Java-based web service via a RESTful API in their on-premises data center. Use of the API is expected to double with a new product launch. The business wants to migrate their application to Oracle Cloud Infrastructure (OCI) to meet the scale and reliability requirements. In order to achieve this, they will divert only 40% of the traffic to the new Apache Tomcat web servers running on OCI and serve the remaining 60% traffic through their on-premises infrastructure. Once the migration is complete and application works fine, they will divert all traffic to OCI. How can these requirements be met with the LEAST amount of effort?

• A. Use VPN connectivity between on premises Infrastructure and OCI and create routing tables to distribute the traffic between them.
• B. Use an OCI load Balancer and distribute the traffic between OCI and on premises infrastructure.
• C. Use OCI Traffic management service with failover steering policy and distribute the traffic between OCI and on premises infrastructure.
• D. Use OCI Traffic management service with Load Balancing steering policy and distribute the traffic between OCI and on premises infrastructure.

You are working on the migration of the web application infrastructure of your company from on-premises to Oracle Cloud Infrastructure. You need to ensure that the DNS cache entries of external clients will not direct them to the on-premises infrastructure after switching to the new infrastructure.
Which of the following options will minimize this problem?

• A. Reduce the TTL of the DNS records after the switch.
• B. Increase the TTL of the DNS records before the switch.
• C. Increase the TTL of the DNS records after the switch.
• D. DNS changes propagate fast enough that it is not necessary to take any action.
• E. Reduce the TTL of the DNS records before the switch.

A large London based eCommerce company is running Oracle DB System Virtual RAC database on Oracle Cloud Infrastructure (OCI) for their eCommerce application activity. They are launching a new product soon, which is expected to sell in large quantities all over the world.
The application architecture should have minimal cost, no data loss, no performance impacts during the database backup windows and should have minimal downtime.

• A. Turn off automatic backups from the eCommerce database, implement Oracle Active Data Guard with the standby database deployed on another availability domain, and take backups from the standby database.
• B. Launch a new VM RAC database in another availability domain, launch a compute instance, deploy Oracle GoldenGate on it and then configure it to replicate the data from the eCommerce Database over to the new RAC database using GoldenGate. Take backups from the new VM RAC database.
• C. Turn off automated backups from the eCommerce database, implement Oracle Data Guard with the Standby database deployed on another availability domain, take backups from the standby database.
• D. Launch a new VM RAC database in another availability domain, launch a compute instance, deploy Oracle GoldenGate on it and then configure bi-directional replication from the eCommerce Database over to the new VM RAC database using GoldenGate. Take backups from the new VM RAC database.

You are trying to troubleshoot the configuration of your Oracle Cloud Infrastructure (OCI) Load Balancing service. You have a backend HTTP service for which you have created a backend set in the load balancer. You have configured health checks for the backend set. Although the health checks appear good, customers sometimes experience transaction failures.
Which of the following options will definitely lead to this problem?

• A. You are NOT using regional subnets in your Virtual Cloud Network. With Availability Domain (AD) specific subnet. the compute instances of the backend service running in the subnet have issues when the AD is down.
• B. You are using iSCI for block volume attachment to the compute instances in your backed HTTP service. TCP/IP configuration of your block volume attachment is not configured correctly, leading to issues in your backend service.
• C. You are using OCI Domain Name System. You have misconfigured the 'A' record with the wrong IP address leading to requests not getting routed correctly.
• D. You are running a TCP-level health check against your HTTP service. The TCP handshake can succeed and indicate that the service is up even when the HTTP service has issues.

You are working for a Travel company and your travel portal application is a collection of microservices that run on Oracle Cloud Infrastructure Container Engine for Kubernetes. As per the recent security overview, you have noticed that Oracle has published a newer image of the Operating System used by the worker nodes. You want to make sure that your application doesn't face any downtime but at the same time the worker nodes gets upgraded to the latest version of the Operating System.
What should you do to get this upgrade done without application downtime? (Choose the best answer.)

• A. 1. Create a new node pool using the latest available Operating System image. 2. Run kubectl cordon <node name> against all the worker nodes in the old pool to stop any new application pods to get scheduled 3. Run kubectl drain <node name> """"delete""local""data """"force """"ignore""daemonsets to evict any Pods that are running 4. Delete the old node pool
• B. 1. Run kubectl cordon <node name> against all the worker nodes in the old pool to stop any new application pods to get scheduled 2. Run kubectl drain <node name> """"delete""local""data """"force """"ignore""daemonsets to evict any Pods that are running 3. Download the patches for the new Operating System image 4. Patch the worker nodes to the latest Operating System image
• C. 1. Shutdown the worker nodes 2. Create a new node pool 3. Manually schedule the pods on the newly built node pool
• D. 1. Create a new node pool using the latest available Operating System image 2. Run kubectl taint nodes """"all node""role.kubernetes.io/master"" 3. Delete the old node pool