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?
Answer:

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.
Trustworthy
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.
 Safety
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.