Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-1085-20 Topic 6 Question 10 Discussion

Actual exam question for Oracle's 1Z0-1085-20 exam
Question #: 10
Topic #: 6
[All 1Z0-1085-20 Questions]

Your company has deployed a business critical application in Oracle Cloud Infrastructure. What should you do to ensure that your application has the highest level of resilience and availability?

Show Suggested Answer Hide Answer
Suggested Answer: C

To design a high availability architecture, three key elements should be considered--- redundancy, monitoring, and failover:

1) Redundancymeans that multiple components can perform the same task. The problem of a single point of failure is eliminated because redundant components can take over a task performed by a component that has failed.

2) Monitoringmeans checking whether or not a component is working properly.

3) Failoveris the process by which a secondary component becomes primary when the primary component fails.

The best practices introduced here focus on these three key elements. Although high availability can be achieved at many different levels, including the application level and the cloud infrastructure level, here we will focus on the cloud infrastructure level.

An Oracle Cloud Infrastructureregionis a localized geographic area composed of one or more availability domains, each composed of three fault domains. High availability is ensured by a redundancy of fault domains within the availability domains.

Anavailability domainis one or more data centers located within a region. Availability domains are isolated from each other, fault tolerant, and unlikely to fail simultaneously. Because availability domains do not share physical infrastructure, such as power or cooling, or the internal availability domain network, a failure that impacts one availability domain is unlikely to impact the availability of others.

Afault domainis a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains let you distribute your instances so that they are not on the same physical hardware within a single availability domain. As a result, an unexpected hardware failure or a Compute hardware maintenance that affects one fault domain does not affect instances in other fault domains. You can optionally specify the fault domain for a new instance at launch time, or you can let the system select one for you.

All the availability domains in a region are connected to each other by a low-latency, high bandwidth network. This predictable, encrypted interconnection between availability domains provides the building blocks for both high availability and disaster recovery.


https://docs.oracle.com/en/solutions/design-ha/index.html#GUID-76ECDDB4-4CB1-4D93-9A6D-A8B620F72369

Contribute your Thoughts:

Currently there are no comments in this discussion, be the first to comment!


Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77