Exam AWS Certified Solutions Architect - Professional topic 1 question 11 discussion

Answer is C A: This works if the website is static but we don’t know enough about it to determine if S3 can host it B: ELB can not be used with resources outside of AWS C: CloudFront works with custom origins, in this case the external PHP web app. CloudFront is a good choice for handling the traffic spike in a short time D: The scenario does not say the on-prem app is in a VM, this is not an option https://acloud.guru/forums/aws-certified-solutions-architect-professional/discussion/-KF5MzPkMfG_IyE2jkG1/load-balancing-to-balance-traffic-between-on-premises-web-servers-and-those-host

I don't think it's C. What if database is the bottleneck? Cloudfront would not help with that. I vote D.

B and C is wrong because they do not account for the DB layer. Answer is D. The question mentioned "upcoming days" so I assume over a period of a few days. Importing/Exporting AMIs will take less than an hour. Migrating the DB will not take too many days since the max size is 64TB. The effort and time required for option D is definitely more than other options but it still fits the requirements of the question.

Anwser is B. A and C is not correct because we have dynamic content. D can be considered as an answer but it is time consuming to migrate all onto AWS.

A - makes no sense, site is dynamic and S3 is only static B - would work but is missing the VPN or DC link. C - will reduce the impact by caching part of the content. I manage large PHP applications in a similar fashion and Cloudfront currently absorbs 70-90% of the traffic but it definitely depends on the application. D - not quick to be setup.

C. Offload traffic from on-premises environment: Setup a CIoudFront distribution, and configure CloudFront to cache objects from a custom origin. Choose to customize your object cache behavior, and select a TTL that objects should exist in cache.

I will go with B because You can use an Elastic Load Balancing (ELB) service like Application Load Balancer (ALB) or Network Load Balancer (NLB) to distribute traffic between AWS resources and on-premises servers. This allows you to seamlessly integrate your on-premises infrastructure with your AWS environment.

B and C are only real answers. Its a stupid question because obviously you would have some idea of where the bottle neck was. Would you really try to solve this problem without knowing if the problem was in the Database teir or the webtier. B is more complicated, but would solve the problem. Honestly what you would do in a very short term would be spin up more on prem resources and then work on migrated it to AWS which would take longer than a few days.

C with cloudfront does not necessarily address the unexpected burst. We dont know the nature of the app. PHP can be cached but depending on the site logic, it may still send a ton of requests back so there is no gurantee this will solve the problem. B will solve it. One thing not mentioned here is VPN or DX between on-prem and cloud. VPN can be setup quickly

C is most fast

C. is the only possible option B. Wrong, ELB is regional, cannot distribute between EC2 and on-prem D. is wrong since you cannot create RDS read replicas with on premises MYSQL server

In short notice either DX or VPN will take longer to establish connectivties.. besides to ELB was not specific if can scale to reach OnPrem there still custom config to create connection and scale the pool using IP Addresses which in the option not clear.. would go for C.. CloudFront for static and dynamic..

Option B (Hybrid environment) suggests creating an AMI (Amazon Machine Image) of the web servers and setting up an Auto Scaling group to scale the web tier based on incoming traffic. It also suggests using Elastic Load Balancing (ELB) to balance traffic between on-premises web servers and those hosted in AWS. This approach allows for quick scaling of the web tier to handle increased traffic, leveraging the elasticity and scalability of AWS. It provides a hybrid solution where both on-premises and AWS resources work together to handle the burst in traffic, ensuring full site functionality.

Option B would be a better option to handle any amount of traffic with the ELB and autoscaling of the EC2 web instances.

I think B will work best since the application is fully hosted on premise , offloading it by creating a hybrid environment will handle the short time traffic burst

Even though chatGPT isn't always correct, this answer below is persuasive. B. Hybrid environment: Create an AMI, which can be used to launch web servers in EC2. Create an Auto Scaling group, which uses the AMI to scale the web tier based on incoming traffic. Leverage Elastic Load Balancing to balance traffic between on-premises web servers and those hosted in AWS. Option B would provide full site functionality while improving the ability of your application to handle unpredictable bursts in web traffic. This option involves creating an Amazon Machine Image (AMI) of the web servers and launching them in EC2 instances. An Auto Scaling group is created to scale the web tier based on incoming traffic, and Elastic Load Balancing is used to balance traffic between on-premises web servers and those hosted in AWS.

A. S3 web hosting only for static content. Two-tier, application/DB, most likely not static. If it is static, why not just migrate all but failover? B. Hybrid with auto-scaling EC2 group may work. What about DB? Could be the DB the bottleneck? How to handle on-premises server's performance metrics (quite complex) C: CloudFront can be set up quickly, and it supports both static and dynamic cache, which offloads the loads from applications and DB. D: This could be a good long-term solution but not for improving the ability of the application in the short timeframe required.