AWS VPC Interview Questions and Answers Pdf

AWS Certified Solutions Architect Begins the 50 Top Funding IT Certifications. Surely, AWS Architect situation is the whole of the familiar sought subsequent amongst IT projects. We at SVR are dedicated to accommodating you enhance your business in sync with enterprise specifications. That’s why we have designed a table of AWS Architect Interview questions and answers that will several notices requested through your interview. If you’ve visited an Amazon Web Services Training interview or have further questions exceeding whatever we have included, you can maximize the Cloud computing profession possibilities that are sure to get your form by practicing AWS Certified Solutions Architect Training with SVR. You can communicate the AWS Architect certification exam later the course at SVR Technologies.

AWS VPC Interview Questions:

Here are the best 50 objective type sample AWS Interview questions and their answers are presented simply following them. Certain example questions are composed of professionals from SVR technologies who leads for Amazon Web Services Job Support Online to give you an idea of a type of questions which may be claimed in an interview. We have acquired to provide accurate answers to all the questions.

1. What is Amazon Virtual Private Cloud (Amazon VPC)?
Answer: Amazon VPC lets you provision a logically isolated section of the Amazon Web Services (AWS) cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including a selection of your IP address range, creation of subnets, and configuration of route tables and network gateways. You can also create a hardware Virtual Private Network (VPN) connection between your corporate datacenter and your VPC and leverage the AWS cloud as an extension of your corporate datacenter. You can easily customize the network configuration for your Amazon VPC. For example, you can create a public-facing subnet for your web servers that have access to the Internet, and place your backend systems such as databases or application servers in a private-facing subnet with no Internet access. You can leverage multiple layers of security, including security groups and network access control lists, to help control access to Amazon EC2 instances in each subnet.

Get Started with AWS for Free

The following diagram shows the architecture that you’ll create as you complete the exercise in this guide. The security group that you set up and associate with the instance allows traffic only through specific ports, locking down communication with the instance according to the rules that you specify. Using an Elastic IP address (EIP) enables an instance in an otherwise private, to be reached from the Internet through an Internet gateway (for example, it could act as a web server).

2. What are the connectivity options for my VPC?
Answer: You may connect your VPC to:
The Internet (via an Internet gateway)
Your corporate data center using a Hardware VPN connection (via the virtual private gateway)
Both the Internet and your corporate data center (utilizing both an Internet gateway and a virtual private gateway)
Other AWS services (via Internet gateway, NAT, virtual private gateway, or VPC endpoints)
Other VPCs (via VPC peering connections)

3. How do you connect my VPC to the Internet?
Answer: Amazon VPC supports the creation of an Internet gateway. This gateway enables Amazon EC2 instances in the VPC to directly access the Internet.AWS Video Training

4. What are the components of Amazon VPC?

Amazon VPC comprises a variety of objects that will be familiar to customers with existing networks:

  • A Virtual Private Cloud (VPC): A logically isolated virtual network in the AWS cloud. You define a VPC’s IP address space from a range you select.
  • Subnet: A segment of a VPC’s IP address range where you can place groups of isolated resources.
  • Internet Gateway: The Amazon VPC side of a connection to the public Internet.
  • NAT Gateway: A highly available, managed Network Address Translation (NAT) service for your resources in a private subnet to access the Internet.
  •  Hardware VPN Connection: A hardware-based VPN connection between your Amazon VPC and your datacenter, home network, or co-location facility.
  • Virtual Private Gateway: The Amazon VPC side of a VPN connection.
  • Customer Gateway: Your side of a VPN connection.
  • Router: Routers interconnect subnets and direct traffic between Internet gateways, virtual private gateways, NAT gateways, and subnets.
  • Peering Connection: A peering connection enables you to route traffic via private IP addresses between two peered VPCs.
  • VPC Endpoint for S3: Enables Amazon S3 access from within your VPC without using an Internet gateway or NAT, and allows you to control the access using VPC endpoint policy
  • Egress-only Internet Gateway: A stateful gateway to provide egress only access for IPv6 traffic from the VPC to the Internet.

5. What are the steps to build a custom VPC?
Answer: Below is the steps to building a custom VPC:

1. Create a VPC
2. Create subnets
3. Create an internet gateway (IGW)
4. Attach the new IGW to your VPC
5. Create a new route table (RT)
6. Add the IGW as a route to the new RT
7. Add a subnet to the RTs subnet associations (this will be the public-facing subnet)
8. Create webserver (public subnet) and database server (private subnet) instances
9. Create a new security group for the NAT instance
10. Add HTTP and HTTPS inbound rules that allow traffic from the private subnets IP
11. Create a NAT instance (public subnet)
Community AMIs
Choose the first image
Diable Auto-assign Public IP
Add it to the NAT security group
12. Create an Elastic IP
12. Associate the Elastic IP to the NAT
13. Disable Source/Destination Checks for the NAT
14. Add the NAT instance as a route to the initial VPC RT

6. Why should you use Amazon VPC, Advantage of using AWS VPC?
Answer: Advantages of using AWS VPC are the following:
Intuitive and Easy-to-Use
When AWS was built, the prime motivation was to create a platform where application providers, vendors, and ISVs could swiftly and safely host their apps. Today, AWS fulfills this task, for both existent apps and new SaaS-based apps. The AWS Management Console allows you to access the AWS’s app-hosting platform
 Friendly to the Pockets
There are no long-drawn contracts or up-front demands when you sign up with AWS. You only have to pay for the resources that you use, which includes the storage, computing power and other tools. The AWS Economics Center provides a detailed view of different pricing options.
High Functionality and Scalability
Depending on the demand you receive, you can scale your app using the AWS tools. Since AWS has an outstanding infrastructure, you can make use of the computing and storage resources whenever required.
 Dynamic and Flexible Operations
With AWS, you can customize your resources for exactly the project you intend to fulfill. You can choose the web application platform, the operating system, the programming language, database, and other resources. This will ensure that you can easily migrate the existent apps and also lock these options while building new apps.
Built over decades, AWS comes with impeccable global computing infrastructure. The testimony of its perfection is measurable through the consistent increase in their clientele which passed over $7.3 billion in late 2015.
AWS undertakes operational, software and physical measures to make sure that your web and app are secure. You can restrict access to AWS resources by employing IAS (Identity and Access Management) where different roles can be attributed to varying privileges. You can also use VPX where services can be hosted on a private network that cannot be approached through the internet.

7. What is the difference between stateful and stateless filtering?
Answer: Stateful filtering tracks the origin of a request and can automatically allow the reply to the request to be returned to the originating computer. For example, a stateful filter that allows inbound traffic to TCP port 80 on a web server will allow the return traffic, usually on a high numbered port (e.g., destination TCP port 63, 912) to pass through the stateful filter between the client and the webserver. The filtering device maintains a state table that tracks the origin and destination port numbers and IP addresses. Only one rule is required on the filtering device: Allow traffic inbound to the web server on TCP port 80.

Stateless filtering, on the other hand, only examines the source or destination IP address and the destination port, ignoring whether the traffic is a new request or a reply to a request. In the above example, two rules would need to be implemented on the filtering device: one rule to allow traffic inbound to the web server on TCP port 80, and another rule to allow outbound traffic from the webserver (TCP port range 49, 152 through 65, 535).

8. Within Amazon VPC, can you use SSH key pairs created for instances within Amazon EC2, and vice versa?
Answer: Yes

9. Can Amazon EC2 instances within a VPC communicate with Amazon EC2 instances, not within a VPC?
Answer: Yes. If an Internet gateway has been configured, Amazon VPC traffic bound for Amazon EC2 instances, not within a VPC traverses the Internet gateway and then enters the public AWS network to reach the EC2 instance. If an Internet gateway has not been configured, or if the instance is in a subnet configured to route through the virtual private gateway, the traffic traverses the VPN connection, egresses from your datacenter, and then re-enters the public AWS network.

10. Why can’t you ping the router, or my default gateway, that connects my subnets?
Answer: Ping (ICMP Echo Request and Echo Reply) requests to the router in your VPC is not supported. Ping between Amazon EC2 instances within VPC is supported as long as your operating system’s firewalls, VPC security groups, and network ACLs permit such traffic.

11. Can you monitor the network traffic in your VPC?
Answer: Yes. You can use the Amazon VPC Flow Logs feature to monitor the network traffic in your VPC.

12. Within which Amazon EC2 region(s) is Amazon VPC available?
Answer: Amazon VPC is currently available in multiple Availability Zones in all Amazon EC2 regions.

13. Can a VPC span multiple Availability Zones ?
Answer: Yes.

14. Can you use your existing AMIs in Amazon VPC?
Answer: You can use AMIs in Amazon VPC that are registered within the same region as your VPC. For example, you can use AMIs registered in us-east-1 with a VPC in us-east-1. More information is available in the Amazon EC2 Region and Availability Zone FAQ.

15. Can you employ Amazon CloudWatch within Amazon VPC?
Answer: Yes 

16. How do you specify which Availability Zone my Amazon EC2 instances are launched in?
Answer: When you launch an Amazon EC2 instance you must specify the subnet on which to launch the instance. The instance will be launched in the Availability Zone associated with the specified subnet.

17. Are there any bandwidth limitations for Internet gateways?
Do you need to be concerned about its availability? Can it be a single point of failure?
Answer: No. An Internet gateway is horizontally-scaled, redundant, and highly available. It imposes no bandwidth constraints.

18. How do you secure Amazon EC2 instances running within my VPC?
Answer: Amazon EC2 security groups can be used to help secure instances within an Amazon VPC. Security groups in a VPC enable you to specify both inbound and outbound network traffic that is allowed to or from each Amazon EC2 instance. Traffic which is not explicitly allowed to or from an instance is automatically denied.

In addition to security groups, network traffic entering and exiting each subnet can be allowed or denied via network Access Control Lists (ACLs).

19. What are the differences between security groups in a VPC and network ACLs in a VPC?
Answer: Security groups in a VPC specify which traffic is allowed to or from an Amazon EC2 instance. Network ACLs operate at the subnet level and evaluate traffic entering and exiting a subnet. Network ACLs can be used to set both Allow and Deny rules. Network ACLs do not filter traffic between instances in the same subnet. In addition, network ACLs perform stateless filtering while security groups perform stateful filtering.

20. How do you determine which Availability Zone my subnets are located in?
Answer: When you create a subnet you must specify the Availability Zone in which to place the subnet. When using the VPC Wizard, you can select the subnet’s Availability Zone in the wizard confirmation screen. When using the API or the CLI you can specify the Availability Zone for the subnet as you create the subnet. If you don’t specify an Availability Zone, the default “No Preference” option will be selected and the subnet will be created in an available Availability Zone in the region.


21. When you call DescribeInstances(), do you see all of my Amazon EC2 instances, including those in EC2-Classic and EC2-VPC?
Answer: Yes. DescribeInstances() will return all running Amazon EC2 instances. You can differentiate EC2-Classic instances from EC2-VPC instances by an entry in the subnet field. If there is a subnet ID listed, the instance is within a VPC.

22. When you call DescribeVolumes(), do you see all of my Amazon EBS volumes, including those in EC2-Classic and EC2-VPC?
Answer: Yes. DescribeVolumes() will return all your EBS volumes.

23. How many Amazon EC2 instances can you use within a VPC?
Answer: You can run any number of Amazon EC2 instances within a VPC, so long as your VPC is appropriately sized to have an IP address assigned to each instance. You are initially limited to launching 20 Amazon EC2 instances at any one time and a maximum VPC size of /16 (65,536 IPs). If you would like to increase these limits, please complete the following form.

24. Can you employ Auto Scaling within Amazon VPC?
Answer: Yes

25. What is the IP range of a default VPC?
Answer: The default VPC CIDR is Default subnets use /20 CIDRs within the default VPC CIDR. 

26. How many default VPCs can you have?
Answer: You can have one default VPC in each AWS region where your Supported Platforms attribute is set to “EC2-VPC”.

27. How many default subnets are in a default VPC?
Answer: One default subnet is created for each Availability Zone in your default VPC.

28. Can you launch Amazon EC2 Cluster Instances in a VPC?
Answer: Yes. Cluster instances are supported in Amazon VPC, however, not all instance types are available in all regions and Availability Zones. Learn AWS Training Online From Real-Time Experts

29. What is a default VPC?
Answer: A default VPC is a logically isolated virtual network in the AWS cloud that is automatically created for your AWS account the first time you provision Amazon EC2 resources. When you launch an instance without specifying a subnet-ID, your instance will be launched in your default VPC.

30. What is the advantage of a default VPC?
Answer: When you launch resources in a default VPC, you can benefit from the advanced networking functionalities of Amazon VPC (EC2-VPC) with the ease of use of Amazon EC2 (EC2-Classic). You can enjoy features such as changing security group membership on the fly, security group egress filtering, multiple IP addresses, and multiple network interfaces without having to explicitly create a VPC and launch instances in the VPC.

31. What accounts are enabled for default VPC?
Answer: If your AWS account was created after March 18, 2013, your account may be able to launch resources in a default VPC. See this Forum Announcement determine which regions have been enabled for the default VPC feature set. Also, accounts created prior to the listed dates may utilize default VPCs in any default VPC enabled region in which you’ve not previously launched EC2 instances or provisioned Amazon Elastic Load Balancing, Amazon RDS, Amazon ElastiCache, or Amazon Redshift resources.

32. How can you know if my account is configured to use a default VPC?
Answer: The Amazon EC2 console indicates which platforms you can launch instances in for the selected region and whether you have a default VPC in that region. Verify that the region you’ll use is selected in the navigation bar. On the Amazon EC2 console dashboard, look for “Supported Platforms” under “Account Attributes”. If there are two values, EC2-Classic and EC2-VPC, you can launch instances into either platform. If there is one value, EC2-VPC, you can launch instances only into EC2-VPC. Your default VPC ID will be listed under “Account Attributes” if your account is configured to use a default VPC. You can also use the EC2 DescribeAccountAttributes API or CLI to describe your supported platforms.

33. Can you create other VPCs and use them in addition to my default VPC?
Answer: Yes. To launch an instance into nondefault VPCs you must specify a subnet-ID during instance launch.

34. Can you create additional subnets in my default VPC, such as private subnets?
Answer: Yes. To launch into nondefault subnets, you can target your launches using the console or the –subnet option from the CLI, API, or SDK.

35. Will you need to know anything about Amazon VPC in order to use a default VPC?
Answer: No. You can use the AWS Management Console, AWS EC2 CLI, or the Amazon EC2 API to launch and manage EC2 instances and other AWS resources in a default VPC. AWS will automatically create a default VPC for you and will create a default subnet in each Availability Zone in the AWS region. Your default VPC will be connected to an Internet gateway and your instances will automatically receive public IP addresses, just like EC2-Classic. 

36. Can you use my existing Amazon EBS snapshots?
Answer: Yes, you may use Amazon EBS snapshots if they are located in the same region as your VPC. More details are available in the Amazon EC2 Region and Availability Zone FAQ.

37. Can you boot an Amazon EC2 instance from an Amazon EBS volume within Amazon VPC?
Answer: Yes, however, an instance launched in a VPC using an Amazon EBS-backed AMI maintains the same IP address when stopped and restarted. This is in contrast to similar instances launched outside a VPC, which get a new IP address. The IP addresses for any stopped instances in a subnet are considered unavailable.

38. Can you use Amazon EC2 Reserved Instances with Amazon VPC?
Answer: Yes. You can reserve an instance in Amazon VPC when you purchase Reserved Instances. When computing your bill, AWS does not distinguish whether your instance runs in Amazon VPC or standard Amazon EC2. AWS automatically optimizes which instances are charged at the lower Reserved Instance rate to ensure you always pay the lowest amount. However, your instance reservation will be specific to Amazon VPC.

39. Do you need to have a VPN connection to use a default VPC?
Answer: No. Default VPCs are attached to the Internet and all instances launched in default subnets in the default VPC automatically receive public IP addresses. You can add a VPN connection to your default VPC if you choose.

40. Can you delete a default VPC?
Answer: Yes. Contact AWS Support if you’ve deleted your default VPC and want to have it reset.

41. Can you delete a default subnet?
Answer: Yes, but once deleted, it’s gone. Your future instance launches will be placed in your remaining default subnet(s).

42. If you delete my side of a peering connection, will the other side still have access to my VPC?
Answer: No. Either side of the peering connection can terminate the peering connection at any time. Terminating a peering connection means traffic won’t flow between the two VPCs.

43. If you peer VPC A to VPC B and I peer VPC B to VPC C, does that mean VPCs A and C peer?
Answer: No. Transitive peering relationships are not supported.

44. You have an existing EC2-Classic account. Can I get a default VPC?
Answer: The simplest way to get a default VPC is to create a new account in a region that is enabled for default VPCs, or use an existing account in a region you’ve never been to before, as long as the Supported Platforms attribute for that account in that region is set to “EC2-VPC”.

45. You really want a default VPC for my existing EC2 account. Is this possible?
Answer: Yes, however, we can only enable an existing account for a default VPC if you have no EC2-Classic resources for that account in that region. Additionally, you must terminate all non-VPC provisioned Elastic Load Balancers, Amazon RDS, Amazon ElastiCache, and Amazon Redshift resources in that region. After your account has been configured for a default VPC, all future resource launches, including instances launched via Auto Scaling, will be placed in your default VPC. To request your existing account be set up with a default VPC, contact AWS Support. We will review your request and your existing AWS services and EC2-Classic presence to determine if you are eligible for a default VPC. AWS Training Free Demo

46. How are IAM accounts impacted by default VPC?
Answer: If your AWS account has a default VPC, any IAM accounts associated with your AWS account use the same default VPC as your AWS account.

47. Can you attach or detach one or more network interfaces to an EC2 instance while it’s running?
Answer: Yes

48. What if your peering connection goes down?
Answer: AWS uses the existing infrastructure of a VPC to create a VPC peering connection; it is neither a gateway nor a VPN connection and does not rely on a separate piece of physical hardware. There is no single point of failure for communication or a bandwidth bottleneck.

49. Can you create a peering connection to a VPC in a different region?
Answer: No. Peering connections are only available between VPCs in the same region.

50. Can you peer my VPC with a VPC belonging to another AWS account?
Answer: Yes, assuming the owner of the other VPC accepts your peering connection request. Amazon Web Services Training

Note: Browse latest Aws Interview Questions and Aws Tutorial Videos. Here you can check Aws Training details and Aws Training Videos for self learning. Contact +91 988 502 2027 for more information.

Leave a Comment

Scroll to Top