Free Preparation Discussions
MENU
Adobe AD0-E134 Exam Questions
- Topic 1: Determine the correct steps to configure OOTB SAML and LDAP integration/ Determine the approach to implement a headless or hybrid implementation
- Topic 2: Given a scenario, determine the correct steps to develop workflows/ Recommend and implement solutions to sync content/configurations across AEM environments
- Topic 3: Determine the correct method to create unit tests and map mock data/ Given a scenario, determine the correct method to Create and manage custom OAK indices
- Topic 4: Given a design, create custom components including the HTL, models, and services/ Given a scenario, determine the steps required to manage AEM environments
- Topic 5: Given a scenario, determine the approach for any third-party integration/ Identify the steps to create and manage AEM dispatcher configurations
- Topic 6: Determine the correct steps to implement SPA structure, templates, and components/ Identify the steps to set-up and maintain front-end and back-end dependency management
- Topic 7: Determine the correct archetype when building projects/ Explain how to create and manage OSGi configurations
- Topic 8: Determine the correct steps to configure multi-tenancy/ Explain the setup steps around release management
Free Adobe AD0-E134 Exam Actual Questions
Note: Premium Questions for AD0-E134 were last updated On May. 07, 2026 (see below)
Which practice should be used to push a code fix to make it into the current release candidate?
To push a code fix into the current release candidate, the best practice is to cherry-pick the fix commit into the release candidate branch. Cherry-picking allows you to apply specific changes from one branch to another, ensuring that only the necessary fixes are included without introducing unrelated changes.
Here's how to cherry-pick a commit:
Identify the Commit: Locate the commit hash of the fix you need to apply. This can be found in your version control system (e.g., Git).
Checkout the Release Candidate Branch:
git checkout release-candidate-branch
Cherry-pick the Commit:
git cherry-pick <commit-hash>
Resolve Conflicts (if any): If there are conflicts, resolve them manually and then continue the cherry-pick process:
git add <resolved-files>
git cherry-pick --continue
Test the Changes: Ensure that the changes are tested thoroughly in the release candidate environment to confirm the fix works as expected.
Push the Changes:
git push origin release-candidate-branch
Cherry-picking ensures that only the required changes are applied to the release candidate, maintaining the stability and integrity of the codebase.
Git Cherry-pick Documentation
Which attribute must be present in all filter rules in AEM dispatcher configuration?
The /glob attribute is mandatory for all filter rules in the dispatcher configuration. It specifies a pattern that is matched against the incoming request URL. If the pattern matches, the rule is applied. The /glob attribute can use wildcards (*) and placeholders ($1, $2, etc.) to match parts of the URL. Reference: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#filter-rules
A developer is working on a project based on core components. The client requests that text pasted inside the Text component should be stripped of all styling and formatting.
The developer needs to override RTE plugin implementation and change the default paste (CTRL+V) behavior.
Which paste option should the developer add to achieve this?
To ensure that text pasted inside the Text component in AEM is stripped of all styling and formatting, you need to override the RTE (Rich Text Editor) plugin implementation and change the default paste behavior. The correct option to achieve this is defaultPasteMode=plaintext.
Steps to configure the RTE plugin for plain text pasting:
Locate the RTE Configuration: Find the existing configuration for the RTE or create a new one in the /apps directory of your AEM project.
Modify the Plugin Configuration: Add or update the configuration to include the defaultPasteMode parameter. The configuration might look something like this:
{
'jcr:primaryType': 'nt:unstructured',
'features': '[text]',
'defaultPasteMode': 'plaintext'
}
Apply the Configuration: Ensure that this configuration is applied to the Text component. This typically involves updating the component dialog or design dialog to reference the updated RTE configuration.
Test the Configuration: In the AEM author instance, open the page with the Text component and paste text using CTRL+V. The pasted text should now be stripped of all styling and formatting, adhering to the plaintext mode.
By setting defaultPasteMode to plaintext, you ensure that the RTE only accepts plain text input, removing any formatting that might come from external sources.
AEM Rich Text Editor (RTE) Documentation
Configuring the Rich Text Editor in AEM
Where should an AEM Developer add a front end dependency?
An AEM Developer should add a front-end dependency in the package.json file. The package.json file is a standard configuration file for managing dependencies in JavaScript projects, including those using npm or Yarn as package managers.
Here's how to add a front-end dependency:
Open the package.json File: This file is typically located at the root of your project.
Add the Dependency: Add the required front-end dependency under the dependencies or devDependencies section. For example, to add lodash as a dependency:
{
'name': 'my-aem-project',
'version': '1.0.0',
'dependencies': {
'lodash': '^4.17.21'
}
}
Install the Dependency: Run the following command to install the new dependency:
npm install
Verify Installation: Ensure that the dependency has been added to the node_modules directory and is listed in the package-lock.json file.
The package.json file is the central place to manage all front-end dependencies, making it easy to track, update, and share dependencies across the development team.
npm Documentation
Managing Dependencies in AEM Projects
These steps ensure that the front-end dependencies are managed efficiently and consistently within the AEM project.
A developer needs to create a new Title component. The requirements are:
1. The layout must be the same as the Title core component
2. The text property must have the page title as prefix (e.g., Page Title -
3. The component must be reusable
Which approach is recommended?
A proxy component is a site-specific component that inherits from a core component and allows customization of the component name, group, dialog, and behavior. A proxy component can refer to any version of the core component by changing the sling:resourceSuperType property. A custom sling model can be used to implement the logic for adding the page title as prefix to the text property. A component template can be used to define the layout of the component.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Robert Hernandez
10 days agoBrian Nguyen
21 hours agoAngela Garcia
1 day agoJames Martin
3 days agoJason Johnson
6 days agoKaren Martin
7 days agoCharisse
25 days agoChrista
1 month agoChantell
1 month agoCarli
2 months agoIrene
2 months agoMarisha
2 months agoEttie
2 months agoPearly
3 months agoQueen
3 months agoOnita
3 months agoFrank
3 months agoHuey
4 months agoHillary
4 months agoLeonard
4 months agoLouis
4 months agoSherman
5 months agoMarti
5 months agoCatalina
5 months agoErasmo
5 months agoAfton
6 months agoVinnie
6 months agoStephanie
6 months agoDestiny
6 months agoJestine
7 months agoMariko
7 months agoEloisa
7 months agoAdell
7 months agoFrancene
8 months agoLucille
8 months agoSommer
10 months agoTamala
10 months agoMarla
11 months agoAllene
11 months agoJeanice
1 year agoYun
1 year agoVenita
1 year agoRickie
1 year agoJestine
1 year agoIsidra
1 year agoLatosha
1 year agoStefan
1 year agoAnnamae
1 year agoKaycee
1 year agoJustine
1 year agoLisbeth
1 year agoMicheline
1 year agoTamar
1 year agoMy
1 year agoKenneth
1 year agoSanjuana
1 year agoEzekiel
1 year agoDewitt
1 year agoGolda
1 year agoEdna
1 year agoNan
1 year agoEzekiel
2 years agoJutta
2 years agoEric
2 years agoMarti
2 years agoCristy
2 years agoShad
2 years agoQuiana
2 years agoGeoffrey
2 years agoShawnda
2 years agoGracia
2 years agoChristiane
2 years agoLinsey
2 years agoVerona
2 years agoGilberto
2 years agoJohnna
2 years agoShelton
2 years agoLilli
2 years agoGerman
2 years agoBurma
2 years ago