Question : An organization is planning to setup Wordpress on the AWS VPC. The organization needs automated HA and DR along with an high security standard. Which of the below mentioned configurations satisfies the organization's requirement? 1. Create two separate VPCs and run RDS. RDS will have the multi AZ feature enabled which spans across these two VPCs using VPC peering. Setup the App server with one of the public subnets of any VPC. 2. Create a VPC with one private and one public subnet in separate AZs. Setup the EC2 instance with a DB in the private subnet and the web application in a public subnet. 3. Access Mostly Uused Products by 50000+ Subscribers in the public subnet. 4. Create two separate VPCs in different zones. Setup two EC2 instances by installing a DB in the two different VPCs and enable the failover mechanism. Setup the App server with one of the public subnets of any VPC.
Explanation: A Virtual Private Cloud (VPC) is a virtual network dedicated to the user's AWS account. It enables the user to launch AWS resources, such as RDS into a virtual network that the user has defined. Subnets are segments of a VPC's IP address range that the user can designate to a group of VPC resources based on security and operational needs. To setup the HA and DR system it is recommended to use RDS with AWS as it offers a point in time snapshot and multi AZ feature. The user should setup RDS with the VPC subnet group. A DB subnet group is a collection of subnets (generally private) that the user can create in a VPC and which the user assigns to the RDS DB instances. A DB subnet group allows the user to specify a particular VPC when creating the DB instances. Each DB subnet group should have subnets in at least two Availability Zones in a given region.
Question : An organization is planning to host an application on the AWS VPC. The organization wants dedicated instances. However, an AWS consultant advised the organization not to use dedicated instances with VPC as the design has a few limitations. Which of the below mentioned statements is not a limitation of dedicated instances with VPC? 1. All instances launched with this VPC will always be dedicated instances and the user cannot use a default tenancy model for them. 2. The EBS volume will not be on the same tenant hardware as the EC2 instance though the user has configured dedicated tenancy. 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user cannot use Reserved Instances with a dedicated tenancy model.
Correct Answer : Get Lastest Questions and Answer : Explanation: The Amazon Virtual Private Cloud (Amazon VPC) allows the user to define a virtual networking environment in a private, isolated section of the Amazon Web Services (AWS) cloud. The user has complete control over the virtual networking environment. Dedicated instances are Amazon EC2 instances that run in a Virtual Private Cloud (VPC) on hardware that is dedicated to a single customer. The client's dedicated instances are physically isolated at the host hardware level from instances that are not dedicated instances as well as from instances that belong to other AWS accounts. All instances launched with the dedicated tenancy model of VPC will always be dedicated instances. Dedicated tenancy has a limitation that it may not support a few services, such as RDS. Even the EBS will not be on dedicated hardware. However the user can save some cost as well as reserve some capacity by using a Reserved Instance model with dedicated tenancy.
Question : An application is running on AWS EC. The application has no usage (almost zero load) between PM to AM and AM to PM. The application experiences higher CPU utilization between 8 AM to 10 AM and 7 PM to 9 PM. Which of the below mentioned EC2 configurations will be more helpful and cost effective in this scenario? 1. Use EC2 with the spot instance model to scale up and down using Auto Scaling. 2. Use EC2 with Auto Scaling which will scale up when the load increases. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use EC2 with ELB which distributes the higher load effectively.
Explanation: Amazon EC2 allows the user to choose between Fixed Performance Instances (e.g. M3, C3, and R3) and Burstable Performance Instances (e.g. T2). Burstable Performance Instances provide a baseline level of the CPU performance with the ability to burst above the baseline. T2 instances are for workloads that do not use the full CPU often or consistently, but occasionally need to burst. In this scenario instances require higher CPU utilization only during certain periods. T2 instances' baseline performance and ability to burst are governed by CPU Credits. Each T2 instance continuously receives CPU Credits, the rate of which depends on the instance size. T2 instances accrue CPU Credits when they are idle, and use CPU credits when they are active. The current scenario presents the case for CPU credit as otherwise most of the times the instances are idle. Thus, this makes a strong case for T2 instances. Using with Auto Scaling may be little costlier as it may. Amazon EC2 allows you to choose between Fixed Performance Instances (e.g. M3, C3, and R3) and Burstable Performance Instances (e.g. T2). Burstable Performance Instances provide a baseline level of CPU performance with the ability to burst above the baseline. T2 instances are for workloads that don't use the full CPU often or consistently, but occasionally need to burst.
T2 instances' baseline performance and ability to burst are governed by CPU Credits. Each T2 instance receives CPU Credits continuously, the rate of which depends on the instance size. T2 instances accrue CPU Credits when they are idle, and use CPU credits when they are active. A CPU Credit provides the performance of a full CPU core for one minute.
For example, a t2.small instance receives credits continuously at a rate of 12 CPU Credits per hour. This capability provides baseline performance equivalent to 20% of a CPU core. If at any moment the instance does not need the credits it receives, it stores them in its CPU Credit balance for up to 24 hours. If and when your t2.small needs to burst to more than 20% of a core, it draws from its CPU Credit balance to handle this surge seamlessly. Over time, if you find your workload needs more CPU Credits than you have, or your instance does not maintain a positive CPU Credit balance, we recommend either a larger T2 size, such as the t2.medium, or a Fixed Performance Instance type.
Many applications such as web servers, developer environments and small databases don't need consistently high levels of CPU, but benefit significantly from having full access to very fast CPUs when they need them. T2 instances are engineered specifically for these use cases. If you need consistently high CPU performance for applications such as video encoding, high volume websites or HPC applications, we recommend you use Fixed Performance Instances. T2 instances are designed to perform as if they have dedicated high speed Intel cores available when your application really needs CPU performance, while protecting you from the variable performance or other common side effects you might typically see from over-subscription in other environments.
1. Configure an instance with monitoring software and the elastic network interface (ENI) set to promiscuous mode packet sniffing to see an traffic across the VPC. 2. Create a second VPC and route all traffic from the primary application VPC through the second VPC where the scalable virtualized IDS/IPS platform resides. 3. Access Mostly Uused Products by 50000+ Subscribers traffic through the platform to a scalable virtualized IDS/IPS. 4. Configure each host with an agent that collects all network traffic and sends that traffic to the IDS/IPS platform for inspection.