Joint Design & Preparation Flashcards
7 cards from real Architecting on AWS Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Joint Design & Preparation flashcards as text
A joint design team is architecting an event-driven system where multiple downstream services must react to the same order-placed event. Which AWS service best decouples the producer from multiple consumers?
Answer: Amazon SNS topic with SQS queue subscriptions per consumer
SNS fan-out to SQS queues ensures each consumer receives every event independently without competing for messages.
During joint capacity planning, the team determines that a relational workload will have predictable traffic with occasional 10x spikes. Which RDS feature handles spikes without over-provisioning permanently?
Answer: Aurora Serverless v2 with auto-scaling capacity units
Aurora Serverless v2 scales compute capacity in fine-grained increments within seconds, eliminating the need to provision for peak permanently.
A cross-team architecture review identifies that a critical Lambda function must process exactly once even if the triggering SQS message is delivered multiple times. Which design pattern addresses this?
Answer: Implement idempotency using a DynamoDB conditional write keyed on message ID
Storing a processed message ID in DynamoDB with a conditional write ensures the business logic executes exactly once even if Lambda retries.
Two teams are jointly preparing an AWS Well-Architected Framework review for their workload. Which pillar specifically addresses the ability to recover from failures and meet RTO/RPO goals?
Answer: Reliability
The Reliability pillar covers failure recovery, backup strategies, and meeting recovery time and point objectives.
During joint design for a containerized application, the team must choose between ECS on Fargate and EKS. Which factor most strongly favors EKS?
Answer: The application requires Kubernetes-native APIs, Helm charts, and advanced scheduling policies
EKS is the right choice when the workload or team requires Kubernetes-specific ecosystem tools like Helm, custom schedulers, or CRDs.
A team is jointly preparing their AWS infrastructure using Infrastructure as Code. They need to deploy the same environment across dev, staging, and production accounts. Which approach best supports this?
Answer: Use CloudFormation StackSets to deploy across multiple accounts and regions from a single template
StackSets automate template deployment across multiple accounts and regions from a single management account, ensuring consistency.
During joint architecture preparation, the compliance team requires that all S3 data be encrypted at rest with keys the customer controls and can audit. Which option satisfies this requirement?
Answer: SSE-KMS with a customer-managed KMS key and CloudTrail logging enabled
SSE-KMS with a customer-managed key gives full control over key policy, rotation, and provides an audit trail via CloudTrail for every key usage event.