AWS-SysOps Guide

AWS-SysOps Exam Royal Pack (In Stock.)

 
  • Amazon
  • Exam Number/Code AWS-SysOps
  • Product Name AWS Certified SysOps Administrator Associate
  • Questions and Answers
  • 324 Q&As
  • Last Updated
  • July 24,2017
  • List Price
  • $128.99
  • Price
  • Today 59.99 USD

Free TrialVersion: demo Buy Now 50% OFF

[Avant-garde] aws certified sysops administrator associate level dumps

It is impossible to pass Amazon aws sysops pdf exam without any help in the short term. Come to Examcollection soon and find the most advanced, correct and guaranteed Amazon aws certified sysops administrator salary practice questions. You will get a surprising result by our Avant-garde AWS Certified SysOps Administrator Associate practice guides.

Q161. - (Topic 1) 

When assessing an organization s use of AWS API access credentials which of the following three credentials should be evaluated? 

Choose 3 answers 

A. Key pairs 

B. Console passwords 

C. Access keys 

D. Signing certificates 

E. Security Group memberships 

Answer: A,C,D 

Explanation: Reference: 

http://media.amazonwebservices.com/AWS_Operational_Checklists.pdf 


Q162. - (Topic 1) 

You have an Auto Scaling group associated with an Elastic Load Balancer (ELB). You have noticed that instances launched via the Auto Scaling group are being marked unhealthy due to an ELB health check, but these unhealthy instances are not being terminated 

What do you need to do to ensure trial instances marked unhealthy by the ELB will be terminated and replaced? 

A. Change the thresholds set on the Auto Scaling group health check 

B. Add an Elastic Load Balancing health check to your Auto Scaling group 

C. Increase the value for the Health check interval set on the Elastic Load Balancer 

D. Change the health check set on the Elastic Load Balancer to use TCP rather than HTTP checks 

Answer:

Explanation: Reference: 

http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/as-add-elb-healthcheck.html 

Add an Elastic Load Balancing Health Check to your Auto Scaling Group 

By default, an Auto Scaling group periodically reviews the results of EC2 instance status to determine the health state of each instance. However, if you have associated your Auto Scaling group with an Elastic Load Balancing load balancer, you can choose to use the Elastic Load Balancing health check. In this case, Auto Scaling determines the health status of your instances by checking the results of both the EC2 instance status check and the Elastic Load Balancing instance health check. 

For information about EC2 instance status checks, see.Monitor Instances With Status Checks.in the.Amazon EC2 User Guide for Linux Instances. For information about Elastic Load Balancing health checks, see.Health Check.in the.Elastic Load Balancing Developer Guide. 

This topic shows you how to add an Elastic Load Balancing health check to your Auto Scaling group, assuming that you have created a load balancer and have registered the load balancer with your Auto Scaling group. If you have not registered the load balancer with your Auto Scaling group, see.Set Up a Scaled and Load-Balanced Application. 

Auto Scaling marks an instance unhealthy if the calls to the Amazon EC2 action.DescribeInstanceStatus.return any state other than.running, the system status shows.impaired, or the calls to Elastic Load Balancing action.DescribeInstanceHealth.returns.OutOfService.in the instance state field. 

If there are multiple load balancers associated with your Auto Scaling group, Auto Scaling checks the health state of your EC2 instances by making health check calls to each load balancer. For each call, if the Elastic Load Balancing action returns any state other than.InService, the instance is marked as unhealthy. After Auto Scaling marks an instance as unhealthy, it remains in that state, even if subsequent calls from other load balancers return an.InService.state for the same instance. 


Q163. - (Topic 3) 

A sysadmin has created the below mentioned policy on an S3 bucket named cloudacademy. The bucket has both AWS.jpg and index.html objects. What does this policy define? 

"Statement": [{ 

"Sid": "Stmt1388811069831", 

"Effect": "Allow", 

"Principal": { "AWS": "*"}, 

"Action": [ "s3:GetObjectAcl", "s3:ListBucket", "s3:GetObject"], 

"Resource": [ "arn:aws:s3:::cloudacademy/*.jpg] 

}] 

A. It will make all the objects as well as the bucket public 

B. It will throw an error for the wrong action and does not allow to save the policy 

C. It will make the AWS.jpg object as public 

D. It will make the AWS.jpg as well as the cloudacademy bucket as public 

Answer:


Q164. - (Topic 3) 

A user has configured ELB with a TCP listener at ELB as well as on the back-end instances. The user wants to enable a proxy protocol to capture the source and destination IP information in the header. Which of the below mentioned statements helps the user understand a proxy protocol with TCP configuration? 

A. If the end user is requesting behind a proxy server then the user should not enable a proxy protocol on ELB 

B. ELB does not support a proxy protocol when it is listening on both the load balancer and the back-end instances 

C. Whether the end user is requesting from a proxy server or directly, it does not make a difference for the proxy protocol 

D. If the end user is requesting behind the proxy then the user should add the “isproxy” flag to the ELB Configuration 

Answer:

Explanation: 

When the user has configured Transmission Control Protocol (TCP. or Secure Sockets Layer (SSL. for both front-end and back-end connections of the Elastic Load Balancer, the load balancer forwards the request to the back-end instances without modifying the request headers unless the proxy header is enabled. If the end user is requesting from a Proxy Protocol enabled proxy server, then the ELB admin should not enable the Proxy Protocol on the load balancer. If the Proxy Protocol is enabled on both the proxy server and the load balancer, the load balancer will add another header to the request which already has a header from the proxy server. This duplication may result in errors. 


Q165. A user is trying to setup a scheduled scaling activity using Auto Scaling. The user wants to setup the recurring schedule. Which of the below mentioned parameters is not required in this case? 

A. Maximum size 

B. Auto Scaling group name 

C. End time 

D. Recurrence value 

Answer:

Auto Scaling based on a schedule allows the user to scale the application in response to predictable load changes. The user can also configure the recurring schedule action which will follow the Linux cron format. If the user is setting a recurring event, it is required that the user specifies the Recurrence value (in a cron format., end time (not compulsory but recurrence will stop after this. and the Auto Scaling group for which the scaling activity is to be scheduled. 


Q166. - (Topic 3) 

A user wants to find the particular error that occurred on a certain date in the AWS MySQL RDS DB. Which of the below mentioned activities may help the user to get the data easily? 

A. It is not possible to get the log files for MySQL RDS 

B. Find all the transaction logs and query on those records 

C. Direct the logs to the DB table and then query that table 

D. Download the log file to DynamoDB and search for the record 

Answer:

Explanation: 

The user can view, download, and watch the database logs using the Amazon RDS console, the Command Line Interface (CLI. or the Amazon RDS API. For the MySQL RDS, the user can view the error log, slow query log, and general logs. The user can also view the MySQL logs easily by directing the logs to a database table in the main database and querying that table. 


Q167. - (Topic 2) 

A customer is using AWS for Dev and Test. The customer wants to setup the Dev environment with 

Cloudformation. Which of the below mentioned steps are not required while using Cloudformation? 

A. Create a stack 

B. Configure a service 

C. Create and upload the template 

D. Provide the parameters configured as part of the template 

Answer:

Explanation: 

AWS Cloudformation is an application management tool which provides application modelling, deployment, configuration, management and related activities. AWS CloudFormation introduces two concepts: the template and the stack. The template is a JSON-format, text-based file that describes all the AWS resources required to deploy and run an application. The stack is a collection of AWS resources which are created and managed as a single unit when AWS CloudFormation instantiates a template. While creating a stack, the user uploads the template and provides the data for the parameters if required. 


Q168. - (Topic 3) 

A user has launched an EC2 instance from an instance store backed AMI. If the user restarts the instance, what will happen to the ephermal storage data? 

A. All the data will be erased but the ephermal storage will stay connected 

B. All data will be erased and the ephermal storage is released 

C. It is not possible to restart an instance launched from an instance store backed AMI 

D. The data is preserved 

Answer:

Explanation: 

A user can reboot an EC2 instance using the AWS console, the Amazon EC2 CLI or the Amazon EC2 API. Rebooting an instance is equivalent to rebooting an operating system. However, it is recommended that the user use Amazon EC2 to reboot the instance instead of running the operating system reboot command from the instance. When an instance launched from an instance store backed AMI is rebooted all the ephermal storage data is still preserved. 


Q169. - (Topic 3) 

A user has configured ELB with two EBS backed instances. The user has stopped the instances for 1 week to save costs. The user restarts the instances after 1 week. Which of the below mentioned statements will help the user to understand the ELB and instance registration better? 

A. There is no way to register the stopped instances with ELB 

B. The user cannot stop the instances if they are registered with ELB 

C. If the instances have the same Elastic IP assigned after reboot they will be registered with ELB 

D. The instances will automatically get registered with ELB 

Answer:

Explanation: 

Elastic Load Balancing registers the user’s load balancer with his EC2 instance using the associated IP address. When the instances are stopped and started back they will have a different IP address. Thus, they will not get registered with ELB unless the user manually registers them. If the instances are assigned the same Elastic IP after reboot they will automatically get registered with ELB. 


Q170. - (Topic 3) 

A user has launched an EC2 Windows instance from an instance store backed AMI. The user has also set the Instance initiated shutdown behavior to stop. What will happen when the user shuts down the OS? 

A. It will not allow the user to shutdown the OS when the shutdown behaviour is set to Stop 

B. It is not possible to set the termination behaviour to Stop for an Instance store backed AMI instance 

C. The instance will stay running but the OS will be shutdown 

D. The instance will be terminated 

Answer:

Explanation: 

When the EC2 instance is launched from an instance store backed AMI, it will not allow the user to configure the shutdown behaviour to “Stop”. It gives a warning that the instance does not have the EBS root volume. 


To know more about the AWS-SysOps, click here.

Tagged as : Amazon AWS-SysOps Dumps, Download AWS-SysOps pdf, AWS-SysOps VCE, AWS-SysOps pass4sure, examcollection AWS-SysOps