Latest [Aug 27, 2026] 100% Passing Guarantee – Brilliant AD0-E124 Exam Questions PDF [Q37-Q57]

AD0-E124 Adobe

admin • August 27, 2026

Latest [Aug 27, 2026] 100% Passing Guarantee – Brilliant AD0-E124 Exam Questions PDF [Q37-Q57]

Rate this post

Latest [Aug 27, 2026] 100% Passing Guarantee – Brilliant AD0-E124 Exam Questions PDF

AD0-E124 Certification – Valid Exam Dumps Questions Study Guide! (Updated 172 Questions)

NO.37 A developer creates a new multi-module Maven project and needs to create a Maven module for storing run-mode configurations.
Which packageType should the DevOps engineer instruct the developer to use?

container

application

content

Use the “core” package type for run-mode configurations.

NO.38 Which Adobe service allows integration of Cloud Manager with third-party APIs?

AEM Replication Agents

Adobe I/O Runtime

Cloud Manager Deployment Manager

Dispatcher Configuration Manager

NO.39 A DevOps engineer must upload SSL certificates for multiple domains to Cloud Manager via the UI. Which two certificate formats can the DevOps engineer use? (Choose two.)

Wildcard certificate

SAN certificate

PKCS certificate

Single certificate for each domain

To secure multiple domains or subdomains efficiently using a single certificate upload in Adobe Cloud Manager, DevOps engineers should use either a SAN (Subject Alternative Name) certificate or a Wildcard certificate. A SAN certificate allows multiple distinct hostnames (e.g., example.com, shop.example.com, example.org) to be protected by a single certificate. A Wildcard certificate (e.g., *.example.com) protects a single domain and all its subdomains. Both are officially supported in the Cloud Manager UI for SSL deployment.

NO.40 An html page is published and is accessible through the dispatcher. A client is trying to access the updated page but is not getting the updated content.
A rule /type “allow” /glob “*.html” is present in the dispatcher /cache /rules configuration The HTTP header “Cache-Control: max-age=3600” is set for all requests with the html extension The /invalidate section is not set in the dispatcher configuration A flush agent is configured on the publish instance A CDN is serving all static content including html files and was flushed manually Why does the content fail to update on the client side?

The file was cached on the client side in the browser cache.

The flush occurred before the content was replicated because there are a lot of items in the queue.

The content is still cached in the dispatcher after the CDN flush.

There is no /invalidate section present in the dispatcher configuration to invalidate the updated content.

NO.41 A Cloud Manager pipeline deployment fails due to a missing dependency.
What is the best approach to resolve this issue?

Check and update the pom.xml to ensure the dependency is correctly referenced

Remove all dependencies and rebuild the project

Disable the dependency check and force the deployment

Manually add the missing JAR file to the AEM instance

NO.42 A DevOps engineer needs to configure SAML on an AEM author instance.
Which items does the DevOps engineer need from the Identity Provider (IdP)?

IdP certificate, ServiceEntity ID, IdP URL

SSL certificate, ServiceEntity ID, IdP URL

IdP PrivateKey, ServiceEntity ID, IdP URL

Use an IdP-generated username instead of the IdP certificate

NO.43 In the Security Checks report, status for CRXDe Support is set to WARN.
Which steps should be taken to change the status for CRXDe Support to OK?

Stop Apache Sling Simple WebDAV Access to repositories (org.apache.sling.jcr.webdav) bundle

Uninstall Adobe CRXDE Support, Adobe Granite CRX Explorer, and Adobe Granite CRXDE Lite bundles

Stop Apache Sling DavEx Access to repositories (org.apache.sling.jcr.davex) bundle

Uninstall Apache Sling Tooling Support Install((org.apache.sling.tooling.support.install) bundle

NO.44 An enterprise customer of AEM as a Cloud Service has three independent development teams. Each team is responsible for publishing a different website with a unique domain and SSL certificate to the single, shared AEM program.
Each team has set their own project timeline with a different launch date planned within the next 6 months.
Each team has their own upstream Git repository hosted in the corporate subnet, which they initialized using the latest aem-project-archetype.
The DevOps engineer is solely responsible for any configurations needed to enable automated deployment to all three environments (dev, stage, and prod).
Which two options should the DevOps engineer choose? (Choose two.)

A fourth Git repository that contains a root pom file and a CI/CD pipeline script cloning the other three project repositories as subfolders

A multi-module Maven project that embeds each team’s Git repository as a module of the encompassing Maven project

Three separate Cloud Service programs and Cloud Manager Developer/Deployment Manager role assignments for each of the three team leads

Use Git submodules in Cloud Manager to merge the content of multiple branches across git repositories at build time

NO.45 A developer creates a new git branch for a feature that is being developed on AEM as a Cloud Service. The developer asks the DevOps engineer to establish an automated deployment to occur every 4 hours only.
What should the DevOps engineer do?

Set up a cron job to call Adobe I/O CLI every 4 hours.

Write a git commit hook to call Adobe I/O CLI every 4 hours.

Set up a cron job to push a git commit every 4 hours.

Schedule a pipeline in the Cloud Manager UI to run every 4 hours.

Cloud Manager UI pipelines are typically triggered manually or automatically “On Git Changes” (commits).
Out-of-the-box, the Cloud Manager UI does not provide a native way to configure an exact, repeating chronological schedule (like “every 4 hours”) that runs independently of code commits. To achieve this specific time-based requirement, the DevOps engineer must use an external cron job or scheduling system to invoke the Cloud Manager API programmatically. This is done by authenticating via Adobe I/O and using the Adobe I/O CLI (e.g., aio cloudmanager:pipeline:create-execution) to trigger the deployment pipeline every 4 hours.

NO.46 Which key elements must be configured in Cloud Manager to enable a successful deployment? (Choose three)

Pipeline triggers and scheduling

User permissions and access control

Deployment logs and monitoring

Manual content sync between author and publish instances

Custom replication agents for deployment

NO.47 A website experiences slow page loads despite enabling caching in Dispatcher.
What is the best approach to troubleshoot the issue?

Analyze the Dispatcher logs to check cache hit/miss rates

Disable caching completely to check if performance improves

Increase the AEM instance memory allocation

Configure replication agents to force content updates

NO.48 During the Non-Production pipeline, an issue occurs with a Security Rating of B.
Based on the Review Results, all critical and mandatory tests passed.
What should the DevOps engineer do to proceed with the build?

Switch on Override failed results and submit.

Bypass testing for security and proceed to performance.

Reject the deployment and restart it again.

Reconfigure the pipeline to pull from another branch.

Similar to Code Coverage, a Security Rating of ‘B’ in Cloud Manager usually results in a “Partial Pass” state (3-tier rating system where critical vulnerabilities cause outright failures, but lower-tier warnings cause partial passes). Since all critical and mandatory tests passed, the pipeline pauses and waits for user intervention. The DevOps engineer (with the Deployment Manager role) can proceed with the build by navigating to the execution details, selecting the option to “Override failed results,” and submitting the decision to resume the pipeline.

NO.49 The DevOps engineer is defining a new project setup in AEM as a Cloud Service. The initial setup for Maven Profiles is done by the development team.
The test is to check where the build is running and provide a statement. The build needs to be run within AEM as a Cloud Service and on Stage to see where the build was executed.
The expected test output was not observed during the most recent pipeline run.
&lt;profile&gt;
&lt;id&gt;CMBuild&lt;/id&gt;
&lt;activation&gt;
&lt;property&gt;
&lt;name&gt;!env.CM_BUILD&lt;/name&gt;
&lt;/property&gt;
&lt;/activation&gt;
&lt;build&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
&lt;version&gt;1.8&lt;/version&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;initialize&lt;/phase&gt;
&lt;configuration&gt;
&lt;target&gt;
&lt;echo&gt;I’m running inside Cloud Manager!&lt;/echo&gt;
&lt;/target&gt;
&lt;/configuration&gt;
&lt;goals&gt;
&lt;goal&gt;run&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/build&gt;
&lt;/profile&gt;
What must the DevOps engineer do?

Change
<name>!env.CM_BUILD</name>
to
<name>env.CM_BUILD</name>

Change
<name>!env.CM_BUILD</name>
to
<name>STAGE.CM_BUILD</name>

Configure the STAGE environment via the Cloud Manager API using the CLI to run if ( STARTED === event[“@type”] &amp;&amp; EXECUTION === event[“xdmEventEnvelope:objectType”] ) { console.log(`I’m running inside Cloud Manager!`);
}

Replace the Maven profile with a different plugin configuration.

NO.50 A DevOps engineer notices that the Online Revision Garbage collection is not running as part of the daily maintenance tasks. After inspecting the server’s error log, the following shows up during the maintenance schedule:
“Revision GC will not run: Size delta is N% or N/N (N/N bytes), so skipping compaction for now” The DevOps engineer needs to make sure that the revision garbage collection runs during the scheduled maintenance task. Which additional step should the DevOps engineer take?

Set full compaction schedule property for com.adobe.granite.maintenance.crx.impl.
RevisionCleanupTask to a preferred day.

Disable the estimation phase in the Apache Jackrabbit Oak segment-Tar Nodestore Factory.

Invoke startRevisionGC() for SegmentRevisionGarbageCollection MBean in the JMX console.

Increase the size of the TarMK segment files.

The Oak Segment NodeStore (TarMK) includes an “estimation phase” before running Revision Garbage Collection (Compaction). This phase calculates if enough “garbage” (unreferenced data) has accumulated to justify the heavy I/O cost of compaction. If the size delta doesn’t meet the threshold, it skips the process to save resources. If a DevOps engineer must force the compaction to run regardless of the delta, they must configure the OSGi configuration for the “Apache Jackrabbit Oak Segment NodeStore Service” and disable the “Estimation Phase” by unchecking/toggling the appropriate property.

NO.51 The project builds and deploys successfully on a local environment. A DevOps engineer deploys the same project source code on an AEM as a Cloud Service Non-Production pipeline. The pipeline fails at the Build & Unit Testing stage.
The end of the build_maven_build.log shows the following log messages:
[INFO] SITS Sites Project – Project Analyser …………… FAILURE
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.1:single (default) project aem-kit-sits.analyse: Failed to create assembly: Error creating assembly archive distribution: archive cannot be empty The non-production pipeline was run once more, and the build failed at the same step with the same errors in the build log file. How should the DevOps engineer resolve this issue?

Update the AEM Analyzer to the latest version in the main pom.xml.

Update the Maven Assembly Plugin to the latest version in the main pom.xml.

Check if all OSGi bundles have their Import-Package(s) declared and add any that are missing.

Reconfigure the analyzer plugin to ignore the assembly phase.

AEM as a Cloud Service enforces strict architectural rules analyzed by the aemanalyser-maven-plugin. This analyzer scans the compiled project to ensure it is compliant with cloud standards. If a custom OSGi bundle relies on external Java packages but fails to explicitly declare them in the Import-Package section of its manifest (often managed by the bnd-maven-plugin), the analyzer feature model validation will fail. This failure frequently manifests as a downstream assembly error where the analyzer’s output archive is empty because it crashed during bundle inspection. Resolving the missing Import-Package headers fixes the analyzer model creation.

NO.52 Which actions can be performed using the Cloud Manager API? (Choose two)

Retrieve pipeline execution logs

Manually trigger a code deployment

Enable real-time dispatcher rule updates

NO.53 A DevOps engineer receives a report from users that some content pages take a long time to load on their AEM Managed Services Production instance. The DevOps engineer decides to confirm that this behavior is occurring before taking action.
What should the DevOps engineer investigate?

Query Performance via the Diagnosis Tools

Requests via the Web Console

Request Performance via the Diagnosis Tools

Requests via the access.log

To verify and analyze slow-loading pages in AEM, the correct tool is “Request Performance” located under the Diagnosis Tools (accessible via the AEM Web Console / Operations Dashboard). This tool tracks incoming HTTP requests to the AEM instance, breaks down the execution time of the request across various internal components and scripts, and allows the DevOps engineer to pinpoint exactly which part of the page rendering is causing the delay. Query Performance (Option A) is specifically for slow JCR searches, not necessarily overall page load times.

NO.54 Which actions help identify bottlenecks affecting AEM performance? (Choose two)

Analyzing request latency using Cloud Manager metrics

Increasing the number of publish instances without checking load balancer settings

Reviewing logs for long-running queries

Modifying the sling.properties file to boost performance

NO.55 After deploying a new version of an AEM site, users report slow page load times.
What should be checked first?

Dispatcher cache settings and invalidation rules

OSGi component logs for errors

The number of active workflows running in AEM

CRX repository size and index settings

NO.56 A DevOps engineer is supporting a client on Adobe Managed Services. The setup will be migrated to AEM as a Cloud Service.
Which two methods can be applied for scaling publish instances on the current platform? (Choose two.)

Manual scaling via Cloud Manager horizontally

Manual scaling via the Adobe I/O CLI vertically

Auto scaling via Cloud Manager vertically

Auto scaling via Cloud Manager horizontally

Manual scaling via CSE horizontally

This question draws a technical comparison between how scaling works on the legacy Adobe Managed Services (AMS) platform versus the target AEM as a Cloud Service (AEMaaCS) platform. On the current legacy AMS platform, horizontal scaling (adding more instances) requires submitting a ticket to a Customer Success Engineer (CSE) to provision and attach new VMs manually (Option E). By contrast, on AEM as a Cloud Service, publish instances scale automatically (Auto scaling) horizontally via Cloud Manager based on live traffic thresholds, or can be scaled via Cloud Manager logic (Option A represents the target platform’s cloud-native scaling methodology, though standard AEMaaCS implies Auto scaling; Cloud Manager orchestrates this).

NO.57 During security tests, it becomes apparent that AEM-specific paths were accessible on the publish instance. These paths should not be accessible to the public.
Which configuration should be used on a publish dispatcher instance?

/0001 { /type “deny” /glob “/system/*”}

/0001 { /type “deny” /url “/crx/*”}

/0001 { /type “deny” /glob “*”}

/0001 { /type “deny” /url “/system/*”}

Loading …