What are the key steps in configuring Cloud Manager pipelines? (Choose three)

Question

Options

• ASetting up build triggers
• BEnabling automated testing processes
• CManually deploying changes to staging
• DConfiguring approval gates for deployment
• EIntegrating dispatcher invalidation scripts

• A
  77% (46)
• C
  15% (9)
• E
  8% (5)

Explanation

Configuring Cloud Manager pipelines centers on automation and governance: build triggers (A) define when pipeline execution starts (e.g., on code commits), automated testing (B) validates code quality at each stage without manual intervention, and approval gates (D) enforce controlled promotion between environments by requiring human sign-off before deployment proceeds. Together, these three form the core pipeline lifecycle - trigger, validate, govern.

Why the distractors are wrong:

• C (manually deploying to staging) contradicts the purpose of a CI/CD pipeline, which automates deployments rather than relying on manual steps.
• E (dispatcher invalidation scripts) relates to AEM cache management post-deployment, not pipeline configuration itself - it's an integration concern, not a pipeline setup step.

Memory tip: Think "TVG" - Trigger, Validate, Gate. A pipeline doesn't exist without something to start it (trigger), something to verify it (testing), and something to control where it goes (approval gate). If an answer is about manual action or post-deploy cache behavior, it's outside this core pattern.

No community discussion yet for this question.