AWS - ECS and FargateWhy does AWS Fargate require specifying both CPU and memory in task definitions rather than allowing dynamic allocation?ABecause Fargate cannot monitor resource usageBTo reserve resources and ensure predictable performance and billingCTo force users to over-provision resourcesDBecause containers cannot share resourcesCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand resource reservation in FargateSpecifying CPU and memory reserves resources upfront, ensuring tasks have predictable performance and cost.Step 2: Exclude incorrect reasonsFargate can monitor usage, does not force over-provisioning, and containers can share resources within limits.Final Answer:To reserve resources and ensure predictable performance and billing -> Option BQuick Check:Resource reservation = predictable performance and cost [OK]Quick Trick: CPU and memory set for predictable cost and performance [OK]Common Mistakes:Thinking Fargate cannot monitor usageBelieving it forces over-provisioningAssuming containers cannot share resources
Master "ECS and Fargate" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Advanced Security - Why defense in depth matters - Quiz 5medium Architecture Best Practices - Cost optimization pillar - Quiz 14medium CloudFormation - Outputs for cross-stack references - Quiz 15hard CloudFormation - Stack drift detection - Quiz 3easy ECS and Fargate - Task definitions - Quiz 5medium Route 53 - Route 53 with ELB integration - Quiz 15hard Route 53 - Failover routing for disaster recovery - Quiz 13medium Serverless Architecture - Lambda with DynamoDB Streams - Quiz 11easy Serverless Architecture - Lambda with DynamoDB Streams - Quiz 8hard Serverless Architecture - Serverless vs container decision - Quiz 15hard