Premium

AWS Certified SysOps Administrator - Associate Questions and Answers (Dumps and Practice Questions)



Question : You are tasked with setting up a cluster of EC Instances for a NoSOL database The database
requires random read 10 disk performance up to a 100.000 IOPS at 4KB block side per node
Which of the following EC2 instances will perform the best for this workload?
  : You are tasked with setting up a cluster of EC Instances for a NoSOL database The database
1. A High-Memory Quadruple Extra Large (m2 4xlarge) with EBS-Optimized set to true and a PIOPs EBS volume
2. A Cluster Compute Eight Extra Large (cc2 8xlarge) using instance storage
3. Access Mostly Uused Products by 50000+ Subscribers
4. A Cluster GPU Quadruple Extra Large (cg1 4xlarge) using four separate 4000 PIOPS EBS volumes in a RAID 0 configuration



Correct Answer : Get Lastest Questions and Answer :

Explanation: I2 - High I/O Instances : This family includes the High Storage Instances that provide very fast SSD-backed instance storage optimized for very high random I/O performance, and
provide high IOPS at a low cost.

The question refers to a cluster of EC2 instances. So even a failure of single instance shouldn't matter, additionally it can always be backed up to S3.

"The SSD storage is local to the instance. Using PV virtualization, you can expect 120,000 random read IOPS (Input/Output Operations Per Second) and between 10,000 and 85,000 random
write IOPS, both with 4K blocks. For HVM and Windows AMIs, you can expect 90,000 random read IOPS and 9,000 to 75,000 random write IOPS"






Question : When an EC EBS-backed (EBS root) instance is stopped, what happens to the data on any ephemermal store volumes?
  :  When an EC EBS-backed (EBS root) instance is stopped, what happens to the data on any ephemermal store volumes?
1. Data will be deleted and will no longer be accessible
2. Data Is automatically saved in an EBS volume.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Data is unavailable until the instance is restarted


Correct Answer : Get Lastest Questions and Answer :
Explanation: An EBS-backed instance is an EC2 instance which uses such a device as its root partition, rather than local disk. EBS-backed images can boot in seconds (as
opposed to minutes for less-well cached S3 images) as they just need to stream enough of the image to start the boot process. They also can be up to 1TB in size - in other words the
max size of any EBS volume. EBS volumes also have different performance characteristics than local drives, which may need to be taken into account depending on your particular use.

The key benefit is that EBS-backed instances can be 'suspended' - by stopping an EBS-backed instance, you can resume it later, with all EBS-backed state (e.g. the OS state) being
maintained. In this way it is more akin to the slices at slicehost, or a real, physical machine.

There is one out and out downside when compared to S3-hosted images - your charges will be higher. You will be charged for IO, which could mount up depending on your particular usage
patterns. You're also charged for the allocated size of the EBS volume too.EBS-Backed" Instances : Note that there is a difference between "stop" and "terminate". If you "stop" an
instance that is backed by EBS then the information on the root volume will still be in the same state when you "start" the machine again. If you "terminate" the machine, then even
if it is backed by EBS it is gone. Creating the AMI will save that state for you and allow you to start a new instance to replace a terminated instance. The virtual machine's hard
drive is considered "ephemeral". The term "ephemeral" comes from the greek word "ephemeros" which means "lasting only one day". Anything on such a hard drive should be considered
temporary. Unless the data is copied off the hard drive, if the virtual machine is stopped, then the data is lost. This includes data, software, and even an operating system that
resides on those hard drives.

The data stored on a local instance store will persist only as long as that instance is alive. However, data that is stored on an Amazon EBS volume will persist independently of the
life of the instance. Therefore, we recommend that you use the local instance store for temporary data and, for data requiring a higher level of durability, we recommend using Amazon
EBS volumes or backing up the data to Amazon S3. If you are using an Amazon EBS volume as a root partition, you will need to set the Delete On Terminate flag to "N" if you want your
Amazon EBS volume to persist outside the life of the instance. However, data still in ephemermal store is not stored in EBS volume hence will be deleted.







Question : Your team Is excited about theuse of AWS because now they have access to programmable
Infrastructure" You have been asked to manage your AWS infrastructure In a manner similar to
the way you might manage application code You want to be able to deploy exact copies of
different versions of your infrastructure, stage changes into different environments, revert back to
previous versions, and identify what versions are running at any particular time (development test
QA. production).

Which approach addresses this requirement?


  : Your team Is excited about theuse of AWS because now they have access to programmable
1. Use cost allocation reports and AWS Opsworks to deploy and manage your infrastructure.
2. Use AWS CloudWatch metrics and alerts along with resource tagging to deploy and manage your infrastructure.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Use AWS CloudFormation and a version control system like GIT to deploy and manage your infrastructure.


Correct Answer : Get Lastest Questions and Answer :

Explanation: AWS CloudFormation is a service that gives developers and businesses an easy way to create a collection of related AWS resources and provision them in an orderly and
predictable fashion.

AWS CloudFormation automates and simplifies the task of repeatedly and predictably creating groups of related resources that power your applications. Creating and interconnecting all
resources your application needs to run is now as simple as creating a single EC2 or RDS instance.

These services are designed to complement each other. AWS Elastic Beanstalk provides an environment to easily develop and run applications in the cloud. It is integrated with
developer tools and provides a one-stop experience for you to manage the lifecycle of your applications. AWS CloudFormation is a convenient deployment mechanism for a broad range of
AWS resources. It supports the infrastructure needs of many different types of applications such as existing enterprise applications, legacy applications, applications built using a
variety of AWS resources and container-based solutions (including those built using AWS Elastic Beanstalk).

AWS CloudFormation supports Elastic Beanstalk application environments as one of the AWS resource types. This allows you, for example, to create and manage an AWS Elastic
Beanstalk-hosted application along with an RDS database to store the application data. In addition to RDS instances, any other supported AWS resource can be added to the group as
well.

Yes. You can use AWS CloudFormation to modify and update the resources in your existing stacks in a controlled and predictable way. By using templates to manage your stack changes,
you have the ability to apply version control to your AWS infrastructure just as you do with the software running on it.

A template can be used repeatedly to create identical copies of the same stack (or to use as a foundation to start a new stack). You can capture and control region-specific
infrastructure variations such as Amazon EC2 AMIs, as well as Amazon EBS and Amazon RDS snapshot names. Templates are simple JSON-formatted text files that can be placed under your
normal source control mechanisms, stored in private or public locations such as Amazon S3, and exchanged via email. With AWS CloudFormation, you can "open the hood," to see exactly
which AWS resources make up a stack. You retain full control and have the ability to modify any of the AWS resources created as part of a stack.


Answer: 4

- Answer 1: does not provide versioning
- Answer 2: does not provide versioning
- Answer 3: Beanstalk provide version control over your application (not infrastructure)




Related Questions


Question : What is a placement group?
 : What is a placement group?
1. A collection of Auto Scaling groups in the same Region
2. Feature that enables EC2 instances to interact with each other via high bandwidth, low latency connections
3. Access Mostly Uused Products by 50000+ Subscribers
4. A collection of authorized Cloud Front edge locations for a distribution


Question : Your entire AWS infrastructure lives inside of one Amazon VPC You have an infrastructure
monitoring application running on an Amazon instance in Availability Zone (AZ) A of the region,
and another application instance running in AZ B. The monitoring application needs to make use
of ICMP ping to confirm network reachability of the instance hosting the application.
Can you configure the security groups for these instances to only allow the ICMP ping to pass
from the monitoringinstance to the application instance and nothing else, If so how?
 :  Your entire AWS infrastructure lives inside of one Amazon VPC You have an infrastructure
1. No Two instances in two different AZ's can't talk directly to each other via ICMP ping as that
protocol is not allowed across subnet (iebroadcast) boundaries
2. Yes Both the monitoring instance and the application instance have to be a part of the same
security group, and that security group needs to allow inbound ICMP
3. Access Mostly Uused Products by 50000+ Subscribers
application instance's security group needs to allow Inbound ICMP.
4. Yes, Both the monitoring instance's security group and the application instance's security group
need to allow both inbound and outbound ICMP ping packets since ICMP is not a connection oriented protocol



Question : You have two Elastic Compute Cloud (EC) instances inside a Virtual Private Cloud (VPC) in the
same Availability Zone (AZ) but in different subnets.One instance is running a database and the
other instance an application that will interface with the database. You want to confirm that they
can talk to each other for your application to work properly.
Which two things do we need to confirm in the VPC settings so that these EC2 instances can
communicate inside the VPC?

Choose 2 answers
A. A network ACL that allows communication between the two subnets.
B. Both instances are the same instance class and using the same Key-pair.
C. That the default route is set to a NAT instance or internet Gateway (IGW) for them to communicate.
D. Security groups are set to allow the application host to talk to the database on the right port/protocol.

 : You have two Elastic Compute Cloud (EC) instances inside a Virtual Private Cloud (VPC) in the
1. A,B
2. A,D
3. Access Mostly Uused Products by 50000+ Subscribers
4. C,D



Question : Which services allow the customer to retain full administrative privileges of the underlying EC instances?

Choose 2 answers
A. Amazon Elastic Map Reduce
B. Elastic Load Balancing
C. AWS Elastic Beanstalk
D. Amazon Elasticache
E. Amazon Relational Database service


 : Which services allow the customer to retain full administrative privileges of the underlying EC instances?
1. A,B
2. A,D
3. Access Mostly Uused Products by 50000+ Subscribers
4. C,D
5. A,C


Question : You have a web-style application with a stateless but CPU and memory-intensive web tier running on a cc xlarge EC instance inside of a VPC. The instance when under
load is having problems returning requests within the SLA as defined by your business. The application maintains its state in a DynamoDB table, but the data tier is properly
provisioned and responses are consistently fast. How can you best resolve the issue of the application responses not meeting your SLA?
 : You have a web-style application with a stateless but CPU and memory-intensive web tier running on a cc xlarge EC instance inside of a VPC. The instance when under
1. Add another cc2 8xlarge application instance, and put both behind an Elastic Load Balancer
2. Move the cc2 8xlarge to the same Availability Zone as the DynamoDB table
3. Access Mostly Uused Products by 50000+ Subscribers
4. Move the database from DynamoDB to RDS MySQL in scale-out read-replica configuration



Question : You are managing a legacy application Inside VPC with hard coded IP addresses in its configuration.
Which two mechanisms will allow the application to failover to new instances without the need for reconfiguration? Choose 2 answers

A. Create an ELB to reroute traffic to a failover instance
B. Create a secondary ENI that can be moved to a failover instance
C. Use Route53 health checks to fail traffic over to a failover instance
D. Assign a secondary private IP address to the primary ENI that can be moved to a failover instance

 : You are managing a legacy application Inside VPC with hard coded IP addresses in its configuration.
1. A,B
2. B,C
3. Access Mostly Uused Products by 50000+ Subscribers
4. C,D
5. A,C