What should be prioritized when preparing a configuration for Asset Microservices?

Question

Options

• AConfiguring custom workflows for metadata updates
• BEnabling synchronous asset replication
• CDefining asset renditions and processing profiles
• DAutomating dispatcher cache invalidation

• A
  12% (2)
• B
  6% (1)
• C
  71% (12)
• D
  12% (2)

Explanation

Defining asset renditions and processing profiles (C) is the foundational step when configuring Asset Microservices because they directly control how uploaded assets are processed - generating thumbnails, web-optimized renditions, and extracting metadata. Without these profiles in place, the microservice pipeline has no instructions for transforming raw assets into usable formats, making all other configuration meaningless.

Why the distractors are wrong:

• A (Custom workflows for metadata updates): Metadata workflows are a secondary concern that builds on top of a working processing pipeline; they are not a prerequisite for the microservices themselves.
• B (Synchronous asset replication): Asset Microservices operate asynchronously by design in cloud-native AEM, so synchronous replication is not a relevant or supported priority in this context.
• D (Automating dispatcher cache invalidation): Cache invalidation is a delivery-layer concern (CDN/Dispatcher), entirely separate from the asset ingestion and processing layer that microservices govern.

Memory tip: Think of processing profiles as the "recipe book" for your microservices - before the kitchen (microservice) can cook anything, it needs recipes (rendition definitions). No recipe = no output.

No community discussion yet for this question.