Question 1: Assigning a Fixed Public IPv4 to an EC2 Instance

Question:

You have launched an EC2 instance that will host a NodeJS application. After installing all the required software and configuring your application, you noted down the EC2 instance public IPv4 so you can access it. Then, you stopped and then started your EC2 instance to complete the application configuration. After restart, you can't access the EC2 instance, and you found that the EC2 instance public IPv4 has changed. What should you do to assign a fixed public IPv4 to your EC2 instance?

Options:

🔘 Allocate an Elastic IP and assign it to your EC2 instance ✅ (Correct Answer)

⚪ From inside your EC2 instance OS, change network configuration from DHCP to static and assign it a public IPv4

⚪ Contact AWS Support and request a fixed public IPv4 to your EC2 instance

⚪ This can't be done, you can only assign a fixed private IPv4 to your EC2 instance

💡 Explanation:

• AWS assigns a new public IPv4 each time an EC2 instance stops and starts.
• Elastic IPs are static public IPs that remain the same across reboots.

Question 2: Choosing the Right EC2 Placement Group for High Performance

Question:

You have an application performing big data analysis hosted on a fleet of EC2 instances. You want to ensure your EC2 instances have the highest networking performance while communicating with each other. Which EC2 Placement Group should you choose?

Options:

⚪ Spread Placement Group

🔘 Cluster Placement Group ✅ (Correct Answer)

⚪ Partition Placement Group

💡 Explanation: