Auto Scaling is a management service that can automatically adjust elastic computing resources based on your business needs and policies. It supports adding existing ECS instances into the scaling group, whose status however must be .
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
12 comments · newest first
MA
Marsha
12 months ago
Just Created instances can’t be added? That’s surprising!
LU
Luz
12 months ago
Wait, really? I thought Preparing was a valid state.
LI
Lisha
1 year ago
I thought Stopped could work too, but guess not.
EL
Elfriede
1 year ago
Totally agree, Running is the only option!
AM
Amos
1 year ago
It has to be Running to add to the scaling group.
EF
Effie
1 year ago
I definitely recall that only "Running" instances can be added, but I hope I’m not mixing it up with another service.
KI
Kimbery
1 year ago
I’m a bit confused about the statuses. I thought "Created" might work too, but it doesn't sound right now.
DO
Donette
1 year ago
I remember practicing a similar question where the instance status was crucial, and "Running" seemed to be the right choice.
XU
Xuan
1 year ago
I think the instances need to be in a "Running" state to be added to the scaling group, but I'm not completely sure.
GA
Gary
1 year ago
This one seems pretty straightforward. I'm pretty sure the V-model is the right answer here.
WI
Willow
1 year ago
I'm pretty confident I know the answer to this. The 802.11a node and 802.11g access point should be able to communicate, but there may be some performance impacts.
MA
Mary
1 year ago
Hmm, I'm a bit unsure about the specifics here. Retrieving the existing secret and storing its value seems easy enough, but creating a new secret and a pod that can access it might be trickier. I'll need to review my Kubernetes notes carefully.