Examkin

Question

Difficulty: MediumIdentify design principles of the AWS Cloud

A startup is developing a mobile application and needs to implement user registration, sign-in, and access control. To minimize administrative overhead and avoid managing virtual servers, the development team decides to use Amazon Cognito instead of deploying and maintaining a custom authentication system on Amazon EC2. Which AWS Cloud design principle does this decision best represent?

  1. A
    Elasticity
  2. B
    Loose coupling
  3. Services not serversAnswer
  4. D
    Scalability

Answer

Services not servers
By utilizing Amazon Cognito, a fully managed service, the startup delegates the responsibilities of provisioning, scaling, patching, and maintaining servers to AWS. This directly aligns with the 'services not servers' design principle, which advises using managed services to reduce operational overhead.

Step-by-Step Solution

1
Analyze the scenario and identify the primary architectural goal of the development team.
The team wants to implement user authentication while avoiding the provisioning, scaling, patching, and maintenance of virtual servers (Amazon EC2).
Understanding the core business and technical driver helps map the decision to the correct AWS design principle.
2
Evaluate the AWS Cloud design principles against the choice of using Amazon Cognito instead of EC2.
Using Amazon Cognito represents opting for a fully managed service where AWS manages the underlying infrastructure. This aligns with the 'services not servers' design principle.
The principle of 'services not servers' encourages offloading infrastructure management to managed services so developers can focus on application code.

Key Concept

Services not servers (managed services)
Estimated Time:1m 0s
Rate this question

Topics

Identify design principles of the AWS Cloud

More questions from this topic