AWS Certified Cloud Practitioner
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company needs an AWS design solution for a distributed system. The system's components need to be set up so that one system component cannot negatively impact another component. Which AWS architectural best practice will meet this requirement?
Real Exam
Community
RRitesh
A
Use request throttling
B
Use a stateful service
C
Implement automatic data backups
D
Implement loose coupling
Explanation:
Explanation
Loose coupling is the correct AWS architectural best practice that ensures one system component cannot negatively impact another component.
Why Loose Coupling?
-
Fault Isolation: In loosely coupled systems, components are independent and communicate through well-defined interfaces
-
Resilience: Failure in one component doesn't cascade to other components
-
Scalability: Components can scale independently without affecting others
-
Maintainability: Components can be updated or replaced without disrupting the entire system
Why Other Options Are Incorrect:
-
Request throttling: This manages API request rates but doesn't prevent component interdependencies
-
Stateful service: Stateful services actually create dependencies between components
-
Automatic data backups: This provides data protection but doesn't address component isolation
AWS Implementation Examples:
-
Use SQS for asynchronous communication
-
Implement API Gateway with Lambda functions
-
Use S3 for data storage instead of direct database connections
-
Employ event-driven architectures with SNS/SQS
Loose coupling is a fundamental principle in AWS Well-Architected Framework that promotes system resilience and fault tolerance.
Comments
Loading comments...