Service Resiliency in Cloud-Native Applications | Oracle Exam 1Z0-1043-20

Service Resiliency in Cloud-Native Applications

Question

With the volume of communication that can happen between different components in cloud-native applications, it is vital to not only test functionality, but also service resiliency.

Which statement is true with regards to service resiliency? (Choose the best answer.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

The statement that is true with regards to service resiliency is A. Resiliency is about recovering from failures without downtime or data loss.

Resiliency refers to the ability of a system or service to continue operating in the face of failures or disruptions, and to recover quickly and reliably from any such events. In cloud-native applications, where there can be a large volume of communication between different components, it is important to ensure that the system can handle failures and disruptions without downtime or data loss.

Option A is correct because it accurately describes the goal of resiliency - to recover from failures without downtime or data loss. This means that the system should be able to detect and respond to failures in a timely manner, and be able to recover from those failures without impacting the availability or integrity of the system's data or services.

Option B is incorrect because the goal of resiliency is precisely to bring a service back to a functioning state after a failure. This is important to ensure that the service remains available to its users, and that any data or transactions that were in progress at the time of the failure are not lost.

Option C is also incorrect because resiliency testing can be done in production environments as well as test environments. In fact, it is often advisable to test resiliency in production environments, where the system is subject to real-world conditions and can be more thoroughly evaluated.

Option D is incorrect because resiliency is not about avoiding failures, but rather about responding to them in a way that minimizes their impact on the system and its users. While it is important to design systems that are robust and can handle a wide range of failure scenarios, it is impossible to completely avoid failures altogether, and resiliency measures are necessary to ensure that the system can continue to operate even in the face of those failures.