Premium

AWS Certified Solutions Architect - Professional Questions and Answers (Dumps and Practice Questions)



Question : Which of the following feature will not be available in case of High Storage Instance?
: Which of the following feature will not be available in case of High Storage Instance?
1. Spot Instances
2. On-Demand Instance
3. Reserved Instance
4. None of the above


Correct Answer : Get Lastest Questions and Answer :

Explanation: Spot Instances are a new way to purchase and consume Amazon EC2 Instances. They allow customers to bid on unused EC2 capacity and run those instances for as long as their bid
exceeds the current Spot Price. The Spot Price changes periodically based on supply and demand, and customers whose bids meet or exceed it gain access to the available Spot
Instances. Spot Instances are complementary to On-Demand Instances and Reserved Instances, providing another option for obtaining compute capacity.

Spot Instances provide the ability for customers to purchase compute capacity with no upfront commitment, at hourly rates usually lower than the On-Demand rate. Spot Instances allow
you to specify the maximum hourly price that you are willing to pay to run a particular instance type. Amazon EC2 sets a Spot Price for each instance type in each availability zone,
which is the hourly price all customers will pay to run a Spot Instance for that given period. The Spot Price fluctuates based on supply and demand for instances, but customers will
never pay more than the maximum price they have specified. If the Spot Price moves higher than a customer's maximum price, the customer's instance will be shut down by Amazon EC2.
Other than those differences, Spot Instances perform exactly the same as On-Demand or Reserved Instances.

High Storage instances support all Amazon EC2 features with the exception of Spot Instances. Currently you can only purchase High Storage instances as On Demand or Reserved
Instances. Also, For customers using Microsoft Windows Server, High I/O Instances are only supported with the Microsoft Windows Server AMIs for Cluster Instances or Windows Server
2012.





Question : Which of the following application is a good choice for High Storage instances ?
: Which of the following application is a good choice for High Storage instances ?
1. Hadoop
2. Data warehousing
3. Cluster file systems
4. All 1,2 and 3
5. None of the above


Correct Answer : Get Lastest Questions and Answer :

Explanation: High Storage instances are ideal for applications that require fast access to very large data sets, and can leverage data stores and architectures that manage data redundancy
and availability. Example applications are:

Hadoop
Data warehousing
Cluster file systems






Question : QuickTechie.com is setting up a web application for providing online recruitment solutions in the AWS VPC. And as a backend database
they will use an AWS RDS,so that they can get High Availability and Disaster Recovery requirements fullfilled. They also need secure access to RDS oracle instance
Select the correct statement for above setup?
: QuickTechie.com is setting up a web application for providing online recruitment solutions in the AWS VPC. And as a backend database
1. Create a VPC with one public and one private subnet. Launch an application instance in the public subnet while RDS is launched in the private subnet.
2. Create two separate VPCs and launch a Web app in one VPC and RDS in a separate VPC and connect them with VPC peering.
3. Setup a public and two private subnets in different AZs within a VPC and create a subnet group. Launch RDS with that subnet group.
4. Create a network interface and attach two subnets to it. Attach that network interface with RDS while launching a DB instance.


Correct Answer : Get Lastest Questions and Answer :

Explanation: A virtual private cloud is a virtual network that is logically isolated from other virtual networks in the AWS cloud. Amazon Virtual Private Cloud (VPC) lets you launch AWS
resources, such as an Amazon RDS or Amazon EC2 instance, into a VPC. The VPC can either be a default VPC that comes with your account or it could be one that you create. All VPCs are
associated with your AWS account.

Amazon RDS supported two EC2 platforms: EC2-VPC and EC2-Classic. The EC2-VPC platform has a default VPC where all new DB instances are created unless you specify otherwise. The
EC2-Classic platform does not have a default VPC, but as with either platform, you can create your own VPC and specify that a DB instance be located in that VPC. If you are a new
customer to Amazon RDS or if you are using a region you have not previously used, you are most likely working with the EC2-VPC platform. When an option group is assigned to a DB
instance, it is linked to the supported platform the DB instance is on, either VPC or EC2-Classic (non-VPC). Furthermore, if a DB instance is in a VPC, the option group associated
with the instance is linked to that VPC. This means that you cannot use the option group assigned to a DB instance if you attempt to restore the instance into a different VPC or onto
a different platform. If you restore a DB instance into a different VPC or onto a different platform, you must either assign the default option group to the instance, assign an
option group that is linked to that VPC or platform, or create a new option group and assign it to the DB instance. Note that with persistent or permanent options, such as Oracle
TDE, you must create a new option group that includes the persistent or permanent option when restoring a DB instance into a different VPC. Subnets are segments of a VPC's IP
address range that you designate to group your resources based on security and operational needs. A DB subnet group is a collection of subnets (typically private) that you create in
a VPC and that you then designate for your DB instances. A DB subnet group allows you to specify a particular VPC when creating DB instances using the CLI or API; if you use the
console, you can just select the VPC and subnets you want to use.

Each DB subnet group should have subnets in at least two Availability Zones in a given region. If you are using SQL Server Mirroring with a SQL Server DB instance in a VPC, you must
create a DB subnet group that has 3 subnets in distinct Availability Zones. When creating a DB instance in VPC, you must select a DB subnet group. Amazon RDS uses that DB subnet
group and your preferred Availability Zone to select a subnet and an IP address within that subnet to associate with your DB instance. If the primary DB instance of a Multi-AZ
deployment fails, Amazon RDS can promote the corresponding standby and subsequently create a new standby using an IP address of the subnet in one of the other Availability Zones.

When Amazon RDS creates a DB instance in a VPC, it assigns a network interface to your DB instance by using an IP address selected from your DB Subnet Group. However, we strongly
recommend that you use the DNS Name to connect to your DB instance because the underlying IP address can change during failover. For each DB instance that you run in a VPC, you
should reserve at least one address in each subnet in the DB subnet group for use by Amazon RDS for recovery actions.




Related Questions

Question : Acmeshell is trying to setting up a backup and restore system in AWS of their in premise system and needs HA and DR but is okay to have a longer
recovery time to save costs. Which of the below mentioned setup options helps achieve the objective of cost saving as well as DR in the most effective way?
 : Acmeshell is trying to setting up a backup and restore system in AWS of their in premise system and needs HA and DR but is okay to have a longer
1. Setup a small instance with AutoScaling; in case of DR start diverting all the load to AWS from on premise.
2. Replicate on premise DB to EC2 at regular intervals and setup a scenario similar to the pilot light.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Setup the backup data on S3 and transfer data to S3 regularly using the storage gateway.




Question : Acmeshell.com is having an application which can start and stop an EC instance as per schedule and needs the MAC address of the instance
to be registered with its software. The instance is launched in EC2-CLASSIC. How can the organization update the MAC registration every time an instance is booted?
 : Acmeshell.com is having an application which can start and stop an EC instance as per schedule and needs the MAC address of the instance
1. The instance MAC address never changes. Thus, it is not required to register the MAC address every time.
2. AWS never provides a MAC address to an instance; instead the instance ID is used for identifying the instance for any software registration.
 3. Access Mostly Uused Products by 50000+ Subscribers
4. Acmeshell should write a boot strapping script which will get the MAC address from the instance metadata and use that script to register with the application.




Question : QuickTechie.com is setting up a highly scalable application using the Elastic Beanstalk. The organization is using ELB as well as VPC with public and
private subnets. The organization wants that all the EC2 instances should have a private IP as well as receive data from ELB. Which of below mentioned requirements
will not be required while configuring this setup?
 : QuickTechie.com is setting up a highly scalable application using the Elastic Beanstalk. The organization is using ELB as well as VPC with public and
1. Configure ELB and NAT as a part of the public subnet only.
2. Launch the EC2 instances with only the public subnet.
 3. Access Mostly Uused Products by 50000+ Subscribers
4. Create routing rules which will route all outbound traffic from the EC2 instances through NAT.




Question : QuickTechie.com is planning to use EBS for his DB requirement and QuickTechie already has an EC instance running in the VPC private subnet.
How can QuickTechie attach the EBS volume to a running instance?
 : QuickTechie.com is planning to use EBS for his DB requirement and QuickTechie already has an EC instance running in the VPC private subnet.
1. QuickTechie can create EBS in the same zone as the subnet of instance and attach that EBS to instance.
2. It is not possible to attach an EBS to an instance running in VPC until the instance is stopped.
 3. Access Mostly Uused Products by 50000+ Subscribers
4. QuickTechie must create EBS within the same VPC and then attach it to a running instance.




Question : QuickTechie.com has five branches across the globe (NeYork, Mumbai, HongKong, Geneva and London). They want to expand their data centers such that
their web server will be in the AWS and each branch would have their own database in the local data center. Based on the user login, the company wants to connect
to the data center. How can MySecureData company implement this scenario with the AWS VPC?
 : QuickTechie.com has five branches across the globe (NeYork, Mumbai, HongKong, Geneva and London). They want to expand their data centers such that
1. It is not possible to connect different data centers from a single VPC.
2. Create five VPCs with the public subnet for the app server and setup the VPN gateway for each VPN to connect them individually.
 3. Access Mostly Uused Products by 50000+ Subscribers
4. Use the AWS VPN CloudHub to communicate with multiple VPN connections.




Question : AWS has launched T instances which come with CPU usage credit. QuickTechie.com has a requirement which keeps an instance running for hours.
However, QuickTechie has high usage only during 11 AM to 12 PM and planning to use a T2 small instance for this purpose.
If QuickTechie.com already has multiple instances running since Jan 2012, which of the below mentioned options should the QuickTechie implement while launching a T2 instance?
 : AWS has launched T instances which come with CPU usage credit. QuickTechie.com has a requirement which keeps an instance running for hours.
1. While launching a T2 instance the organization must select EC2-VPC as the platform.
2. The organization must migrate to the EC2-VPC platform first before launching a T2 instance.
 3. Access Mostly Uused Products by 50000+ Subscribers
4. While launching a T2 instance the organization must create a new AWS account as this account does not have the EC2-VPC platform.