AD0-E117 · Question #14
An existing AEM sites platform will receive the latest service pack. The service pack includes functional and non-functional fixes such as security patches. Which action should the Architect take to…
The correct answer is C. Identify the packages affected by the service pack after installing them into production and monitor. There appears to be an error in this question - the marked correct answer (C) conflicts with AEM best practices, and D is actually the correct answer. Option C describes installing the service pack directly into production first and only then monitoring - this is backwards and…
Question
An existing AEM sites platform will receive the latest service pack. The service pack includes functional and non-functional fixes such as security patches. Which action should the Architect take to make sure the update is successful?
Options
- AAdvise the customer to request Adobe to install the fixes directly on production since they are
- BInstall the service pack m staging and ensure that all the bundles are up and running, then deploy
- CIdentify the packages affected by the service pack after installing them into production and monitor
- DDo a full staging of the service pack including a regression test, if passed, deploy to production.
How the community answered
(29 responses)- A10% (3)
- B7% (2)
- C79% (23)
- D3% (1)
Explanation
There appears to be an error in this question - the marked correct answer (C) conflicts with AEM best practices, and D is actually the correct answer.
Option C describes installing the service pack directly into production first and only then monitoring - this is backwards and dangerous, as it skips the entire pre-validation stage and exposes a live environment to untested changes.
D is correct because AEM update methodology always follows a promote-through-environments model: apply the service pack to a full staging environment, run regression tests to catch regressions introduced by the functional/security fixes, and only promote to production after a clean pass. This protects the live site from breaking changes.
Why the distractors fail:
- A is wrong because Adobe does not manage on-premise/managed installations on the customer's behalf, and going straight to production is never acceptable.
- B is partially right (staging is involved) but only checks that OSGi bundles are active - it skips regression testing, which is critical for service packs that touch core functionality.
- C installs into production before validating, which is the opposite of safe change management.
Memory tip: Think "Stage before Stage" - Staging environment + Regression testing before any production touch. Service packs are not hotfixes; they require full regression coverage because they bundle multiple changes across functional and security domains.
Double-check your source material - if this is from an official Adobe exam bank, C may be a typo for D.
Topics
Community Discussion
No community discussion yet for this question.