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

Amazon Exam CLF-C02 Topic 4 Question 30 Discussion

Actual exam question for Amazon's CLF-C02 exam
Question #: 30
Topic #: 4
[All CLF-C02 Questions]

A company is building a new application on AWS. The company needs the application to remain available if an individual application component fails.

Which design principle should the company use to meet this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: D

Loose coupling is a design principle that involves reducing dependencies between application components so that they can operate independently. This approach ensures that the failure of one component does not affect the availability of the others, thereby improving the application's fault tolerance and resilience. Disposable resources, automation, and rightsizing are valuable principles in cloud architecture, but they do not directly address the requirement of remaining available despite the failure of an individual component like loose coupling does. References:

AWS Well-Architected Framework - Design Principles


Contribute your Thoughts:

Novella
2 months ago
Loose coupling? That's how I describe my relationship with my alarm clock every morning.
upvoted 0 times
...
Hollis
2 months ago
Rightsizing? I thought that was just my daily struggle with finding the perfect-fitting pants.
upvoted 0 times
...
Colby
2 months ago
Automation? Isn't that just the fancy way of saying 'I let the robots do the work'?
upvoted 0 times
Kallie
21 days ago
That makes sense, thanks for explaining!
upvoted 0 times
...
Johna
1 months ago
In this case, the company should use loose coupling to ensure availability if a component fails.
upvoted 0 times
...
Nakisha
2 months ago
Yes, automation is like having robots do the work for you.
upvoted 0 times
...
...
Hyman
2 months ago
Disposable resources? I thought that was just my old high school notebooks.
upvoted 0 times
Colette
1 months ago
C: Disposable resources are like my old high school notebooks, not for this situation.
upvoted 0 times
...
Camellia
1 months ago
B: Yeah, that way the application can remain available if a component fails.
upvoted 0 times
...
Ming
1 months ago
A: I think the company should use loose coupling.
upvoted 0 times
...
...
Zita
2 months ago
I'm not sure about loose coupling. Maybe automation could also help in this scenario.
upvoted 0 times
...
Quiana
2 months ago
Loose coupling? That's what I do with my socks every morning!
upvoted 0 times
German
1 months ago
User 4: Haha, that's a funny way to think about it!
upvoted 0 times
...
Gerald
2 months ago
I always try to keep my socks loosely coupled too!
upvoted 0 times
...
Carin
2 months ago
Yeah, it helps the application stay available if one component fails.
upvoted 0 times
...
Thaddeus
2 months ago
Loose coupling sounds like a good idea for the application.
upvoted 0 times
...
...
Joye
2 months ago
I agree with Launa. Loose coupling helps in ensuring availability even if a component fails.
upvoted 0 times
...
Launa
3 months ago
I think the company should use loose coupling to meet the requirement.
upvoted 0 times
...

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