Which action is critical when managing the deployment process using Cloud Manager?

Question

Options

• AManually testing all pipelines
• BConfiguring CI/CD pipelines for automated deployment
• CSkipping automated tests for faster delivery
• DRefactoring legacy components during the deployment process

• A
  4% (2)
• B
  73% (40)
• C
  7% (4)
• D
  16% (9)

Explanation

Configuring CI/CD pipelines for automated deployment (B) is the critical action because Cloud Manager is specifically designed around pipeline-based automation - it standardizes, enforces, and tracks deployments through configured pipelines, making automation the core feature rather than an optional enhancement.

Why the distractors fail:

• A (Manual testing all pipelines) contradicts the purpose of CI/CD, which exists to replace manual steps with repeatable automation.
• C (Skipping automated tests) is a dangerous anti-pattern; Cloud Manager enforces quality gates precisely to prevent skipping tests.
• D (Refactoring legacy components during deployment) conflates two separate concerns - deployment is not the appropriate time to introduce code changes or risk new regressions.

Memory tip: Think of Cloud Manager as a pipeline manager first - the word "configure" is your signal. If an answer involves skipping, doing things manually, or bundling unrelated work into a deploy, it undermines the whole point of the tool.

No community discussion yet for this question.