Option A (SageMaker automatic model tuning) is the built-in hyperparameter tuning. Option D (SageMaker Experiments) can track and compare tuning jobs, but not directly run them. However, the question asks for features that can be used to perform HPO.
SageMaker automatic model tuning is the primary feature. SageMaker SDK can be used to implement custom tuning, but it's not a feature name. SageMaker Debugger (B) and Model Monitor (C) are not for HPO.
SageMaker Pipelines (E) can orchestrate HPO but is not a direct tuning feature. The best answer is A and D (Experiments can be used to track HPO runs). Alternatively, A and something else.
Let's reconsider: SageMaker automatic model tuning (A) is the official HPO. SageMaker Experiments (D) can be used to track and analyze tuning jobs, but doesn't perform tuning. The question says 'perform hyperparameter optimization'.
Typically, only automatic model tuning performs it. However, sometimes 'SageMaker SDK' is considered. To align with MLS-C01, the correct answer is A and D (Experiments can be used to run multiple trials).
I'll go with A and D.