AWS 2

“adjustment=3” (type is ExactCapacity)

“adjustment=-50” (type is PercentChangeInCapacity)

“adjustment=-1” (type is ChangeInCapacity)

“adjustment=-8” (type is ExactCapacity)

75

74

69

76

47

48

50

52

100

40

10

20

3

2

0

1

EC2-> Auto Scaling-> Instance Listing

EC2->Describe Instances Page

The launch from the instance is not supported in the AWS console

EC2-> Launch Config Creation Page

Vault Inventory Retrieval Job Complete.

Glacier does not support the AWS console.

Archival Upload Complete.

Vault Retrieval Job Complete.

SOAP API

CLI

REST API

AWS console

Use the AWS Tools for Windows PowerShell with an AMI that the user selects.

Launch an instance using the Amazon EBS snapshot.

Launch using the ELB console with the selected AMI.

Launch an instance using the EC2 CLI.

Select Community AMIs.

Select from the AWS marketplace.

Select from the Trusted AWS partners.

Select My AMIs.

The user has to use Cloudwatch to configure instance termination while the instance is being stopped.

Update the instance termination protection attributes so it always terminates when it is stopped.

Change the shutdown behaviour of the instance from stop to terminate.

It is not possible to terminate the instance when it is stopped.

The user can communicate using the private IP across regions.

The private IP address and public IP address for an instance are directly mapped to each other using NAT.

The private IP addresses are not reachable from the internet.

The private IP address for the instance is assigned using DHCP.

The user cannot create a custom firewall in EC2-Classic.

The custom firewall should map the internal DNS with the elastic IP using NAT.

Allow inbound traffic on port 53 from the Amazon DNS server.

The user should implement NAT for DNS and IP mapping.

The volume will survive instance termination.

The volume will be terminated only if it is mounted as a root device.

The volume will be terminated along with the instance.

The volume will be terminated only if the user has marked the flag of deleteontermination false.

Attach an EBS volume of 1 GB.

Launch with RHEL OS.

Enable termination protection.

Attach an ephemeral storage.

Provided it is an EBS backed AMI.

No.

Provided it is an instance store backed AMI.

Yes.

It is not possible to have ephermal storage with free usage.

Launch an instance with an instance store backed AMI.

Create an AMI which has ephermal storage attached on instance launch.

While launching an instance the user can attach ephermal storage.

It is not possible to have this instance under the free usage tier.

Launch a micro instance, but in the EBS configuration modify the size of EBS to 30 GB.

Launch a micro instance.

Launch a micro instance, but do not store the data of more than 30 GB on the EBS storage.

Key: “aws:name” Value: “instance@aws”

Key: “Name :aws” Value: “instance@aws”

Key : “name@aws” Value:”aws:instance”

Key : “aws” Value:”aws”

By default all inbound traffic is disabled and all outbound traffic is enabled.

By default all inbound and outbound traffic is enabled.

By default all inbound and outbound traffic is disabled.

By default all inbound traffic is enabled and all outbound traffic is disabled.

Yes.

No.

No, but it is possible that the current version stays in RRS and the older version in S3.

Yes, only if the life cycle rule is set.

The user can store a php file in AWS S3.

The user can host a static website on AWS S3.

The user can host a dynamic website with Cloudfront.

The user can create a bucket with the same name as the user domain on S3.

Nothing. The website hosting feature just enables the user to point to the specific index file.

It helps the user to save some costs as it will not consider the I/O charges if website hosting is enabled.

The user can directly access the website using the region specific endpoint.

Nothing. the user can always access index.html without the hosting feature.

Create two buckets with the name www.cloudacademy.com and cloudacademy.com and host a static website on both the buckets.

Create two buckets with the name www.cloudacademy.com and cloudacademy.com and route requests from both the buckets to each other using S3 website hosting.

It is not possible to have two buckets serving the same website.

Create two buckets with the name www.cloudacademy.com and cloudacademy.comand route requests of one bucket to another using S3 website hosting.

Archival.

Checksum.

Encryption.

Intrinsic replication.

It will return “colour=white”.

It will return “colour=red”.

It will return an error saying that the object was not found.

It may return either “colour=red” or “colour=white” i.e. any of the value.

It will return error 404 object not found.

It may return an error or return the value “colour=red”.

It will return an invalid key.

It will return “colour=red”.

It will allow the other AWS owner to create since the AWS account ID is different.

It will throw an error saying naming criteria not met for EU region.

It will allow the other AWS owner to create since the region is different.

It will throw an error saying the requested bucket name is not available

Verifies if the IAM policy is available for the root account to provide permission to the other IAM users.

Verifies that the bucket has the required policy defined for access the IAM user.

Verifies if the parent of the IAM user has granted sufficient permission.

Reject the request since the IAM user does not belong to the root account.

Glacier is not supported the in US-West-1 region.

Glacier will throw an error for same vault name.

Glacier will allow the user to create a new vault in the US-West-1 region.

Glacier will throw an error for wrong naming convention in the US-West-1 region.

It will list the archive in the job result.

It will not list the archive in the job result.

It may or may not list the archive in the result.

It is not possible to get the list of the archive using the vault inventory Job.

AWS will allow to create the IAM group with the name cloud as both the user and the group have separate ARNs.

AWS will not allow to create the IAM group with the name cloud as there will be a conflict between the ARNs.

AWS will allow to create the IAM group with the name cloud provided the user has given the path attribute name.

If the user is creating from CLI, it will allow since the user can specify the path attribute to a separate ARN.

The owner needs a setup for each user’s smartphone.

Create a policy which will allow each user to setup their smartphone for MFA.

Enable MFA for each user and AWS will ask the user to attach their smartphone on first login.

It is not possible to have MFA with a smartphone.

It is linked with the user AWS account.

It is mapped to the primary network interface.

It can be used to access the instance from the internet.

The public DNS cannot be changed by the user.

AWS will not take any version of the policy.

AWS will take the default "Version":"2012-10-17".

AWS will throw an error.

AWS will take the default "Version":"2008-10-17".

Supported Data Types

NotEffect

PrincipalResource

VersionManagement

Allow the EC2 security group within the RDS security group to allow access from EC2.

IAM role with RDS access and attach it to EC2.

Access between RDS and EC2 is always secure.

Create an IAM user with RDS access and use its own credentials.

No, provided the snapshot storage is less than 40 GB.

No. Backup storage is always free.

No, provided the total snapshot size is less than 20 GB.

Yes.

5 GB

50 GB

1 TB

100 GB

The user should select the option as ‘No’ in the Management Options screen against the Maintenance window.

The user should provide the same time for start and end so that it will not perform maintenance.

The user should skip the step to configure the maintenance window.

It is not possible to skip the mandatory maintenance window.

12:30 AM

01:00 AM

01:01 AM

The default duration for maintenance is 30 minutes and the user cannot specify 1 hour.

Use dedicated instances.

Use enhanced EC2 instances.

It is not possible to have hardware separation for EC2.

Use single tenant option.

The instance is not configured for security.

The user might not have attached the key-pair with the EC2 instance.

The instance default user name is wrong.

Port 22 is not open for the instance security group.

Create a new AMI template and launch it. The new instance will have all the required config options.

Use the option “Launch from template” from the AWS console.

Create the instance template and launch it.

Use the option “Launch More like this” from the AWS console.

The instance may not be able to flush the file system and may result in a corrupted file system of the volume.

AWS deletes the volume automatically since it will be in a corrupted state.

The volume will be available but cannot be attached to any instance in the future.

AWS terminates the instance automatically since the file system is corrupted.

AWS will create a snapshot of only blocks which are written on the volume.

AWS will copy all the blocks from EBS and create a snapshot.

The I/O on the volume will be frozen while a snapshot is being taken.

AWS will create a snapshot of the modified content in the same AZ of the region.

The snapshot will fail since the volume is not mounted.

The snapshot will succeed but it will have no data.

The snapshot will succeed with all the modified data of the EBS volume.

The new snapshot will only have the original volume content.

The user should access all the blocks of data before the exam in advance.

The user should select the instance with a higher size to avoid an initial low I/O.

The EBS will automatically scale up the I/O when the load increases.

Use the ELB to distribute the load on EBS.

20

10

30

5

4000

1000

2000

3000