Which activities are supported by setting up local SDKs for AEM as a Cloud Service? (Choose two)

Question

Options

• ALocal testing of AEM components
• BMigrating content directly to the cloud
• CValidating dispatcher cache invalidation rules
• DRunning workflows in a local environment
• EConfiguring metadata extraction for assets

• A
  74% (23)
• B
  6% (2)
• C
  16% (5)
• E
  3% (1)

Explanation

Setting up local SDKs for AEM as a Cloud Service enables developers to build, test, and debug AEM components locally before deploying to the cloud (A), and to run and test workflows in a local environment without needing cloud access (D) - both are core development activities the local SDK is explicitly designed to support.

Why the distractors are wrong:

• B - Content migration to the cloud uses tools like the Content Transfer Tool, not the local SDK setup.
• C - Dispatcher cache invalidation rules are validated using the Dispatcher Tools (a separate component), not simply by setting up the local SDK.
• E - Metadata extraction for assets is a cloud-side pipeline configuration concern, not a local SDK activity.

Memory tip: Think of the local SDK as a developer sandbox - it exists to let you write and test code (components = A, workflows = D). Anything involving moving data to the cloud, cloud-side caching rules, or asset processing pipelines happens outside that sandbox.

No community discussion yet for this question.