AD0-E117 · Question #49
A retail customer with an international presence and both in-store and online sales needs a new assets. The customer's sites will continue to assets platform. The customer decides to use A run on…
The correct answer is C. An AEM Assets setup on Adobe Managed Services with Cloud Manager. Option C is correct because the customer needs a dedicated AEM Assets platform - not a Sites solution - and their websites will remain on a proprietary CMS, so only the DAM (Digital Asset Management) layer is being migrated to AEM. Adobe Managed Services (AMS) with Cloud…
Question
A retail customer with an international presence and both in-store and online sales needs a new assets. The customer's sites will continue to assets platform. The customer decides to use A run on their proprietary CMS for websites. The customer wants to be able to scale the platform for spikes in user traffic such as on local sales or online marketing campaigns. Under some circumstances, the customer also has a higher load of editors for a certain period of time. Which architecture should an Architect use for this business case?
Options
- AAn AEM Publish instance on Adobe Managed Services with auto scaling
- BAn AEM as a Cloud Service Sites with Dynamic Media
- CAn AEM Assets setup on Adobe Managed Services with Cloud Manager
- DAn AEM as a Cloud Service Assets setup using the combined CDN for delivery
How the community answered
(54 responses)- A13% (7)
- B7% (4)
- C56% (30)
- D24% (13)
Explanation
Option C is correct because the customer needs a dedicated AEM Assets platform - not a Sites solution - and their websites will remain on a proprietary CMS, so only the DAM (Digital Asset Management) layer is being migrated to AEM. Adobe Managed Services (AMS) with Cloud Manager is the appropriate fit here because it provides managed infrastructure with configurable scaling policies to handle both spikes in end-user traffic (delivery) and spikes in editor activity (authoring), which are two distinct scaling demands the customer explicitly called out.
Why the distractors are wrong:
- A - AEM Publish on AMS is a Sites/delivery solution, not an Assets platform; it doesn't address the DAM requirement.
- B - AEM as a Cloud Service Sites with Dynamic Media is still Sites-centric; the customer already has a proprietary CMS for their websites and only needs the Assets layer.
- D - AEMaaCS Assets with combined CDN optimizes delivery via CDN but doesn't give the same granular control over author-tier scaling for editor load spikes that AMS + Cloud Manager provides; it also shifts responsibility for scaling away from the customer's control.
Memory tip: Think "C = Control" - when a customer keeps their own CMS and only needs Assets, and they want controllable scaling for both visitors and editors, AMS + Cloud Manager gives them that control. AEMaaCS (option D) auto-scales but is a fully managed SaaS model, which is a different architectural commitment.
Topics
Community Discussion
No community discussion yet for this question.