MENU
A video streaming company uses SLB to distribute user requests to 30 ECS instances (the 30 ECS instances have the same configuration). Yet, the company finds that the service traffic soars dramatically every night from 20:00 to 02:00. According to their calculation, the evening traffic is 100% higher than the traffic in other periods of time. To properly respond to user requests, which of the following methods is most preferred from the perspective of cost and implementation simplicity?
Suggested Answer: A
Get Premium ACA-Cloud1 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
22 comments · newest first
AL
Aleta
11 months ago
Weights for ECS instances? Seems overly complicated.
MI
Miss
11 months ago
Option B sounds too labor-intensive for nightly traffic spikes.
SH
Shelia
12 months ago
Surprised they don't just use Auto Scaling from the start!
AL
Alishia
12 months ago
I disagree, manual scaling gives more control.
MA
Maira
1 year ago
Auto Scaling is definitely the way to go!
TY
Ty
1 year ago
I feel like option D is similar to what we practiced, but I’m not clear on the difference between upgrading/downgrading versus adding/removing instances.
AN
Andra
1 year ago
I think configuring weights for the ECS instances could work, but it might be more complex than just using Auto Scaling.
VO
Von
1 year ago
I'm not entirely sure, but manually creating instances every night sounds really tedious and could lead to errors.
JU
Julene
1 year ago
I remember we discussed Auto Scaling in class, and it seems like the most efficient way to handle fluctuating traffic.
TE
Terina
1 year ago
I'm a little unsure about the details of how Auto Scaling works, so I'm not 100% sure if option A is the best choice. The manual approach in option B seems like it could work, but it does sound like a lot of effort. I might need to do some research on Auto Scaling before making a decision.
MA
Maynard
1 year ago
Option A looks like the way to go here. Auto Scaling is designed to handle these kinds of traffic fluctuations, and it should be the most efficient and low-maintenance solution. I feel pretty confident that this is the best approach for this scenario.
EU
Eugene
1 year ago
This seems like a classic case of handling traffic spikes. I'd probably go with option A and configure Auto Scaling to automatically add or reduce instances as needed. That seems like the most cost-effective and straightforward solution.
DE
Dean
1 year ago
Hmm, I'm a bit confused by the options. Manually creating and removing instances every day seems like a lot of work, and I'm not sure I fully understand the weight configuration in option C. I think I'll need to re-read the question and options carefully before deciding.
VE
Vernice
1 year ago
This seems straightforward. Option B looks like the best fit since it has the 'Contact' array with the individual contact details, which aligns with the card layout.
AL
Alton
1 year ago
Okay, I think I've got this. Consolidating shipments and reducing pickups should primarily reduce total transportation costs, which is option C. The other choices don't seem as directly related to those logistics strategies.
DY
Dylan
1 year ago
I think option D is the best way to go. Trying to work around the delays or proceed without the escort could lead to incomplete or inaccurate results.
LA
Lai
2 years ago
Configuring weights could work but not as clean. Auto Scaling is my pick too.
JE
Jettie
2 years ago
Totally. Auto Scaling handles traffic variability better without much setup.
KI
Kiley
2 years ago
True, manual process is just a hassle and more prone to errors.
DE
Denae
2 years ago
Yeah, I'd say configure Auto Scaling. Adding/removing ECS manually is a pain.
NO
Noble
3 years ago
Feels tricky, but Auto Scaling makes sense. Simpler and cost-efficient.
AU
Audra
3 years ago
What do you think about the question on video streaming company traffic?