Developers add a content package module named 'ui.utils' with debugging servlets that should not be deployed to production. What should the DevOps engineer add?

Developers add a content package module named 'ui.utils' with debugging servlets that should not be deployed to production. What should the DevOps engineer add?

• A. Add an element identifying the 'ui.utils' artifact and a matching element to the 'all' package pom.xml with a target path of /apps/mysite-packages/application/install.
• B. Add a dependency element in the 'ui.utils' pom.xml that adds the 'all' to the ui.utils package properties, activated when an env variable is set to a particular value.
• C. Add a pipeline to the CI service that builds the ui.utils content package and uploads it to the Author server's CRX Package Manager servlet after Cloud Manager webhook success.
• D. Exclude the ui.utils module from the build.

Answer: (B)

Controlling what gets packaged based on the environment is the right approach. In AEM DevOps, you want the debugging UI utilities to exist in development or staging builds but not end up in production. The way this is achieved is by making the inclusion of those utilities conditional at build time, rather than altering runtime behavior or relying on separate pipelines. By adding a dependency in the ui.utils module’s POM that brings in the shared “all” package properties only when a specific environment variable is set, you create a build-time gate. When the environment variable indicates a non-production environment, the dependency is activated and the ui.utils content package is assembled with the additional debug servlets. In production, the variable is not set (or set to a value that disables the activation), so the dependency is not included and the debugging servlets aren’t packaged or deployed. This keeps production artifacts lean and avoids deploying debugging functionality, while still allowing easy inclusion for development builds. This approach is preferable to static exclusions or manual steps in CI/CD, because it centralizes environment-specific behavior in the build configuration itself. It also avoids risking production deployment if the gating logic isn’t applied in every pipeline.

Controlling what gets packaged based on the environment is the right approach. In AEM DevOps, you want the debugging UI utilities to exist in development or staging builds but not end up in production. The way this is achieved is by making the inclusion of those utilities conditional at build time, rather than altering runtime behavior or relying on separate pipelines.

By adding a dependency in the ui.utils module’s POM that brings in the shared “all” package properties only when a specific environment variable is set, you create a build-time gate. When the environment variable indicates a non-production environment, the dependency is activated and the ui.utils content package is assembled with the additional debug servlets. In production, the variable is not set (or set to a value that disables the activation), so the dependency is not included and the debugging servlets aren’t packaged or deployed. This keeps production artifacts lean and avoids deploying debugging functionality, while still allowing easy inclusion for development builds.

This approach is preferable to static exclusions or manual steps in CI/CD, because it centralizes environment-specific behavior in the build configuration itself. It also avoids risking production deployment if the gating logic isn’t applied in every pipeline.