AWS - EC2 FundamentalsYou want to ensure your web server keeps the same public IP even if the instance stops and starts. Which approach is best?ACreate a new Elastic IP each time the instance startsBUse the instance's default public IP addressCAssign a private IP and use NAT gatewayDAllocate an Elastic IP and associate it with the instanceCheck Answer
Step-by-Step SolutionSolution:Step 1: Identify requirement for static public IPDefault public IP changes on stop/start; Elastic IP remains static.Step 2: Evaluate optionsUsing default IP or creating new Elastic IP each time does not ensure stability; private IP with NAT is indirect and complex.Final Answer:Allocate an Elastic IP and associate it with the instance -> Option DQuick Check:Elastic IP keeps public IP constant across restarts [OK]Quick Trick: Elastic IP keeps public IP fixed after instance restart [OK]Common Mistakes:MISTAKESRelying on default public IP which changesCreating new Elastic IPs repeatedlyUsing private IP without proper NAT setup
Master "EC2 Fundamentals" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS CLI - Installing AWS CLI - Quiz 7medium Cloud Computing Fundamentals - Why cloud over on-premises - Quiz 13medium Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 12easy EC2 Fundamentals - Instance states (running, stopped, terminated) - Quiz 3easy EC2 Fundamentals - Instance types and families - Quiz 15hard EC2 Fundamentals - Key pairs for SSH access - Quiz 13medium Identity and Access Management - IAM best practices - Quiz 8hard S3 Fundamentals - Why S3 matters for object storage - Quiz 14medium Security Groups and Network ACLs - Stateful behavior of security groups - Quiz 8hard Security Groups and Network ACLs - Stateless behavior of NACLs - Quiz 6medium