Question : You run a nightly Elastic Map Reduce (EMR) job that processes a single Tb file which is stored on S. The EMR job runs on on-demand core nodes and three on-demand task nodes. What can help you achieve a reduction in the EMR job completion time? 1. Use three Spot Instances for the task nodes rather than three On-Demand instances. 2. Change the input split size in the MapReduce job configuration and adjust the number of simultaneous mapper tasks. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Launch the core nodes and task nodes within an Amazon Virtual Cloud. 5. Enable termination protection for the job flow.
Question : You have been asked to leverage Amazon VPC EC and SQS to implement an application that submits and receives millions of messages per second to a message queue. You want to ensure your application has sufficient bandwidth between your EC2 instances and SQS Which option will provide (The most scalable solution for communicating between the application and SQS)? 1. Ensure the application instances are properly configured with an Elastic Load Balancer 2. Ensure the application instances are launched in private subnets with the EBS-optimized option enabled 3. Access Mostly Uused Products by 50000+ Subscribers 4. Launch application instances in private subnets with an Auto Scaling group and Auto Scaling triggers configured to watch the SQS queue size
Correct Answer : Get Lastest Questions and Answer : Exp: For example, suppose that you have a web app that receives orders from customers. The app runs on EC instances in an Auto Scaling group that is configured to handle a typical amount of orders. The app places the orders in an Amazon SQS queue until they are picked up for processing, processes the orders, and then sends the processed orders back to the customer This architecture works well if your order levels remain the same at all times. What happens if your order levels change? You would need to launch additional EC2 instances when the orders increase and terminate the extra EC2 instances when the orders decrease. If your orders increase and decrease on a predictable schedule, you can specify the time and date to perform scaling activities. Otherwise, you can scale based on criteria, such as the number of messages in your Amazon SQS queue. Queues provide a convenient mechanism to determine the load on an application. You can use the length of the queue (number of messages available for retrieval from the queue) to determine the load. Because each message in the queue represents a request from a user, measuring the length of the queue is a fair approximation of the load on the application. CloudWatch integrates with Amazon SQS to collect, view, and analyze metrics from Amazon SQS queues. You can use the metrics sent by Amazon SQS to determine the length of the Amazon SQS queue at any point in time. For a list of all the metrics that Amazon SQS sends to CloudWatch,
Question : You have CloudFormation templates. Each template is for a different application architecture. These architectures vary between your blog apps and your gaming apps. What determines the cost of using the CloudFormation templates?
1. The length of time it takes to build the architecture with CloudFormation. 2. CloudFormation does not have a cost but you are charged for the underlying resources it builds. 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above
Explanation: There is no additional charge for AWS CloudFormation. You pay for AWS resources (such as Amazon EC2 instances, Elastic Load Balancing load balancers, etc.) created using AWS CloudFormation in the same manner as if you created them manually.
In order to avoid having you sign up individually for all services supported by AWS CloudFormation, we automatically sign you up for all these services when you sign up for AWS CloudFormation. This makes it easy for you to use the AWS CloudFormation sample templates without having to manually check that you are enabled for the respective AWS services. As with all AWS services, you only pay for what you use, as you use it; there are no minimum fees and no required upfront commitments.
1. When an EIP is allocated. 2. When it is allocated and associated with a running instance. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Costs are incurred regardless of whether the EIP is associated with a running instance.
Ans : 4 Exp : You can have one Elastic IP (EIP) address associated with a running instance at no charge. If you associate additional EIPs with that instance, you will be charged for each additional EIP associated with that instance per hour on a pro rata basis. Additional EIPs are only available in Amazon VPC.
To ensure efficient use of Elastic IP addresses, we impose a small hourly charge when these IP addresses are not associated with a running instance or when they are associated with a stopped instance or unattached network interface. $0.00 for one Elastic IP address associated with a running instance $0.005 per additional Elastic IP address associated with a running instance per hour on a pro rata basis $0.005 per Elastic IP address not associated with a running instance per hour on a pro rata basis $0.00 per Elastic IP address remap for the first 100 remaps per month $0.10 per Elastic IP address remap for additional remaps over 100 per month
Q: Why am I charged when my Elastic IP address is not associated with a running instance? In order to help ensure our customers are efficiently using the Elastic IP addresses, we impose a small hourly charge for each address when it is not associated to a running instance.
Question : When you put objects in Amazon S, what is the indication that an object was successfully stored? 1. A HTTP 200 result code and MD5 checksum, taken together, indicate that the operation was successful. 2. Amazon S3 is engineered for 99.999999999% durability. Therefore there is no need to confirm that data was inserted. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Each S3 account has a special bucket named _s3_logs. Success codes are written to this bucket with a timestamp and checksum.
1. Amazon EBS-backed instances can be stopped and restarted. 2. Instance-store backed instances can be stopped and restarted. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Virtual Private Cloud requires EBS backed instances. Ans : 1 Exp : "Instance Store" Instances An "instance store" instance is an EC2 instance whose root device resides on the virtual machine's hard drive. When the instance is created, the base AMI is copied to the virtual machine's hard drive and launched. The instance can run for as long as you want, but it cannot be stopped. Since the instance's root device is the actual hard drive, it is "stuck" on the hardware, and the only thing you can do is terminate the instance. If you do this, the instance is deleted, never to be recovered. You also run the risk that if the virtual machine's hardware fails, then you will also lose anything on the hard drive. If you launch an "instance store" instance, be prepared to leave it running until you're completely done with it. Note that you will be charged from the moment the instance is started, until the time it is terminated. "EBS-Backed" Instances An "EBS-backed" instance is an EC2 instance which uses an EBS volume as it's root device. EBS volumes are redundant, "virtual" drives, which are not tied to any particular hardware, however they are restricted to a particular EC2 availability zone. This means that an EBS volume can move from one piece of hardware to another within the same availability zone. You can think of EBS volumes as a kind of Network Attached Storage. If the virtual machine's hardware fails, the EBS volume can simply be moved to another virtual machine and re-launched. In theory, you won't lose any data. Another benefit, is that EBS volumes can easily be backed up and duplicated. So you can take easy backup snapshots of your volumes, create new volumes and launch new EC2 instances based on those duplicate volumes. Probably the biggest advantage "EBS-backed" instances have over "instance store" instances is that they can be stopped. When you do this, the virtual machine is shutdown and the EBS volume is stored for later retrieval. The hardware is then available for someone else to use. In addition, during this time, you are not charged the EC2 instance running charge. But you are charged for the EBS storage. When you want the instance to run again, you just start it up again. A new virtual machine is reserved, your EBS volume is attached, and your instance is booted. But what about the virtual machine's hard drives? Yes, it is possible to use those hard drives, even when your EC2 instance is "EBS-backed". By default, they are not available. If you use the command line programs to launch your instance, you can use the "-b" option on the ec2-run-instances command to attach the "instance store" drives to your EC2 instance. Having these drives available can be beneficial if you want to store temporary data. Read and write access should be faster than reading from and writing to an EBS volume because you're not sending data over the network. In addition, you won't be charged for data transfer or data storage. But this only works if the data can be lost at any time. " EBS backed instances can be stopped when you're not using them and resumed when you need them again (like pausing a Virtual PC), at least with my usage patterns saving much more money than I spend on a few dozen GB of EBS storage.
Question : Per the AWS Acceptable Use Policy, penetration testing of EC instances: 1. May be performed by AWS, and will be performed by AWS upon customer request. 2. May be performed by AWS, and is periodically performed by AWS. 3. Access Mostly Uused Products by 50000+ Subscribers 4. May be performed by the customer on their own instances with prior authorization from AWS. 5. May be performed by the customer on their own instances, only if performed from EC2 instances
5. 1. Suspend disk I/O, 2. Start EBS snapshot of volumes, 3. Wait for snapshots to complete, 4. Resume disk I/O
Ans : 1 Exp : Q: Do volumes need to be un-mounted in order to take a snapshot? Does the snapshot need to complete before the volume can be used again? No, snapshots can be done in real time while the volume is attached and in use. However, snapshots only capture data that has been written to your Amazon EBS volume, which might exclude any data that has been locally cached by your application or OS. In order to ensure consistent snapshots on volumes attached to an instance, we recommend cleanly detaching the volume, issuing the snapshot command, and then reattaching the volume. For Amazon EBS volumes that serve as root devices, we recommend shutting down the machine to take a clean snapshot.
Question : How can you secure data at rest on an EBS volume? 1. Attach the volume to an instance using EC2's SSL interface. 2. Write the data randomly instead of sequentially. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Create an IAM policy that restricts read and write access to the volume. 5. Use an encrypted file system on top of the EBS volume.
1. Deploy 6 EC2 instances in one availability zone and use Amazon Elastic Load Balancer. 2. Deploy 3 EC2 instances in one region and 3 in another region and use Amazon Elastic Load Balancer. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Deploy 2 EC2 instances in three regions and use Amazon Elastic Load Balancer.