AWS Certified SysOps Administrator - Associate Questions and Answers (Dumps and Practice Questions)
Question : QuickTechie Admin launched an RDS postgreSQL DB with AWS. The user did not specify the maintenance window during creation. The user has
configured RDS to update the DB instance type from micro to large. If the user wants to have it during the maintenance window, what will AWS
do?
1. AWS will not allow to update the DB until the maintenance window is configured
2. AWS will select the default maintenance window if the user has not provided it
3. AWS will ask the user to specify the maintenance window during the update
4. It is not possible to change the DB size from micro to large with RDS
Correct Answer : 2
Explanation: The Amazon RDS maintenance window is your opportunity to control when DB Instance modifications (such as scaling DB Instance class) and software patching occur, in the event
they are requested or required. If a maintenance event is scheduled for a given week, it will be initiated and completed at some point during the maintenance window you identify.
Maintenance windows are 30 minutes in duration.
The only maintenance events that require Amazon RDS to take your DB Instance offline are scale compute operations (which generally take only a few minutes from start-to-finish) or
required software patching. Required patching is automatically scheduled only for patches that are security and durability related. Such patching occurs infrequently (typically once
every few months) and should seldom require more than a fraction of your maintenance window. If you do not specify a preferred weekly maintenance window when creating your DB
Instance, a 30 minute default value is assigned. If you wish to modify when maintenance is performed on your behalf, you can do so by modifying your DB Instance in the AWS Management
Console or by using the ModifyDBInstance API. Each of your DB Instances can have different preferred maintenance windows, if you so choose.
Running your DB Instance as a Multi-AZ deployment can further reduce the impact of a maintenance event, because Amazon RDS will perform the activity like so:
Perform the maintenance on the standby instance
Promote the standby to be the new primary
Perform maintenance on the old primary, which then becomes the new standby
AWS RDS has a compulsory maintenance window which by default is 30 minutes. If the user does not specify the maintenance window during the creation of RDS then AWS will select a
30-minute maintenance window randomly from an 8-hour block of time per region. In this case, Amazon RDS assigns a 30-minute maintenance window on a randomly selected day of the week.
Most maintenance occurs during a user-definable maintenance window. You can think of the maintenance window as an opportunity to control when DB instance modifications (such as
implementing pending changes to storage or CPU class for the DB instance) and software patching occur, in the event either are requested or required. If a maintenance event is
scheduled for a given week, it will be initiated and completed at some point during the 30 minute maintenance window you identify.
Amazon RDS allows you to choose when to upgrade your DB software and when you upgrade the underlying operating system. Upgrades to the operating system are most often for security
issues and should be done as soon as possible. This gives you the ability to see ahead of time when a given required maintenance update will be applied to their instances, as well as
the ability to opt in to the maintenance ahead of the scheduled start time.
The 30-minute maintenance window is selected at random from an 8-hour block of time per region. If you don't specify a preferred maintenance window when you create the DB instance,
Amazon RDS assigns a 30-minute maintenance window on a randomly selected day of the week.
Question : Acmeshell Inc's Sysadmin has created a subnet in VPC and launched an EC instance within it.Admin has not selected the option to assign
the IP address while launching the instance. The user has 3 elastic IPs and is trying to assign one of the Elastic IPs to the VPC
instance from the console. The console does not show any instance in the IP assignment screen. What is a possible reason that
the instance is unavailable in the assigned IP console?
1. The IP address may be attached to one of the instances
2. The IP address belongs to a different zone than the subnet zone
3. The user has not created an internet gateway
4. The IP addresses belong to EC2 Classic; so they cannot be assigned to VPC
Correct Answer : 4
Explanation: Elastic IP Addresses in EC2-Classic : By default, we assign each instance in EC2-Classic two IP addresses at launch: a private IP address and a public IP address that is mapped
to the private IP address through network address translation (NAT). The public IP address is allocated from the EC2-Classic public IP address pool, and is associated with your
instance, not with your AWS account. You cannot reuse a public IP address after it's been disassociated from your instance.
If you use dynamic DNS to map an existing DNS name to a new instance's public IP address, it might take up to 24 hours for the IP address to propagate through the Internet. As a
result, new instances might not receive traffic while terminated instances continue to receive requests. To solve this problem, use an EIP.
When you associate an EIP with an instance, the instance's current public IP address is released to the EC2-Classic public IP address pool. If you disassociate an EIP from the
instance, the instance is automatically assigned a new public IP address within a few minutes. In addition, stopping the instance also disassociates the EIP from it.
To ensure efficient use of EIPs, we impose a small hourly charge if an EIP is not associated with a running instance. For more information, see Amazon EC2 Pricing.
Elastic IP Addresses in a VPC
We assign each instance in a default VPC two IP addresses at launch: a private IP address and a public IP address that is mapped to the private IP address through network address
translation (NAT). The public IP address is allocated from the EC2-VPC public IP address pool, and is associated with your instance, not with your AWS account. You cannot reuse a
public IP address after it's been disassociated from your instance.
We assign each instance in a nondefault VPC only a private IP address, unless you specifically request a public IP address during launch, or you modify the subnet's public IP address
attribute. To ensure that an instance in a nondefault VPC that has not been assigned a public IP address can communicate with the Internet, you must allocate an Elastic IP address
for use with a VPC, and then associate that EIP with the elastic network interface (ENI) attached to the instance.
When you associate an EIP with an instance in a default VPC, or an instance in which you assigned a public IP to the eth0 network interface during launch, its current public IP
address is released to the EC2-VPC public IP address pool. If you disassociate an EIP from the instance, the instance is automatically assigned a new public IP address within a few
minutes. However, if you have attached a second network interface to the instance, the instance is not automatically assigned a new public IP address; you'll have to associate an EIP
with it manually. The EIP remains associated with the instance when you stop it.
To ensure efficient use of EIPs, we impose a small hourly charge if an EIP is not associated with a running instance, or if it is associated with a stopped instance or an unattached
network interface. While your instance is running, you are not charged for one EIP associated with the instance, but you are charged for any additional EIPs associated with the
instance. For more information, see Amazon EC2 Pricing. A Virtual Private Cloud (VPC. is a virtual network dedicated to the user's AWS account. A user can create a subnet with VPC
and launch instances inside that subnet. When the user is launching an instance he needs to select an option which attaches a public IP to the instance. If the user has not selected
the option to attach the public IP then it will only have a private IP when launched. If the user wants to connect to an instance from the internet he should create an elastic IP
with VPC. If the elastic IP is a part of EC2 Classic it cannot be assigned to a VPC instance.
Question : John is an Administrator at Acmeshell Inc and has launched multiple EC instances for the purpose of development and testing in the same region.
Now he wants to find the separate cost for the production and development instances. How can the user find the cost distribution?
1. The user should download the activity report of the EC2 services as it has the instance ID wise data
2. It is not possible to get the AWS cost usage data of single region instances separately
3. The user should use Cost Distribution Metadata and AWS detailed billing
4. The user should use Cost Allocation Tags and AWS billing reports
Correct Answer : 4
Explanation: You can use cost allocation tags to categorize and track your AWS costs. When you apply tags to your AWS resources (such as Amazon EC2 instances or Amazon S3 buckets), AWS
generates a cost allocation report as a comma-separated value (CSV file) with your usage and costs aggregated by your tags. You can apply tags that represent business categories
(such as cost centers, application names, or owners) to organize your costs across multiple services.
The cost allocation report includes all of your AWS costs for each billing period. The report includes both tagged and untagged resources, so you can clearly organize the charges for
resources. For example, if you tag resources with an application name, you can track the total cost of a single application that runs on those resources. AWS provides cost allocation
tags to categorize and track the AWS costs. When the user applies tags to his AWS resources (such as Amazon EC2 instances or Amazon S3 buckets., AWS generates a cost allocation
report as a comma-separated value (CSV file. with the usage and costs aggregated by those tags. The user can apply tags which represent business categories (such as cost centres,
application names, or instance type - Production/Dev. to organize usage costs across multiple services.
At the end of the billing cycle, the total charges (tagged and untagged) on the detailed billing report with cost allocation tags reconciles with the total charges on your Bills page
total and other detailed billing reports for the same period.
You can also use tags to filter views in Cost Explorer. Note that before you can filter views by tags in Cost Explorer, you must have applied tags to your resources, as described in
the following section.
AWS writes detailed billing reports to an Amazon S3 bucket that you create and own. You can retrieve these reports from the bucket using the Amazon S3 API, AWS Management Console for
Amazon S3, or the Amazon S3 command line interface (CLI). The cost allocation report cannot be downloaded from the Account Activity page of the Billing and Cost Management console.
A tag is a label you assign to an AWS resource. Each tag consists of a key and a value, both of which you define. AWS uses tags as a mechanism to organize your resource costs on your
cost allocation report.
Related Questions
Question : QuickTechie.com sys admin has enabled logging on ELB. Which of the below mentioned fields will not be a part of the log file name?
1. Load Balancer IP
2. EC2 instance IP
3. S3 bucket name
4. Random string
Question : HadoopExam.com sysadmin has created a queue named "awsmodule" with SQS for getting info on new learner.
One of the consumers of queue is down for 3 days and then becomes available. Will that component receive message from queue?
1. Yes, since SQS by default stores message for 4 days
2. No, since SQS by default stores message for 1 day only
3. No, since SQS sends message to consumers who are available that time
4. Yes, since SQS will not delete message until it is delivered to all consumers
Question : QuickTechie.com has setup multiple IAM users. The organization wants that each IAM user accesses the IAM console only within the organization
and not from outside. How can it achieve this?
1. Create an IAM policy with the security group and use that security group for AWS console login
2. Create an IAM policy with a condition which denies access when the IP address range is not from the organization
3. Configure the EC2 instance security group which allows traffic only from the organization's IP range
4. Create an IAM policy with VPC and allow a secure gateway between the organization and AWS Console
Question : An organization has created one IAM user and applied the below mentioned policy to the user. What entitlements do the IAM users avail with this policy? { "Version":
"2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": "ec2:Describe*",
"Resource": "*"
},{ "Effect": "Allow"
"Action": [
"cloudwatch:ListMetrics",
"cloudwatch:GetMetricStatistics",
"cloudwatch:Describe*"
], "Resource": "*"
},{ "Effect": "Allow",
"Action": "autoscaling:Describe*",
"Resource": "*"
}]}
1. The policy will allow the user to perform all read only activities on the EC2 services
2. The policy will allow the user to list all the EC2 resources except EBS
3. The policy will allow the user to perform all read and write activities on the EC2 services
4. The policy will allow the user to perform all read only activities on the EC2 services except load Balancing
Question : A user has enabled session stickiness with ELB. The user does not want ELB to manage the cookie; instead he wants the application to manage
the cookie. What will happen when the server instance, which is bound to a cookie, crashes?
1. The response will have a cookie but stickiness will be deleted
2. The session will not be sticky until a new cookie is inserted
3. ELB will throw an error due to cookie unavailability
4. The session will be sticky and ELB will route requests to another server as ELB keeps replicating the Cookie
Question : A user is observing the EC CPU utilization metric on CloudWatch. The user has observed some interesting patterns while filtering over the
week period for a particular hour. The user wants to zoom that data point to a more granular period. How can the user do that easily with
CloudWatch?
1. The user can zoom a particular period by selecting that period with the mouse and then releasing the mouse
2. The user can zoom a particular period by double clicking on that period with the mouse
3. The user can zoom a particular period by specifying the aggregation data for that period
4. The user can zoom a particular period by specifying the period in the Time Range