Question

Difficulty: EasyIdentify design principles of the AWS Cloud

A startup is building a new mobile application backend. The development team wants to focus entirely on writing application code without the operational overhead of provisioning, patching, or managing virtual servers. Which AWS Cloud design principle is best demonstrated by choosing managed services like AWS Lambda and Amazon DynamoDB for this architecture?

  1. Services, not serversAnswer
  2. B
    Tight coupling of system components
  3. C
    Static over-provisioning of resources
  4. D
    Monolithic infrastructure design

Answer

Services, not servers
The principle of 'Services, not servers' recommends using AWS managed services to eliminate the need for customers to manage, patch, and provision virtual servers. By choosing managed offerings like AWS Lambda (serverless compute) and Amazon DynamoDB (serverless database), developers can focus entirely on application logic while AWS handles the underlying infrastructure.

Step-by-Step Solution

1
Analyze the requirements in the scenario.
The team wants to avoid provisioning, patching, and managing virtual servers, opting instead for managed services.
This helps identify which AWS design principle removes server management overhead.
2
Compare the scenario details with AWS Cloud design principles.
Using serverless and managed services like AWS Lambda and Amazon DynamoDB aligns directly with the principle of using services instead of managing servers.
This confirms the correct architectural principle being applied.

Key Concept

Services, not servers
Rate this question