Table of Contents
Question
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. Set up a VPN connectivity between on-premises infrastructure and OCI and create routing tables to distribute traffic between them.
B. Use OCI Traffic management service with Failover steering policy and distribute traffic between OCI and on-premises infrastructure.
C. Use OCI Load Balancing service to distribute traffic between OCI and on-premises infrastructure.
D. Use OCI Traffic management service with Load Balancing steering policy and distribute traffic between OCI and on-premises infrastructure.
Answer
D. Use OCI Traffic management service with Load Balancing steering policy and distribute traffic between OCI and on-premises infrastructure.
Explanation 3
The correct answer to the question is D. Use OCI Traffic management service with Load Balancing steering policy and distribute traffic between OCI and on-premises infrastructure.
Here is a detailed explanation of why this is the correct answer and why the other options are incorrect:
- Option A is incorrect because setting up a VPN connectivity between on-premises infrastructure and OCI does not address the requirement of distributing traffic between them. VPN connectivity only provides secure and encrypted communication between the two networks, but it does not have any load balancing or traffic steering capabilities. You would still need to configure routing tables or other mechanisms to divert traffic between OCI and on-premises infrastructure based on the desired ratio.
- Option B is incorrect because using OCI Traffic management service with Failover steering policy does not meet the requirement of distributing traffic between OCI and on-premises infrastructure based on a predefined ratio. Failover steering policy only allows you to prioritize the order in which you want answers served in a policy (for example, Primary and Secondary) and leverages health checks to determine the health of answers in the policy. If the Primary Answer is determined to be unhealthy, DNS traffic will automatically be steered to the Secondary Answer. However, this option does not allow you to specify a percentage of traffic that you want to divert to each answer.
- Option C is incorrect because using OCI Load Balancing service does not meet the requirement of distributing traffic between OCI and on-premises infrastructure. OCI Load Balancing service only distributes traffic across multiple servers within your VCN. It does not have the ability to route traffic across different networks or regions. Moreover, OCI Load Balancing service only supports TCP and HTTP based traffic, which may not be suitable for all types of applications.
- Option D is correct because using OCI Traffic management service with Load Balancing steering policy meets the requirement of distributing traffic between OCI and on-premises infrastructure based on a predefined ratio. Load Balancing steering policy allows you to distribute traffic across multiple endpoints based on custom weights that you assign for each endpoint. You can use this feature to achieve ratio load balancing between OCI and on-premises infrastructure by assigning appropriate weights for each endpoint. For example, if you want to divert 40% of the traffic to OCI and 60% of the traffic to on-premises infrastructure, you can assign a weight of 40 for OCI endpoint and a weight of 60 for on-premises endpoint. OCI Traffic management service also leverages health checks to determine the health of endpoints and automatically distributes traffic to healthy endpoints. Additionally, OCI Traffic management service supports any type of DNS query, which makes it suitable for any type of application.
Reference
- Traffic Management (oracle.com)
- Managing Traffic Management steering policies (oracle.com)
- Information Center: OCI Networking – Domain Name System (DNS) and Traffic Management (oracle.com)
- Setting up active failover with OCI Traffic Management Steering (oracle.com)
- Load Balancing | Oracle
- Application load balancing on Oracle Cloud Infrastructure
- Defining Kubernetes Services of Type LoadBalancer (oracle.com)
- TCP or HTTP: Which one to use for Listener Protocol in OCI Load Balancer? (oracle.com)
- Getting Started with Traffic Management (oracle.com)
Oracle Cloud Infrastructure 2022 Architect Professional 1z0-997-22 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Oracle Cloud Infrastructure 2022 Architect Professional 1z0-997-22 exam and earn Oracle Cloud Infrastructure 2022 Architect Professional 1z0-997-22 certification.