Exam 350-901 All QuestionsBrowse all questions from this exam
Go to Exam
Question 5

An organization manages a large cloud-deployed application that employs a microservices architecture. No notable issues occur with downtime because the services of this application are redundantly deployed over three or more data center regions. However, several times a week reports are received about application slowness. The container orchestration logs show faults in a variety of containers that cause them to fail and then spin up brand new.

Which action must be taken to improve the resiliency design of the application while maintaining current scale?

    Correct Answer: A

    To improve the resiliency design of the application, updating the base image of the containers is a sound strategy. A base image is the foundational image from which container images are built. If there are faults causing containers to fail, updating the base image can address underlying issues with the software stacks or the configuration that the containers rely on. This ensures that the containers are running on the most secure and stable environments, reducing the likelihood of faults and improving the application's overall reliability and performance at scale.

Discussion
FR99Option: D

I go with 'D'

blurainOption: D

Believe D is right. Above the issue is not with the availability, but with the app's performance. Changing the base image of the containers, changing the cloud services platform, or simply increasing the number of containers may not address the root cause. Adding proper "try/catch(exception)" clauses allows the application to handle exceptions gracefully, which can prevent a full container crash and mitigate performance issues caused by the overhead of spinning up new containers.

blurainOption: A

The question states "container orchestration logs show faults". The faults cause the containers to fail. Application is not failing but can try to use resources that are not available on the containers. The most likely resolution is to update the base image of the containers, answer A.

sami777Option: A

The correct answer is A.

fbl

Why A please ?

romanknet

A. Most Dockerfiles start from a parent image. If you need to completely control the contents of your image, you might need to create a base image instead. https://docs.docker.com/glossary/#base_image B. Another cloud platform will not solve the problem if the container is not stable. C. If you increase the number of containers, they probability of individual container failures will be the same - it will not improve resiliency. D. The task doesn't say that the application is written in Python, but D is Python-specific. Thus, D doesn't looks correct.

romanknet

Correction: D is language specific In Python it will be try/except

MerlinTheWizard

try/catch is also Java or C++ for example, afaik, so question is not focused on a single language and should be understood as such (unless you want to have every single language mentioned there)

VincentVegaOption: D

Something wrong at aplication. What caused conteiner to fail. Main reason is unknown. So to troubleshoot issue you need use exception handling.For example "try" at python or "catch" at C++

VincentVega

Please also look q 7

djv_examOption: D

I go with D. B and C wrong for sure the dought is on the A. Why is it wrong for me, a container is made of layers, a base image and the changes that we put on top. We update the base if we detect vulnerabilities of something related to the image itsetl, my understanding is that the container is crashing from an application error. So I'll go with adding error control to the app - Answer D

architect_Option: A

I'd go with A. The questions says it´s a large cloud-deployed app employing microservices architecture. Based on https://www.appdynamics.com/topics/benefits-of-microservices - ... Each service can be developed, deployed, and managed independently, and can utilize different programming languages... ("D" option would imply all services of the app are written in Python) - ... the risk of downtime is reduced since developers can roll back an update or make changes to a module without redeploying the entire application.

jdmpkOption: D

The containers are immutable...all consistent. If there are spurious issues your only recourse is to collect more information which gives us D. Also enhancing monitoring improves the resiliency design. (My 2 bits)

blurainOption: D

The question states "container orchestration logs show faults". The faults cause the containers to fail. Application is not failing but can try to use resources that are not available on the containers. The most likely resolution is to update the base image of the containers, answer A.