Which deployment tasks should be automated using Adobe I/O CLI? (Choose two)

Question

Options

• AManaging pipeline configurations
• BTesting dispatcher cache invalidation rules
• CProvisioning environments
• DGenerating renditions for migrated assets
• EValidating user permissions for staging

• A
  76% (32)
• B
  14% (6)
• D
  2% (1)
• E
  7% (3)

Explanation

Adobe I/O CLI (with the Cloud Manager plugin) is purpose-built for automating Cloud Manager operations - managing pipeline configurations (A) lets you trigger, monitor, and configure pipelines programmatically in CI/CD workflows, while provisioning environments (C) allows you to create and manage AEM Cloud Service environments without manual Admin Console interaction. These two tasks directly align with AIO CLI's Cloud Manager plugin capabilities and are the primary reasons teams adopt it for deployment automation.

Why the distractors are wrong:

• B - Dispatcher cache invalidation testing is handled locally using the Dispatcher SDK tools, not the AIO CLI.
• D - Asset rendition generation is an AEM Assets processing concern (via processing profiles), unrelated to deployment tooling.
• E - User permission validation is managed through the Adobe Admin Console, not automated via AIO CLI.

Memory tip: Think of AIO CLI as your Cloud Manager remote control - it automates the two things Cloud Manager owns: pipelines and environments. Anything touching assets, dispatcher configs, or user access belongs to other tools.

No community discussion yet for this question.