Q: 2
Scenario: During SageMaker AMT tuning, many jobs continue running despite poor early performance, wasting GPU usage. The company needs a tuning strategy that automatically stops underperforming trials and reallocates resources. Question- Which tuning strategy should be employed to enhance optimization efficiency and expedite hyperparameter search?. Options:
Options
Discussion
B . Hyperband is what actually provides the automatic early stopping, C is tempting but doesn't do the auto-stopping part.
B tbh, Hyperband is what I've seen recommended in the official guide and practice exams for auto-stopping poor jobs. Not 100 percent sure, but pretty confident compared to the other options.
C or D for this one. Seen similar on practice exams and random search or Bayesian gets mentioned a lot. Official guide and exam reports help here.
Why not C for this if the focus wasn’t on early stopping?
B here. Hyperband is basically built for this exact early stopping and resource allocation scenario, unlike grid or random search. Pretty sure that's the one they want, but open to pushback if I'm missing something.
C is good for refining search, but it won't cut off bad trials early. B matches the need for auto early stopping and resource shifting since Hyperband does that by design. Unless they ask strictly about optimization, I'd stick with B here. Open to other reads but pretty sure.
B not C. Hyperband is built for early stopping and reallocating resources, which is the key point in this scenario.
B imo, Hyperband fits since it auto-stops weak trials and reallocates GPU. Saw this highlighted in the AWS official guide and exam practice sets. If the scenario didn't need early stopping, C might work, but B is right here.
I'd say C on this. Bayesian optimization is known for smartly narrowing down the hyperparameter space, and in some tuning cases, it can outperform grid or random search. Not totally sure here though, since Hyperband is also popular.
Option C. had something like this in a mock exam.
Be respectful. No spam.