Section: 8 Classic Solutions Architecture Discussions Flashcards
You have an ASG that scales on demand based on the traffic going to your new website: TriangleSunglasses.Com. You would like to optimise for cost, so you have selected an ASG that scales based on demand going through your ELB. Still, you want your solution to be highly available so you have selected the minimum instances to 2. How can you further optimize the cost while respecting the requirements?
A) Remove the ELB and use Elastic IP instead
B) Reserve two EC2 instances
C) Reduce the minimum number of instances to 1
D) Reduce the minimum number of instances to 0
B) Reserve two EC2 instances
This is the way to save further costs as we know we will run 2 EC2 instances no matter what.
Which of the following will NOT help make our application tier stateless?
A) Offload data in RDS
B) Store the session data in ElastiCache
C) Send the session data through the client cookies
D) Storing shared data on EBS volumes
D) Storing shared data on EBS volumes
EBS volumes are created for a specific AZ and can only be attached to one EC2 instance at a time. This will not help make our application stateless
You are looking to store shared software updates data across 100s of EC2 instances. The software updates should be dynamically loaded on the EC2 instances and shouldn’t require heavy operations. What do you suggest?
A) Store the software updates on EBS and sync them using data replication software from one master in each AZ
B) Store the software updates on EFS and mount EFS as a network drive
C) Package the software updates as an EBS snapshot and create EBS volumes for each new software updates
D) Store the software updates on an Amazon RDS instance
B) Store the software updates on EFS and mount EFS as a network drive
EFS is a network file system (NFS) and allows to mount the same file system to 100s of EC2 instances. Publishing software updates their allow each EC2 instance to access them.
As a solution architect managing a complex ERP software suite, you are orchestrating a migration to the AWS cloud. The software traditionally takes well over an hour to setup on a Linux machine, and you would like to make sure your application does leverage the ASG feature of auto scaling based on the demand. How do you recommend you speed up the installation process?
A) Use a Golden AMI
B) Bootstrap using User Data
C) Store the application in RDS
D) Retrieve the application setup files from EFS
A) Use a Golden AMI
Golden AMI are a standard in making sure you snapshot a state after an application installation so that future instances can boot up from that AMI quickly.
I am creating an application and would like for it to be running with minimal cost in a development environment with Elastic Beanstalk. I should run it in
A) Single Instance Mode
B) High Availability Mode
A) Single Instance Mode
This will create one EC2 instance and one Elastic IP
My deployments on Elastic Beanstalk have been painfully slow, and after looking at the logs, I realize this is due to the fact that my dependencies are resolved on each EC2 machine at deployment time. How can I speed up my deployment with the minimal impact?
A) Remove some dependencies in your code
B) Place the dependencies in Amazon EFS
C) Create a Golden AMI that contains dependencies and launch the EC2 instances from that
C) Create a Golden AMI that contains dependencies and launch the EC2 instances from that
Golden AMI are a standard in making sure save the state after the installation or pulling dependencies so that future instances can boot up from that AMI quickly.