AWS - API GatewayYou want to deploy an API to two different stages: 'test' and 'prod'. How should you manage deployments?ACreate separate deployments for each stage with the same API versionBDeploy once and both stages update automaticallyCUse one stage and rename it as neededDDeploy only to 'prod' and link 'test' to itCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand stage deployment independenceEach stage points to a specific deployment. To have different stages, create separate deployments for each.Step 2: Evaluate other optionsDeploying once does not update multiple stages automatically. Renaming stages or linking stages is not supported.Final Answer:Create separate deployments for each stage with the same API version -> Option AQuick Check:Separate deployments needed per stage [OK]Quick Trick: Each stage needs its own deployment [OK]Common Mistakes:MISTAKESAssuming one deploy updates all stagesTrying to rename stages dynamicallyLinking stages incorrectly
Master "API Gateway" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - API keys and usage plans - Quiz 12easy API Gateway - API Gateway throttling - Quiz 11easy Auto Scaling - Launch templates - Quiz 14medium CloudWatch - CloudWatch alarms - Quiz 12easy Elastic Load Balancing - ALB vs NLB decision - Quiz 14medium Elastic Load Balancing - Cross-zone load balancing - Quiz 7medium RDS and Relational Databases - Why managed databases matter - Quiz 2easy RDS and Relational Databases - Multi-AZ deployment for high availability - Quiz 14medium SNS and SQS - Standard vs FIFO queues - Quiz 10hard SNS and SQS - Dead letter queues - Quiz 8hard