Exams > Amazon > AWS-SysOps: AWS Certified SysOps Administrator
AWS-SysOps: AWS Certified SysOps Administrator
Page 39 out of 91 pages Questions 381-390 out of 910 questions
Question#381

What is a placement group in Amazon EC2?

  • A. It is a logical grouping of EC2 instances within a single Availability Zone.
  • B. It the edge location of your web content.
  • C. It is a group used to span multiple Availability Zones.
  • D. It is the AWS region where you run the EC2 instance of your web content.
Discover Answer Hide Answer

A
A placement group is a logical grouping of instances within a single Availability Zone. Placement groups are recommended for applications that benefit from low network latency, high network throughput, or both.
Reference:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html

Question#382

In which screen does a user select the Availability Zones while configuring Auto Scaling?

  • A. Auto Scaling Group Creation
  • B. Auto Scaling Instance Creation
  • C. Auto Scaling Launch config Creation
  • D. Auto Scaling Policy Creation
Discover Answer Hide Answer

A
You can take advantage of the safety and reliability of geographic redundancy by spanning your Auto Scaling group across multiple Availability Zones within a region and then attaching a load bal-ancer to distribute incoming traffic across those Availability Zones. Incoming traffic is distributed equally across all Availability
Zones enabled for your load balancer.
Reference:
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/GettingStartedTutorial.html

Question#383

Which of the CloudWatch services mentioned below is NOT a part of the AWS free tier?

  • A. 10 alarms/month
  • B. 1 million API request/month
  • C. 10 metrics/month
  • D. 15 detailed monitoring metrics
Discover Answer Hide Answer

D
CloudWatch provides the basic monitoring metrics (at five-minute frequency), 10 metrics (applica-ble to detailed monitoring for the Amazon EC2 instances or custom metrics), 10 alarms, and 1 mil-lion API requests each month at no additional charge.
Reference:
http://aws.amazon.com/cloudwatch/pricing/

Question#384

In the context of sending metrics to CloudWatch using Amazon Kinesis, which of the following statements best describes the metric "PutRecord.Latency"?

  • A. It is the time taken per PutRecord operation, measured over the specified time period.
  • B. It is the number of successful records in a PutRecords operation per Amazon Kinesis stream, measured over the specified time period.
  • C. It is the time taken per PutRecords operation to calculate the statistics of the PutRecords opera-tions.
  • D. It is the number of successful PutRecord operations per Amazon Kinesis stream, measured over the specified time period.
Discover Answer Hide Answer

A
The metric PutRecord.Latency measures the time taken per PutRecord operation, measured over the specified time period.

Dimensions: StreamName -
Statistics: Minimum, Maximum, Average

Units: Milliseconds -
Reference:
http://docs.aws.amazon.com/kinesis/latest/dev/monitoring_with_cloudwatch.html

Question#385

Can a user depict CloudWatch metrics such as CPU utilization in % and Network I/O in bytes on a single graph?

  • A. No, a user cannot graph two separate metrics on the same graph.
  • B. Yes, a user can graph several metrics over time on a single graph.
  • C. No, a user cannot plot several metrics on a single graph since the units are different.
  • D. Yes, a user can graph multiple metrics on the same graph provided they are of the same instance in the same AZ.
Discover Answer Hide Answer

B
You can graph several metrics over time on the same graph. The user can select metrics across re-sources and graph them on a single graph. It is not required that they should be of the same instance. They can be of different instances with the same AMI or based on some other dimension. You can filter records and plot them all on the same graph.
Reference:
http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/graph_a_metric_all_resources.html

Question#386

Which of the following comes before Auto Scaling group creation?

  • A. Creating the Auto Scaling launch config
  • B. Creating the Auto Scaling policy
  • C. Creating the Auto Scaling tags
  • D. Creating the Auto Scaling instance
Discover Answer Hide Answer

A
The Auto Scaling launch config is the first step that should be run before a user can create an Auto Scaling group. The launch config has all the information, such as the instance type, AMI ID, and other instance launch parameters. The Auto Scaling group uses this launch config to create a new group.
Reference:
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/LaunchConfiguration.html

Question#387

A placement group in Amazon EC2 can

  • A. place high memory instances in one logical group.
  • B. logically name and tag different tiers of the system (DB, application, business logic etc).
  • C. isolate any instance-type physically so that groups access local resources.
  • D. reduce network latency and increase network throughput
Discover Answer Hide Answer

D
A placement group is a logical grouping of instances within a single Availability Zone. Placement groups are recommended for applications that benefit from low network latency, high network throughput, or both. To provide the lowest latency, and the highest packet-per-second network per-formance for your placement group, choose an instance type that supports enhanced networking.
Reference:
https://aws.amazon.com/ec2/faqs/

Question#388

Which of the following statements is true about Auto Scaling?

  • A. You can only delete your Auto Scaling group but not your Auto Scaling setup.
  • B. If the Auto Scaling infrastructure is being deleted, it is not mandatory to delete the launch con-figuration.
  • C. You can only delete your Auto Scaling set up but not your Auto Scaling group.
  • D. If the Auto Scaling infrastructure is being deleted, it is mandatory to delete the launch configura-tion.
Discover Answer Hide Answer

B
You can create an Auto Scaling group to maintain the healthy number of instances at all times, and optionally delete this basic Auto Scaling infrastructure. You can either delete your Auto Scaling set up or delete just your Auto Scaling group and keep your launch configuration to use at a later time.
Reference:
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/GettingStartedTutorial.html

Question#389

If you specify only the general endpoint (autoscaling.amazonaws.com), Auto Scaling directs your request to the:

  • A. us-west-2 endpoint.
  • B. eu-central-1.
  • C. eu-west-1 endpoint.
  • D. us-east-1 endpoint.
Discover Answer Hide Answer

D
If you just specify the general endpoint (autoscaling.amazonaws.com), Auto Scaling directs your request to the us-east-1 endpoint.
Reference:
http://docs.aws.amazon.com/general/latest/gr/rande.html

Question#390

A user has configured ELB with Auto Scaling. The user temporarily suspended the Auto Scaling terminate process. What might the Availability Zone Rebalancing process (AZRebalance) conse-quently cause during this period?

  • A. Auto Scaling will keep launching instances in all AZs until the maximum instance number is reached.
  • B. AZ Rebalancing might now allow Auto Scaling to launch or terminate any instances.
  • C. AZ Rebalancing might allow the number instances in an Availability Zone to remain higher than the maximum size
  • D. It is not possible to suspend the terminate process while keeping the launch active.
Discover Answer Hide Answer

C
Auto Scaling performs various processes, such as Launch, Terminate, and Availability Zone Re-balance (AZRebalance). The AZRebalance process type seeks to maintain a balanced number of in-stances across Availability Zones within a region. If the user suspends the Terminate process, the AZRebalance process can cause the Auto Scaling group to grow up to ten percent larger than the maximum size. This is because Auto Scaling allows groups to temporarily grow larger than the max-imum size during rebalancing activities. If Auto Scaling cannot terminate instances, the Auto Scal-ing group could remain up to ten percent larger than the maximum size until the user resumes the Terminate process type.
Reference:
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/US_SuspendResume.html

chevron rightPrevious Nextchevron right