Question : QuickTechie.com setting up their website on AWS and working on various security measures to be performed on the AWS EC instances. Which of the below mentioned security mechanisms will not help the QuickTechie to avoid future data leaks and identify security weaknesses? 1. Perform a Code Check for any memory leaks. 2. Run penetration testing on AWS with prior approval from Amazon. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Perform SQL injection for application testing.
Explanation: AWS security follows the shared security model where the user is as much responsible as Amazon. Since Amazon is a public cloud it is bound to be targeted by hackers. If an organization is planning to host their application on AWS EC2, they should perform the below mentioned security checks as a measure to find any security weakness/data leaks: " Perform penetration testing as performed by attackers to find any vulnerability. The organization must take an approval from AWS before performing penetration testing " Perform hardening testing to find if there are any unnecessary ports open " Perform SQL injection to find any DB security issues The code memory checks are generally useful when the organization wants to improve the application performance. However, because penetration testing frequently is indistinguishable from these activities, we have established a policy for customers to request permission to conduct penetration tests and vulnerability scans.
Question : QuickTechie.com is planning to host a Wordpress blog as well a joomla CMS on a single instance launched with VPC. and also wants to have separate domains for each application and assign them using Route 53. It may have about ten instances each with two applications as mentioned above. While launching the instance, QuickTechie Administrator configured two separate network interfaces (primary + ENI) and wanted to have two elastic IPs for that instance. It was suggested to use a public IP from AWS instead of an elastic IP as the number of elastic IPs is restricted. What action will you recommended ? 1. I agree with the suggestion but will prefer that the organization should use separate subnets with each ENI for different public IPs. 2. I agree with the suggestion and it is recommended to use a public IP from AWS since the organization is going to use DNS with Route 53. 3. Access Mostly Uused Products by 50000+ Subscribers 4. I do not agree as it is required to have only an elastic IP since an instance has more than one ENI and AWS does not assign a public IP to an instance with multiple ENIs.
Correct Answer : Get Lastest Questions and Answer : Explanation:An elastic network interface (ENI) is a virtual network interface that you can attach to an instance in a VPC. An ENI can include the following attributes: a primary private IP address one or more secondary private IP addresses one Elastic IP address per private IP address one public IP address, which can be auto-assigned to the network interface for eth0 when you launch an instance, but only when you create a network interface for eth0 instead of using an existing network interface one or more security groups a MAC address a source/destination check flag a description
You can create a network interface, attach it to an instance, detach it from an instance, and attach it to another instance. The attributes of a network interface follow the network interface as it is attached or detached from an instance and reattached to another instance. When you move a network interface from one instance to another, network traffic is redirected to the new instance. Each instance in a VPC has a default network interface. The default network interface has a primary private IP address in the IP address range of its VPC. You can create and attach additional network interfaces. The maximum number of network interfaces that you can use varies by instance type. For more information, see Private IP Addresses Per ENI Per Instance Type.
Attaching multiple network interfaces to an instance is useful when you want to:
Create a management network. Use network and security appliances in your VPC. Create dual-homed instances with workloads/roles on distinct subnets. Create a low-budget, high-availability solution. A Virtual Private Cloud (VPC) is a virtual network dedicated to the user's AWS account. It enables the user to launch AWS resources into a virtual network that the user has defined. An Elastic Network Interface (ENI) is a virtual network interface that the user can attach to an instance in a VPC. The user can attach upto two ENIs with a single instance. However, AWS cannot assign a public IP when there are two ENIs attached to a single instance. It is recommended to assign an elastic IP in this scenario. If the organization wants more than 5 EIPs they can request AWS to increase the number.
Question : QuickTechie.com is making software for a company in USA. Company agreed to host the application on AWS but in a secure environment. QuickTechie is thinking of hosting the application on the AWS GovCloud region. Which of the below mentioned difference is not correct when the organization is hosting on the AWS GovCloud in comparison with the AWS standard region? 1. GovCloud region authentication is isolated from Amazon.com. 2. Physical and logical administrative access only to U.S. persons. 3. Access Mostly Uused Products by 50000+ Subscribers 4. It is physically isolated and has logical network isolation from all the other regions.
AWS GovCloud (US) is an isolated AWS region designed to allow U.S. government agencies and customers to move sensitive workloads into the cloud by addressing their specific regulatory and compliance requirements. The AWS GovCloud (US) region adheres to U.S. International Traffic in Arms Regulations (ITAR) requirements.
You can run workloads that contain all categories of Controlled Unclassified Information (CUI) data and government oriented publicly available data in the AWS GovCloud (US) region. The AWS GovCloud (US) region supports the management of regulated data by offering the following features:
Restricting physical and logical administrative access to U.S. persons only
Providing FIPS 140-2 validated endpoints
Depending on your requirements, you can also run unclassified workloads in the AWS GovCloud (US) region and use the unique capabilities of this region.
Note
AWS manages physical and logical access controls for the AWS boundary. However, the overall security of your workloads is a shared responsibility, where you are responsible for controlling user access to content in your AWS GovCloud (US) account.
The AWS GovCloud (US) User Guide provides details on setting up your AWS GovCloud (US) account, identifies the differences between the AWS GovCloud (US) region and other AWS regions, and defines usage guidelines for processing ITAR-regulated data within the AWS GovCloud (US) region. AWS GovCloud (US) is an isolated AWS region designed to allow U.S. government agencies and customers to move sensitive workloads into the cloud by addressing their specific regulatory and compliance requirements. The AWS GovCloud (US) Region adheres to the U.S. International Traffic in Arms Regulations (ITAR) requirements. It has added advantages, such as: " Restricting physical and logical administrative access to U.S. persons only " There will be a separate AWS GovCloud (US) credentials, such as access key and secret access key than the standard AWS account " The user signs in with the IAM user name and password " The AWS GovCloud (US) Region authentication is completely isolated from Amazon.com If the organization is planning to host on EC2 in AWS GovCloud then it will be billed to standard AWS account of organization since AWS GovCloud billing is linked with the standard AWS account and is not be billed separately
1. Use the EC2 VM Import Connector for vCenter to import the VM into EC2. 2. Use Import/Export to import the VM as an EBS snapshot and attach to EC2. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use me ec2-bundle-instance API to Import an Image of the VM into EC2
1. File a change request to implement Proxy Protocol support In the application Use an ELB with a TCP Listener and Proxy Protocol enabled to distribute load on two application servers in different AZs. 2. File a change request to Implement Cross-Zone support in the application Use an ELB with a TCP Listener and Cross-Zone Load Balancing enabled, two application servers in different AZs. 3. Access Mostly Uused Products by 50000+ Subscribers Use Route 53 with Latency Based Routing enabled to distribute load on two application servers in different AZs. 4. File a change request to implement Alias Resource support in the application Use Route 53 Alias Resource Record to distribute load on two application servers in different AZs.