Question : When creation of an EBS snapshot is initiated, but not completed, the EBS volume: 1. Can be used while the snapshot is in progress. 2. Cannot be detached or attached to an EC2 instance until the snapshot completes 3. Access Mostly Uused Products by 50000+ Subscribers 4. Cannot be used until the snapshot completes.
Correct Answer : Get Lastest Questions and Answer : When your call to ec2-create-snapshot returns, any future writes to the volume will not be reflected in the snapshot. However, that doesn't guarantee that your snapshot will be consistent, due to write caching inside your instance. In order to guarantee a consistent snapshot, you need to quiesce the file system running on top of your volume, sync the information in the cache to disk and then initiate the snapshot.
Some file systems (such as XFS) provide this hook, others (such as EXT3) do not. For file systems that do not, you can use dmsetup (man dmsetup) to suspend and resume the file system. Once the snapshot has started, it guarantees to provide a point-in-time view of the volume at the time the snapshot was taken.
And, yes, snapshots can take quite some time to complete, depending on how much data has been written to the volume since the last snapshot.
So, you can carry on mutating (writing) the volume as soon as you like after the snapshot has started, and this will not affect the content of the snapshot, even though the snapshot will still be pending for some time.
Question : In VPC for Your Customer Gateway, to establish ephemeral keys to secure all communication between your customer gateway and the virutal private gateway IKE uses
Explanation: IKE(Internet Key Exchange IKE) uses Diffie-Hellman to establish ephemeral keys to secure all communication between customer gateways and VPN gateways.
Question : Suppose an Elastic Network Interfaces (ENI) has been automatically created and attached to an instance using the EC Console. If, later on, the instance is terminated, what will the default termination behavior of the ENI be? 1. Will be Deleted 2. Will be Terminated 3. Access Mostly Uused Products by 50000+ Subscribers 4. Unpredicatble
By default, network interfaces that are automatically created and attached to instances using the AWS Management Console are set to terminate when the instance terminates. However, network interfaces created using the command line interface aren't set to terminate when the instance terminates.
You can change the terminating behavior for a network interface using the AWS Management Console or the command line.
Question : For which of the following use cases are Simple Workflow Service (SWF) and Amazon EC an appropriate solution? Choose answers A. Using as an endpoint to collect thousands of data points per hour from a distributed fleet of sensors B. Managing a multi-step and multi-decision checkout process of an e-commerce website C. Orchestrating the execution of distributed and auditable business processes D. Using as an SNS (Simple Notification Service) endpoint to trigger execution of video transcoding jobs E. Using as a distributed session store for your web application 1. A,B 2. B,C 3. Access Mostly Uused Products by 50000+ Subscribers 4. D,E
Ans : 1 Exp : Q: Can I reassign my RI from one instance family (e.g., c1.xlarge) to another (e.g., m1.large)? No. An RI is associated with a specific instance family for the duration of the RI term; however, you can change from one instance type (e.g., c3.large) to another (e.g., c3.xlarge) in the same family, if it is a Linux/UNIX RI. Hence Option D is out. The only difference between a Reserved instance and a regular instance is the billing, All other features such as AutoScaling and AMIs remain the same. It is important that you factor the billing aspect of Reserved Instance's in to your deployment design as you do not want to have paid Reserved Instances not in use as you have already paid for them upfront. Hence option B is out, and C is correct.
Question : In AWS, which security aspects are the customer's responsibility? Choose answers A. Security Group and ACL (Access Control List) settings B. Decommissioning storage devices C. Patch management on the EC2 instance's operating system D. Life-cycle management of IAM credentials E. Controlling physical access to compute resources F. Encryption of EBS (Elastic Block Storage) volumes
1. Use a DynamoDB table with an attribute defining the priority level. Transformation instances will scan the table for tasks, sorting the results by priority level. 2. Use Route 53 latency based-routing to send high priority tasks to the closest transformation instances. 3. Access Mostly Uused Products by 50000+ Subscribers Transformation instances first poll the high priority queue; if there is no message, they poll the default priority queue. 4. Use a single SQS queue. Each message contains the priority level. Transformation instances poll high-priority messages first.