Getting 1z0-997-22 Certification Made Easy!

Managing Traffic ManagementGEOLOCATIONSteering Policies

Geolocation steering policiesdistributeDNS 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 separateendpoint or set of endpoints for each region.

TheHealth Checks serviceallows 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 healthcheck, 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 ManagementGEOLOCATIONSteering Policies with Oracle Health Checks to fail over from one region to another

TheLoad Balancing serviceprovideshealth statusindicators that use your health check policies to report on the general health of your load balancers and their components.

ifyou 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.

Tag Variables

You can use a variable to set the value of a defined tag. When you add the tag to a resource, the variable resolves to the data it represents. You can use tag variables in defined tags and default tags.

Supported Tag Variables

The following tag variables are supported.

${iam.principal.name}The name of the principal that tagged the resource

${iam.principal.type}Thetype of principal that tagged the resource.

${oci.datetime}The date and time that the tag was created.

Consider the following example:

Operations.CostCenter="${iam.principal.name}at${oci.datetime}"

Operations is the namespace, CostCenter is the tag key, and the tag value contains two tag

variables${iam.principal.name}and${oci.datetime}. When you add this tag to a resource, the variable

resolves to your user name (the name of the principal that applied the tag) and a time date stamp for when youadded the tag.

user_name at 2019-06-18T18:00:57.604Z

The variable is replaced with data at the time you apply the tag. If you later edit the tag, the variable is gone and only the data remains. You can edit the tag value in all the ways you would edit anyother tag value. To create a tag variable, you must use a specific format.

${}Type a dollar sign followed by open and close curly brackets. The tag variable goes between the curly brackets. You can use tag variables with other tag variables andwith string values. Tag defaults let you specify tags to be applied automatically to all resources, at the time of creation, in a specificcompartment.This feature allows you to ensure that appropriate tags are applied at resource creation without requiring the user who is creating the resource to have access to the tag namespaces.

https://docs.cloud.oracle.com/en-us/iaas/Content/Tagging/Tasks/managingtagdefaults.htm