AMAZON EBS EXAM QUESTIONS

PDF Download

AMAZON EBS EXAM QUESTIONS

Actual Qs and Ans Expert-Verified Explanation

This Exam contains:

-Guarantee passing score -52 Questions and Answers -format set of multiple-choice -Expert-Verified Explanation Question 1: "Q: Does it take longer to snapshot an entire 16 TB volume as compared to an entire 1 TB volume?"

Answer:

"By design, an EBS Snapshot of an entire 16 TB volume should take no longer than the time it takes to snapshot an entire 1 TB volume. However, the actual time taken to create a snapshot depends on several factors including the amount of data that has changed since the last snapshot of the EBS volume." Question 2: "Q: Is there an additional fee to enable Multi-Attach?"

Answer:

"No. Multi-Attach can be enabled on an EBS Provisioned IOPS io1 volume and there will be charges for the storage (GB-Mo) and IOPS (IOPS-Mo) provisioned." Question 3: "Q: Are EBS Standard Volumes still available?"

Answer:

"EBS Standard Volumes have been renamed to EBS Magnetic volumes. Any existing volumes will not have been changed as a result of this and there are no functional differences in the EBS Magnetic offering compared to EBS Standard. The name of this offering was changed to avoid confusion with our General Purpose SSD (gp2) volume type which is our recommended default volume type."

Question 4: "Q: What level of performance latency can I expect to see from my Provisioned IOPS SSD (io2 and io1) volumes?"

Answer:

"When attached to EBS-optimized instances, Provisioned IOPS volumes can achieve single digit millisecond latencies. Your exact performance depends on your application's I/O requirements." Question 5: "Q: Why should I use EBS encryption?"

Answer:

"You can use Amazon EBS encryption to meet security and encryption compliance requirements for data at rest encryption in the cloud. Pairing encryption with existing IAM access control policies improves your company's defense-in-depth strategy." Question 6: "Q: What is the AWS Key Management Service (KMS)?"

Answer:

"AWS KMS is a managed service that makes it easy for you to create and control the encryption keys used to encrypt your data. AWS Key Management Service is integrated with other AWS services including Amazon EBS, Amazon S3, and Amazon Redshift, to make it simple to encrypt your data with encryption keys that you manage. AWS Key Management Service is also integrated with AWS CloudTrail to provide you with logs of all key usage to help meet your regulatory and compliance needs.To learn more about KMS, visit the AWS Key Management Service product page." Question 7: "Q: What kind of performance can I expect from Amazon EBS volumes?"

Answer:

"Amazon EBS provides five volume types: Provisioned IOPS SSD (io2 and io1), General Purpose SSD (gp2), Throughput Optimized HDD (st1) and Cold HDD (sc1). These volume types differ in performance characteristics and price, allowing you to tailor your storage performance and cost to the needs of your applications. The average latency between EC2 instances and EBS is single digit milliseconds. For more performance information see the EBS product details page.For more information about Amazon EBS performance guidelines, see Increasing EBS Performance." Question 8: "Q: Do your prices include taxes?"

Answer:

"Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS services is subject to Japanese Consumption Tax. Learn more."

Question 9: "Q: Can I boot an EC2 instance using a Multi-Attach enabled volume?"

Answer:

"No." Question 10: "Q: Can I create additional encrypted data volumes at the time of instance launch that are not part of the AMI?"

Answer:

"Yes, you can create encrypted data volume with either default or custom CMK encryption at the time of instances launch. You can specify the volume details and encryption through BlockDeviceMapping object in RunInstances API call or through Launch Wizard in EC2 Console." Question 11: "Q: What happens to my data when an Amazon EC2 instance terminates?"

Answer:

"Unlike the data stored on a local instance store (which persists only as long as that instance is alive), data stored on an Amazon EBS volume can persist independently of the life of the instance. Therefore, we recommend that you use the local instance store only for temporary data. For data requiring a higher level of durability, we recommend using Amazon EBS volumes or backing up the data to Amazon S3. If you are using an Amazon EBS volume as a root partition, set the Delete on termination flag to "No" if you want your Amazon EBS volume to persist outside the life of the instance." Question 12: "Q: Can my application use Multi-Attach?"

Answer:

"If your application does not require storage layer coordination of write operations, such as a read-only application or it enforces application level IO fencing, then your application can use Multi-Attach." Question 13: "Q: What happens if all of my attached instances do not have the 'deleteOnTermination' flag set?"

Answer:

"The volume's deleteOnTermination behavior is determined by the configuration of the last attached instance that is terminated. To ensure predictable delete on termination behavior, enable or disable 'deleteOnTermination' for all of the instances to which the volume is attached.If you want the volume to be deleted when the attached instances are terminated, enable 'deleteOnTermination' for all of instances to which the volume is attached. If you want to retain the volume after the attached instances have been terminated, disable 'deleteOnTermination' for all attached instances. For more information, see Multi-Attach technical documentation."

Question 14: "Q: Can I ensure that all new volumes created are always encrypted?"

Answer:

"Yes, you can enable EBS encryption by default with a single setting per region. This ensures that all new volumes are always encrypted. Refer to technical documentation for more details." Question 15: "Q: How can I discover Amazon EBS snapshots that are shared with me?"

Answer:

"You can find snapshots that are shared with you by selecting Private Snapshots from the list in the Snapshots section of the AWS Management Console. This section lists both snapshots that you own and snapshots that are shared with you." Question 16: "Q: Does the I/O size of my application reads and writes affect the rate of throughput I get from my HDD-backed volumes?"

Answer:

"Yes. The throughput rate you get depends on the I/O size of your application reads and writes.HDD-backed volumes process reads and writes in I/O sizes of 1MB. Sequential I/Os are merged and processed as 1 MB units while each non-sequential I/O is processed as 1MB even if the actual I/O size is smaller. Thus, while a transactional workload with small, random IOs, such as a database, won't perform well on HDD-backed volumes, sequential I/Os and large I/O sizes will achieve the advertised performance of st1 and sc1 for a longer period of time." Question 17: "Q: How can I use EBS direct APIs for Snapshots?"

Answer:

"This feature can be used via the following APIs that can be called using AWS CLI or via AWS SDK.List Snapshot Blocks: The ListSnapshotBlocks API operation returns the block indexes and block tokens for blocks in the specified snapshot.List Changed Blocks: The ListChangedBlocks API operation returns the block indexes and block tokens for blocks that are different between two specified snapshots of the same volume/snapshot lineage.Get Snapshot Blocks: The GetSnapshotBlock API operation returns the data in a block for the specified snapshot ID, block index, and block token.Start Snapshot: The StartSnapshot operation starts a snapshot, either as an incremental snapshot of an existing one or as a new snapshot. The started snapshot remains in a pending state until it is completed using the CompleteSnapshot action.Put Snapshot Block: The PutSnapshot operation adds data in the form of individual blocks to a started snapshot that is in a pending state. You must specify a Base64-encoded SHA256 checksum for the block of data transmitted. The service validates the checksum after the transmission is completed. The request fails if the checksum computed by service doesn't match what you speci?ed.Complete Snapshot: The CompleteSnapshot operation completes a started snapshot that is in a pending state. The snapshot is then changed to a completed state.For more information, please refer to technical documentation."