AWS Certified Solutions Architect – Associate Questions and Answers (Dumps and Practice Questions)
Question : Select the correct statement from below
1. Amazon CloudWatch uses Amazon Simple Notification Service (Amazon SNS) to send email.
2. You can create an alarm from the Alarms list in the Amazon CloudWatch console.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Amazon Cloudwatch alarm can be configure that sends email when EBS exceeds 100 MB throughput
5. You can create alarms that automatically stop or terminate your Amazon Elastic Compute Cloud (Amazon EC2) instances when you no longer need them to
be running
6. You can not monitor your estimated Amazon Web Services (AWS) charges using Amazon CloudWatch
1. 1,2,3,4
2. 2,3,4,5
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1,2,4,5
5. 1,2,3,6
Ans : 4
Exp : Amazon CloudWatch uses Amazon Simple Notification Service (Amazon SNS) to send email. When you create a CloudWatch alarm, you can add this Amazon SNS
topic to send an email notification when the alarm changes state.
You can create an alarm from the Alarms list in the Amazon CloudWatch console.
Amazon CloudWatch alarm that sends an Amazon Simple Notification Service email message when the alarm changes state from OK to ALARM.
Amazon CloudWatch console or the AWS command line interface (CLI) to set up an Amazon Simple Notification Service notification
and configure an alarm that monitors load balancer latency exceeding 100 ms.
AWS Management Console or the command line tools to set up an
Amazon Simple Notification Service notification and to configure an alarm that sends email when EBS exceeds 100 MB throughput.
Using Amazon CloudWatch alarm actions, you can create alarms that automatically stop or terminate your
Amazon Elastic Compute Cloud (Amazon EC2) instances when you no longer need them to be running.
You can monitor your estimated Amazon Web Services (AWS) charges using Amazon CloudWatch.
When you enable the monitoring of estimated charges for your AWS account,
the estimated charges are calculated and sent several times daily to Amazon CloudWatch as metric data that is stored for 14 days.
Question : By default when an application checks the header for a request coming from ELB, which IP address will it receive?
1. IP address of the load balancer
2. Instance IP
3. Access Mostly Uused Products by 50000+ Subscribers
4. Elastic IP
Ans : 1
Exp :The Proxy Protocol header helps you identify the IP address of a client when you use a load balancer configured for TCP/SSL connections.
Because load balancers intercept traffic between clients and your back-end instances, the access logs from your back-end instance contain the
IP address of the load balancer instead of the originating client. When Proxy Protocol is enabled, the load balancer adds a human-readable
format header that contains the connection information, such as the source IP address, destination IP address, and port numbers of the client.
The header is then sent to the back-end instance as a part of the request. You can parse the first line of the request to retrieve your
client's IP address and the port number.
If the client connects with IPv6, the address of the proxy in the header will be the public IPv6 address of your load balancer.
This IPv6 address matches the IP address that is resolved from your load balancer's DNS name that is prefixed with either ipv6 or dualstack.
If the client connects with IPv4, the address of the proxy in the header will be the private IPv4 address of the load balancer and will
therefore not be resolvable through a DNS lookup outside the Amazon Elastic Compute Cloud (Amazon EC2) network.
Question : You have a website, which getting popular day by day and traffic is increasing as well. Hence, you increase the EC instances to handle
heavy traffic as well as introduced the ELB in front of all EC2 instances to balance the traffic. However, you see that your ELB is not accepting
traffic, why?
1. You had forgotten to configure the PORT on which incoming traffic will be accepted
2. You have forgotten to configure Security Group for ELB
3. Access Mostly Uused Products by 50000+ Subscribers
4. You have forgotten to configure Listener on ELB
Correct Answer : Get Lastest Questions and Answer :
Explanation: To accept the incoming traffic through load balancer, it is mandatory that you configure at list one listener on the on ELB.
However, you can configure more than one listener on ELB.
Question : Your website is working fine with the EC instances in normal load initially. Now, it became quite popular and required higher number of
EC2 instances minimum 25 EC2 instances. Hence, you changed your auto scaling launch configuration with minimum instances 15, desired capacity 25 and
maximum 30. As soon as you apply this configuration changes to auto scaling group, you see that 5 instances failed to launch, what could be the reason?
1. Auto scaling configuration is wrong for 5 instances.
2. You cannot launch more than 20 EC2 instances for single application.
3. Access Mostly Uused Products by 50000+ Subscribers
4. It seems, you are working with the default limit of maximum EC2 instances per account per region which is 20, you should raise AWS
request to get more instances.
Correct Answer : Get Lastest Questions and Answer :
Explanation: Yes, there is a default limit in each region 20 to launch EC2 instances per account. You must raise a request to AWS support to
launch more instances in auto scaling group.
Question : You are working with an online training company, which has three different websites one for accessing trainings, one for selling trainings
and one for professional network. These all websites are sharing the various EC2 instances and all this EC2 instances are behind the ELB . Now, you need
to make your website secure and you decided to have a single SSL certificate for all the websites. How will you configure the same, so that end user will
not get any warning with regards to SSL certificate?
1. You will create three copy of same SSL certificate and store it in three different EC2 primary server for each website
2. You will be installing this SSL certificate on ELB and make SAN (Subject Alternative Name) entry for each website in SSL certificate.
3. Access Mostly Uused Products by 50000+ Subscribers
in SSL certificate.
4. You have to create auto scaling group and install the SSL certificate as part of launch configuration.
Correct Answer : Get Lastest Questions and Answer :
Explanation: Use of SSL certificate is to make website secure, so all the traffic between client and server will be encrypted. All the EC2
instances are behind the ELB and reached through it, hence, certificate needs to be installed on ELB. However, issue is how to make it available for all
the website, there is a field named SAN (Subject Alternative Name) which you have to have entry for each website, so that client accessing the website
will not have warning.
Related Questions
Question : You have a Linux EC web server instance running inside a VPC The instance is In a public
subnet and has an EIP associated with it so you can connect to It over the Internet via HTTP or
SSH The instance was also fully accessible when you last logged in via SSH. and was also
serving web requests on port 80.
Now you are not able to SSH into the host nor does it respond to web requests on port 80 that
were working fine last time you checked You have double-checked that all networking
configuration parameters (security groups route tables. IGW'EIP. NACLs etc) are properly
configured {and you haven't made any changes to those anyway since you were last able to reach
the Instance). You look at the EC2 console and notice that system status check shows "impaired."
Which should be your next step in troubleshooting and attempting to get the instance back to a
healthy state so that you can log in again?
1. Stop and start the instance so that it will be able to be redeployed on a healthy host system that
most likely will fix the "impaired" system status
2. Reboot your instance so that the operating system will have a chance to boot in a clean healthy
state that most likely will fix the 'impaired" system status
3. Access Mostly Uused Products by 50000+ Subscribers
since the networking stack of the OS may be locked up causing the "impaired" system status.
4. Add another Elastic Network Interface to the instance and try to connect via that new path since
the networking stack of the OS may be locked up causing the "impaired" system status
5. un-map and then re-map the EIP to the instance, since the IGW/NAT gateway may not be
working properly, causing the "impaired" system status
Question :
Which of the following databases is not supported by RDS?
1. MySQL
2. Microsoft SQL Server
3. Access Mostly Uused Products by 50000+ Subscribers
4. IBM DB2
5. None of the above
Question :
What is an Amazon RDS master user account and how is it different from an AWS account?
1. A master user account is different from an AWS developer account and used only within the context of Amazon RDS to control access to your DB
Instance(s).
2. The master user account is a native database user account which you can use to connect to your DB Instance.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Only 1 and 3 are correct
5. Only 1 and 2 are correct
Question :
If using RDS, what do you not have access to?
1. Parameter Groups
2. MySQL Option Groups
3. Access Mostly Uused Products by 50000+ Subscribers
4. The operating system
5. None of the above
Question :
In which section of instance creation are you able to select Multi-AZ deployment?
1. Launch Screen
2. DB Instance Details
3. Access Mostly Uused Products by 50000+ Subscribers
4. The operating system
5. Management Options
Question :
Amazon Glacier is designed for:
1. active database storage
2. infrequently accessed data
3. Access Mostly Uused Products by 50000+ Subscribers
4. quick backups
5. Management