You have a content management system running on an Amazon EC2 instance that is approaching 100% CPU
utilization. Which option will reduce load on the Amazon EC2 instance?
A.
Create a load balancer, and register the Amazon EC2 instance with it
B.
Create a CloudFront distribution, and configure the Amazon EC2 instance as the origin
C.
Create an Auto Scaling group from the instance using the CreateAutoScalingGroup action
D.
Create a launch configuration from the instance using the CreateLaunchConfiguration action
Explanation:
https://aws.amazon.com/blogs/aws/new-amazon-ec2-micro-instances/
A
0
0
This doesnt change anything. You need to add another EC2 instance to make an impact in this case.
0
0
I think only B by itself is correct.
Had all 3 others were combined then that would make sense and addressed the CPU capacity issue.To successfully help that single instance, auto-scaling needs to be configured and of course use load-balancer to balance the load.
Frustratingly, this question is like asking “how do you build a house?”
A. Put a roof
B. Lay the foundations
C. Put a wall
1
0
Autoscaling group wont do anything without an ELB in front of it, unless it is a distributed application already (no mention), and the launch configuration doesnt help. Only B, as you say, standalone will solve it
0
0
LoL
0
0
Going with your analogy, try this question:
Joe has too much stuff and no place to put any more in his house. What should Joe do?
A: Put a roof on a new bigger house
B: Throw out some of his stuff to make room (until he really needs a new house)
C: Lay the foundation for a new bigger house
D: Build walls for the new bigger house
The moral to the story is that you don’t always need a new house. As you say, only B by itself is correct.
0
0
I think its B
If your instance’s CPU utilization is approaching 100% then you may want to scale (using Auto Scaling) to additional Micro instances or to a larger instance type. In fact, at this low a price you could run CloudWatch configured for Auto Scaling with two Micro instances behind an Elastic Load Balancer for just under the price of one CloudWatch-monitored Standard Small instance.
0
0
Agree the answer is B
A – Create ELB and register the instance, but only one instance still the same load
B – Cloudfront will have multiple endpoints and cache the files, relieving the load
C – autoscaling without ELB don’t reduce the load
D – lauch configuration is just a configuraiton setting for autoscaling
0
0
agree!
0
0
It’s B
0
0
I choose C
0
0
My answer is A.
CloudFront distribution is for low latency purpose.
0
0
A is not an option, you need more servers
B is for content delivery of static files on (primarily) public facing websites
D is just part of the solution
C is the answer
0
1
you can attach one ec2-instance to ELB
0
0
I choose C.
A is wrong becouse Creating ELB does not solve the issue. We at least need more instances
D is wrong. LauchConfiguration is just a template.
B sounds good BUT it addresses only one aspect, the delivery, but not other possible bottlenecks.
0
0
The answer is C!
A is wrong, with ELB we don’t solve the problem becouse we need more instance
B is wrong, it’s for content delivery, the key is “Create a CloudFront distribution, and configure the Amazon EC2 instance as the origin”
Delivery is one of the job of a content distribution system. There can be other N number of jobs for a content management system – for example search the content, fetching the content, catalog the content, saving the content – many of which is not related to network issues.
D is wrong, LauchConfiguration is just a template. Creating a template does not help in this situation.
0
0
C
If your instance’s CPU utilization is approaching 100% then you may want to scale (using Auto Scaling) to additional Micro instances or to a larger instance type
0
0
My take
C alone will not help, you need a load balancer
Similarly A alone will not help without C
Bcoz its content management Cloudfront can do the trick w/o any additional services
Any challengers??
1
0
i will go with b – As its content management system we can go with cloud front
“…This reduces the load on your origin servers reducing the need to scale your origin infrastructure, which can bring you further cost savings..”
0
0
Cant be c bcoz auto scaling required ELB also
0
0
C
You can create an ASG from instance ID
http://docs.aws.amazon.com/AutoScaling/latest/APIReference/API_CreateAutoScalingGroup.html
0
0
I’d like say C
you guys should see this :
http://docs.aws.amazon.com/ko_kr/elasticbeanstalk/latest/dg/events.common.cpu.html
0
0
it is related to AWS Elastic Beanstalk
0
0
Its B
Creating an ASG on its own wont reduce the load on the instance, you’d need to create scaling policies based off a Cloudwatch Alarm on the CPU Util % to make that work. The CreateAutoScalingGroup API doesnt associate policies
The fact it says content mgt means it’s Cloudfront
0
0
I choose C visit below URl
http://docs.aws.amazon.com/autoscaling/latest/userguide/policy_creating.html
0
0
100% it is C.
A-With one instance, load balancer is useless.
B-You cannot scale a content management system with CDN, the concepts just don’t match.
C-Auto scale will reduce the cpu load. CORRECT ANSWER.
D-Irrevelant.
0
1
It all depends on how you interpret Content management system, for most times it is used to upload content into the website.
B could be correct if Cloudfront caches the content and then sends it to source (reverse CDN)
C is correct if processing needs to be reduced
With C however its a given that
There is a LB
There is a Launch Configuration
There is a CloudWatch
And you have adequate IAM privilidges to configure autoscale 🙂
As all these are ingredients for AutoScale.
0
0
B without brainstorm:
https://aws.amazon.com/cloudfront/dynamic-content/
0
0
Agreed. This link too:
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Resources.html#resources-content-management-system
0
0
B is the only correct answer. A ….wouldn’t make sense because you will be registering only the instance with the load balancer which won’t make any difference. C…You can’t create auto-scaling group from a running instance, auto-scaling group involves creating launch configurations and creating the instances from the LC. D…creating launch config from the instance is not enough to reduce the load. Only B ,where cloudfront edge servers are used to cache some of the content can reduce the load as those contents will be served from the cdn rather than the instance.
0
0
I choose answer B.
CloudFront does support caching dynamic content.
0
0
it is B. Once the content is cached in cloudfront edge servers, the the requests won’t hit the web servers directly anymore, just the edge server, thus reducing the load. The only load on web servers will be when cloudfront syncs new content from it to the edge servers.
0
0
C. Dont have Load balance. so is it wrong or not.
0
0