Chapter 1 - Compute: Amazon EC2, Auto Scaling, AWS Lambda, AWS Elastic Beanstalk, Amazon Elastic Container Service, AWS Fargate Flashcards
Q1. What are features of EC2?
- Virtual computing environments, instances with Preconfigured templates known as Amazon Machine Images (AMIs)
- Various configurations of CPU, memory, storage, and networking capacity for your instances, known as instance types
- Provides temporary or permanent Storage volumes known as instance store volumes or Amazon EBS volumes
- All of the above
- Virtual computing environments, instances with Preconfigured templates known as Amazon Machine Images (AMIs)
- Various configurations of CPU, memory, storage, and networking capacity for your instances, known as instance types
- Provides temporary or permanent Storage volumes known as instance store volumes or Amazon EBS volumes
- All of the above
Q2. Which of the following is required to launch a new EC2 instance? Choose 2.
- Root or IAM Admin user access keys
- EC2 instance type
- Linux or Windows license
- Amazon Machine Image ( AMI)
- Root or IAM Admin user access keys
- EC2 instance type
- Linux or Windows license
- Amazon Machine Image ( AMI)
Q3. What does an Amazon Machine Image (AMI) Include? Choose 3.
- Instance Type
- One or more EBS snapshots, or, for instance-store-backed AMIs, a template for the root volume of the instance (for example, an operating system, an application server, and applications).
- Launch permissions that control which AWS accounts can use the AMI to launch instances.
- A block device mapping that specifies the volumes to attach to the instance when it’s launched
- Instance Type
- One or more EBS snapshots, or, for instance-store-backed AMIs, a template for the root volume of the instance (for example, an operating system, an application server, and applications).
- Launch permissions that control which AWS accounts can use the AMI to launch instances.
- A block device mapping that specifies the volumes to attach to the instance when it’s launched
What are the two root device option for AMI to launch EC2 instance?
- AMIs backed by S3
- AMIs backed by Amazon EC2 instance store
- AMIs backed by Amazon EBS
- AMIs backed by DynamoDB
- AMIs backed by S3
- AMIs backed by Amazon EC2 instance store
- AMIs backed by Amazon EBS
- AMIs backed by DynamoDB
Which of the following statements are true for data persistence of EC2 root device volume? Choose 2.
- Data on any instance store volumes always persists only during the life of the instance.
- By default, data of the EBS root volume is deleted when the instance terminates but it can be changed to persist.
- Data on any EBS root volumes always persists only during the life of the instance.
- By default, data of the EBS root volume is not deleted when the instance terminates but it can be changed to be deleted.
- Data on any instance store volumes always persists only during the life of the instance.
- By default, data of the EBS root volume is deleted when the instance terminates but it can be changed to persist.
- Data on any EBS root volumes always persists only during the life of the instance.
- By default, data of the EBS root volume is not deleted when the instance terminates but it can be changed to be deleted.
By default, the root device volume for an AMI backed by Amazon EBS is deleted when the instance terminates. How this behavior can be changed?
- Set the DoNotDeleteOnTermination attribute to true
- Set the DoNotDeleteOnTermination attribute to false
- Set the DeleteOnTermination attribute to true
- Set the DeleteOnTermination attribute to false
- Set the DoNotDeleteOnTermination attribute to true
- Set the DoNotDeleteOnTermination attribute to false
- Set the DeleteOnTermination attribute to true
- Set the DeleteOnTermination attribute to false
What are the characteristics based on which you choose the AMI? Choose 2.
- Region, Operating system, Architecture (32-bit or 64-bit)
- Operating system, Architecture (32-bit or 64-bit)
- Launch Permissions
- Launch Permissions, Storage for the Root Device- EBS/Instance
- Region, Operating system, Architecture (32-bit or 64-bit)
- Operating system, Architecture (32-bit or 64-bit)
- Launch Permissions
- Launch Permissions, Storage for the Root Device- EBS/Instance
What are three different type of launch permissions for AMI?
- Public: The owner grants launch permissions to all AWS accounts.
- Explicit: The owner grants launch permissions to specific AWS accounts.
- Implicit: The owner has implicit launch permissions for an AMI.
- Private: The owner grants launch permissions to specific AWS accounts.
- Public: The owner grants launch permissions to all AWS accounts.
- Explicit: The owner grants launch permissions to specific AWS accounts.
- Implicit: The owner has implicit launch permissions for an AMI.
- Private: The owner grants launch permissions to specific AWS accounts.
You can convert your Instance Store-Backed Linux AMI to an Amazon EBS-Backed Linux AMI.
- True
- False
- True
- False
You can convert an instance store-backed Windows AMI to an Amazon EBS-backed Windows AMI.
- True
- False
- True
- False
To launch EC2 instances, you are using AMIs that are backed by Amazon EBS snapshots. Amazon EC2 instances are launched from AMIs using the RunInstances action with encryption parameters supplied through block device mapping, either by means of the AWS Management Console or directly using the Amazon EC2 API or CLI. In the scenario of Launch with no encryption parameters, which of the following three statements are correct?
- An unencrypted snapshot is restored to an unencrypted volume, unless encryption by default is enabled, in which case all the newly created volumes will be encrypted.
- An encrypted snapshot that you own is restored to a volume that is encrypted to the same CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to your AWS account’s default CMK.
- An unencrypted snapshot is restored to an unencrypted volume, unless encryption by default is enabled, in which case all the newly created volumes will be encrypted.
- An encrypted snapshot that you own is restored to a volume that is encrypted to the same CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to your AWS account’s default CMK.
To launch EC2 instances, you are using AMIs that are backed by Amazon EBS snapshots. Amazon EC2 instances are launched from AMIs using the action with encryption parameters supplied through block device mapping, either by means of the AWS Management Console or directly using the Amazon EC2 API or CLI. In the scenario of Launch with Encrypted set, but no KmsKeyId specified, which of the following three statements are correct?
An unencrypted snapshot is restored to an EBS volume that is encrypted by your AWS account’s default CMK.
- An encrypted snapshot that you own is restored to an EBS volume encrypted by the same CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted by your AWS account’s default CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An unencrypted snapshot is restored to an unencrypted volume.
- An encrypted snapshot that you own is restored to an EBS volume encrypted by the same CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted by your AWS account’s default CMK.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An unencrypted snapshot is restored to an unencrypted volume.
To launch EC2 instances, you are using AMIs that are backed by Amazon EBS snapshots. Amazon EC2 instances are launched from AMIs using the action with encryption parameters supplied through block device mapping, either by means of the AWS Management Console or directly using the Amazon EC2 API or CLI. In the scenario of Launch with Encrypted set and also KmsKeyId specified, which of the following two statements are correct?
- An unencrypted snapshot is restored to an unencrypted volume.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An unencrypted snapshot is restored to an EBS volume encrypted by the specified CMK.
- An encrypted snapshot is restored to an EBS volume encrypted not to the original CMK, but instead to the specified CMK.
- An unencrypted snapshot is restored to an unencrypted volume.
- An encrypted snapshot that you do not own (i.e., the AMI is shared with you) is restored to a volume that is encrypted to original AMI owner’s AWS account’s default CMK.
- An unencrypted snapshot is restored to an EBS volume encrypted by the specified CMK.
- An encrypted snapshot is restored to an EBS volume encrypted not to the original CMK, but instead to the specified CMK.
Which of the following Source-Target encryption scenario is not supported when copying AMI?
- Unencrypted-to-unencrypted
- Encrypted-to-encrypted
- Unencrypted-to-encrypted
- Encrypted-to-unencrypted
- Unencrypted-to-unencrypted
- Encrypted-to-encrypted
- Unencrypted-to-encrypted
- Encrypted-to-unencrypted
You have developed a web application and plan to deploy it in your VPC in us-west region. Your VPC has three subnets mapped to three availability zones: us-west-1a, us-west-1b, us-west-1c. How many minimum web server instances should you deploy in each of three AZ so that you have at least six instances running in case one of AZ goes down within minimum cost?
- Six in us-west-1a, six in us-west-1b, six in us-west-1c.
- Three in us-west-1a, three in us-west-1b, three in us-west-1c.
- Two in us-west-1a, two in us-west-1b, four in us-west-1c.
- Four in us-west-1a, two in us-west-1b, four in us-west-1c.
- Six in us-west-1a, six in us-west-1b, six in us-west-1c.
- Three in us-west-1a, three in us-west-1b, three in us-west-1c.
- Two in us-west-1a, two in us-west-1b, four in us-west-1c.
- Four in us-west-1a, two in us-west-1b, four in us-west-1c.
What are benefits of enabling enhanced networking on your Linux instance type? Choose 3.
- lower I/O performance and higher CPU utilization when compared to traditional virtualized network
Interfaces - higher I/O performance and lower CPU utilization when compared to traditional virtualized Network interfaces
- higher bandwidth, higher packet per second (PPS) performance, and consistently Lower inter-instance latencies
- There is no additional charge for using enhanced networking.
- lower I/O performance and higher CPU utilization when compared to traditional virtualized network
Interfaces - higher I/O performance and lower CPU utilization when compared to traditional virtualized Network interfaces
- higher bandwidth, higher packet per second (PPS) performance, and consistently Lower inter-instance latencies
- There is no additional charge for using enhanced networking.
Which of the following is not a type of EC2 placement group?
- Cluster
- Spread
- Partition
- Enhanced
- Cluster
- Spread
- Partition
- Enhanced
What are the two steps you will take regarding your instances if your application requirement is low network latency, high network throughput, majority of the network traffic is between the instances in the group and require highest packet-per-second network Performance? Choose 2.
- Use Cluster placement groups
- Use Spread Placement groups
- Choose an instance type that supports enhanced networking
- Choose an instance type that supports performance networking
- Use Cluster placement groups
- Use Spread Placement groups
- Choose an instance type that supports enhanced networking
- Choose an instance type that supports performance networking
Which placement groups can be used to deploy large distributed and replicated workloads, such as HDFS, HBase, and Cassandra, across distinct racks?
- Use Cluster placement groups
- Use Spread Placement groups
- Use Partition Placement groups
- Use Container Placement groups
- Use Cluster placement groups
- Use Spread Placement groups
- Use Partition Placement groups
- Use Container Placement groups
Which placement groups are recommended for applications that have a small number of critical instances that should be kept separate from each other?
- Use Cluster placement groups
- Use Spread Placement groups
- Use Partition Placement groups
- Use Container Placement groups
- Use Cluster placement groups
- Use Spread Placement groups
- Use Partition Placement groups
- Use Container Placement groups
How can you connect to your Linux EC2 instance from your local computer? Choose 3.
- Local Computer is Linux, use SSH to connect to Linux EC2 instance.
- Local Computer is windows, use SSH to connect to Linux EC2 instance.
- Local Computer is windows, use Putty to connect to Linux EC2 instance.
- Local Computer is Linux, use Putty to connect to Linux EC2 instance.
- Local Computer is Linux, use SSH to connect to Linux EC2 instance.
- Local Computer is windows, use SSH to connect to Linux EC2 instance.
- Local Computer is windows, use Putty to connect to Linux EC2 instance.
- Local Computer is Linux, use Putty to connect to Linux EC2 instance.
Which of the following statements are correct when you stop an EC2 instance? Choose 2.
- You can only stop an instance store-backed instance and not EBS-backed instance.
- You can only stop an EBS-backed instance and not an instance store-backed instance.
- Any Amazon EBS volumes remain attached to the instance, and their data persists. Any data stored in the RAM of the host computer or the instance store volumes of the host computer is gone.
- Any Amazon instance volumes remain attached to the instance, and their data persists. Any data stored in the RAM of the host computer or the instance store volumes of the host computer is persisted.
- You can only stop an instance store-backed instance and not EBS-backed instance.
- You can only stop an EBS-backed instance and not an instance store-backed instance.
- Any Amazon EBS volumes remain attached to the instance, and their data persists. Any data stored in the RAM of the host computer or the instance store volumes of the host computer is gone.
- Any Amazon instance volumes remain attached to the instance, and their data persists. Any data stored in the RAM of the host computer or the instance store volumes of the host computer is persisted.
Which of the following statements are correct when you stop an EC2 instance? Choose 2.
- The instance retains its private IPv4 addresses and any IPv6 addresses when stopped and restarted. AWS releases the public IPv4 address and assign a new one when you restart it.
- The instance retains its associated Elastic IP addresses. You’re charged for any Elastic IP addresses associated with a stopped instance.
- The instance doesn’t retains its private IPv4 addresses and any IPv6 addresses when stopped and restarted. AWS releases the public IPv4 address and assign a new one when you restart it.
- The instance retains its associated Elastic IP addresses. You’re not charged for any Elastic IP addresses associated with a stopped instance.
- The instance retains its private IPv4 addresses and any IPv6 addresses when stopped and restarted. AWS releases the public IPv4 address and assign a new one when you restart it.
- The instance retains its associated Elastic IP addresses. You’re charged for any Elastic IP addresses associated with a stopped instance.
- The instance doesn’t retains its private IPv4 addresses and any IPv6 addresses when stopped and restarted. AWS releases the public IPv4 address and assign a new one when you restart it.
- The instance retains its associated Elastic IP addresses. You’re not charged for any Elastic IP addresses associated with a stopped instance.
Which of the following is true about Elastic Ip Address? Choose 3.
- To use an Elastic IP address, you first allocate one to your account, and then associate it with your instance or a network interface.
- An Elastic IP address is a private IPv4 address in subnet, which is not reachable from the internet.
- With an Elastic IP address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account.
- An Elastic IP address is a public IPv4 address, which is reachable from the internet.
- To use an Elastic IP address, you first allocate one to your account, and then associate it with your instance or a network interface.
- An Elastic IP address is a private IPv4 address in subnet, which is not reachable from the internet.
- With an Elastic IP address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account.
- An Elastic IP address is a public IPv4 address, which is reachable from the internet.