nerdexam
Oracle

1Z0-997-20 · Question #66

You have deployed a web application targeting a global audience across multiple Oracle Cloud Infrastructure (OCI) regions. You decide to use Traffic Management Geo-Location based Steering Policy to…

The correct answer is B. You did not setup an HTTP Health Check associated with Load Balancer public IP in the disabled E. You did not correctly setup the Load Balancer HTTP health check policy associated with backend. Managing Traffic Management GEOLOCATION Steering Policies Geolocation steering policies distribute DNS traffic to different endpoints based on the location of the end user. Customers can define geographic regions composed of originating continent, countries or states/provinces…

Design for Disaster Recovery

Question

You have deployed a web application targeting a global audience across multiple Oracle Cloud Infrastructure (OCI) regions. You decide to use Traffic Management Geo-Location based Steering Policy to serve web requests to users from the region closets to the user. Within each region you have deployed a public load balancer with 4 servers in a backend set. During a DR test disable all web servers in one of the regions however, traffic Management does not automatically direct all users to the other region. Which two are possible causes?

Options

  • AYou did not setup a Route Table associated with load Balancer's subnet
  • BYou did not setup an HTTP Health Check associated with Load Balancer public IP in the disabled
  • CRather than using Geo-Location based Steering Policy, you should use Failover Policy Type to
  • DOne of the two working web servers In the other region did not pass Its HTTP health check
  • EYou did not correctly setup the Load Balancer HTTP health check policy associated with backend

How the community answered

(50 responses)
  • A
    8% (4)
  • B
    70% (35)
  • C
    16% (8)
  • D
    6% (3)

Explanation

Managing Traffic Management GEOLOCATION Steering Policies Geolocation steering policies distribute DNS traffic to different endpoints based on the location of the end user. Customers can define geographic regions composed of originating continent, countries or states/provinces (North America) and define a separate endpoint or set of endpoints for each region. The Health Checks service allows you to monitor the health of IP addresses and hostnames, as measured from geographic vantage points of your choosing, using HTTP and ping probes. After configuring a health check, you can view the monitor's results. The results include the location from which the host was monitored, the availability of the endpoint, and the date and time the test was performed. Also you can Combine Managing Traffic Management GEOLOCATION Steering Policies with Oracle Health Checks to fail over from one region to another The Load Balancing service provides health status indicators that use your health check policies to report on the general health of your load balancers and their components. if you misconfigure the health check Protocol between the Load balancer and backend set that can lead to not get an accurate response as example below If you run a TCP-level health check against an HTTP service, you might not get an accurate response. The TCP handshake can succeed and indicate that the service is up even when the HTTP service is ly configured or having other issues. Although the health check appears good customers might experience transaction failures.

Topics

#Traffic Management#Geo-Location Steering#health checks#load balancer failover

Community Discussion

No community discussion yet for this question.

Full 1Z0-997-20 Practice