View AD0-E137 Exam Questions

Q: 1

The customer has a requirement to fetch images from a custom folder (folder1) which were modified on/after 1 January 2024. How would the Adobe Experience Manager Developer write the query to get the requested data?

Options

Discussion

Mason Mar 5, 2026 1:18 pm

B . Only [dam:Asset] will reliably fetch assets (like images) from DAM, and the question says custom folder in DAM. A or C could miss images if they're not using the core asset node type. Pretty sure B is the safest call, but open to other takes if I missed something.

Jordan W. Mar 3, 2026 10:36 am

B tbh. [dam:Asset] targets DAM assets directly, while A could grab non-assets and C uses the wrong node type. Pretty sure B is what AEM expects for images in DAM, but someone correct me if I'm missing any subtlety.

Luke R. Feb 28, 2026 3:09 am

B , matches what I saw in the official doc and labs.

Sara Mar 6, 2026 12:54 pm

B , had this in my exam last year and B was the right structure for AEM DAM assets.

SharpReviewer6306 Mar 9, 2026 5:08 pm

Yeah, B makes sense to me too. [dam:Asset] targets just the DAM image assets, which is what the question wants. A feels too broad since [nt:base] is every node type. Pretty confident with B unless they're using some custom image implementation.

Riley L. Feb 23, 2026 4:45 pm

B , matches dam:Asset which is what AEM usually uses for DAM images.

Jack A. Feb 20, 2026 1:48 pm

Standard DAM setups expect [dam:Asset], so B fits best. But if folder1 stores images under a custom node type, then A or even C could work better depending on that structure. Pretty sure about B unless they've customized the DAM schema.

FriendlyConsultant5446 Mar 10, 2026 7:37 am

B is correct here, using [dam:Asset] matches how AEM structures images in DAM. Option A's [nt:base] is too generic, and C's node type doesn't fit typical DAM image assets. I think B is the safest for standard setups, but let me know if your org uses something custom.

Luna N. Mar 8, 2026 2:19 am

B is the pick, since [dam:Asset] is the core node type AEM uses for DAM images. C won't catch all assets, and A's too generic. Pretty sure about this unless there's some custom node setup not mentioned.

PreciseConsultant6269 Mar 5, 2026 5:23 pm

C tbh, saw a similar question in a practice test where image nodes were referenced like that.

Be respectful. No spam.

Q: 2

What is the default file to store the dispatcher cache configuration?

Options

Discussion

Ava Y. Feb 23, 2026 10:39 am

I don’t think it’s A-XML was used for legacy dispatcher versions, but modern setups use .any by default. B matches the current standard and what’s in the docs for the dispatcher cache config path. C looks like a distractor with the wildcard and different extension. Pretty sure B is correct here, but open to correction if I missed something in a recent release.

IshaanA Mar 4, 2026 2:39 am

A tbh, since I remember older setups using the _cache.xml for dispatcher configs, especially before .any took over as the standard. Maybe I'm stuck in the legacy mindset but XML did come up in some docs. Correct me if I'm off here.

QuietAnalyst9721 Mar 7, 2026 7:13 pm

A is wrong, B fits since the dispatcher’s default config uses _cache.any in the conf.dispatcher.d/cache/ dir. XML used to be a thing on legacy setups but .any is standard now. I think B is it, unless I’m missing something?

PracticalSec2993 Feb 18, 2026 9:35 pm

C or A here

Leaning toward C since I've worked with setups where dispatcher config files use *_cache.config in the directory, especially when teams want to split configs out by env or feature. Also, XML (A) used to be more common on some older installs. Not totally confident but I've seen both in the wild. Anyone else prefer these over .any?

Hannah Feb 26, 2026 1:42 am

C or A I'd go with C because I've seen config files named like *_cache.config in some projects, and it matches the directory layout for dispatcher custom configs. Could also be A if they're expecting XML specifically. Not 100 percent sure, but .any doesn't feel right here.

Skyler Feb 18, 2026 2:02 am

Yeah, B is the one I've always seen as default in most docs and setups. The .any extension is used for dispatcher config files unless they specify something about XML-based configs. Haven't come across a default using XML unless it's a custom setup. If someone has proof of a different default in recent versions, I'd like to see it but pretty sure it's B.

Anita Mar 5, 2026 3:24 am

Not C, that's a trap. B is the default file from what I've seen in recent exam reports.

SteadyDev2594 Mar 6, 2026 8:48 pm

Getting tired of these file extension questions-always mixing up XML and ANY. A

Owen F. Mar 7, 2026 3:50 am

Zoe G. Feb 24, 2026 9:33 am

B , saw a similar question in exam reports and it was _cache.any as default.

Be respectful. No spam.

Q: 3

A developer is managing a common mistake that can lead to performance degradation in AEM development. Which mistake would cause this type of problem?

Options

Discussion

Sam Feb 23, 2026 7:26 am

Option C Lack of indexing slows down repository queries big time in AEM. Official docs and hands-on labs cover this mistake a lot, so worth reviewing those if you're unsure.

Reese W. Feb 21, 2026 6:57 pm

C imo. Not indexing big data in AEM means queries get super slow, seen that flagged on several exam dumps. Static variables can be tricky too but performance suffers most from poor indexing. Open to other views if someone disagrees.

Layla W. Feb 18, 2026 1:36 pm

Rowan F. Feb 25, 2026 5:36 am

Probably B, since using static variables everywhere can lead to memory leaks and weird side effects which might slow things down. Not positive but I see people tripped up by that in AEM projects all the time.

Ryan Feb 24, 2026 4:36 am

B or D? Both of these can impact performance if used badly. I've seen static variables cause weird app state issues in AEM, and overusing synchronized blocks can slow things down with lots of threads. Not sure which hurts more in real world, but B seems pretty plausible for performance drops. Let me know if you disagree.

Luke Mar 6, 2026 3:51 am

Had something like this in a mock recently. C makes sense since not having proper indexing on large datasets in AEM drags query performance way down. Other options can cause issues but not the same hit to speed. Agree with C?

PiyaG Mar 5, 2026 3:25 am

B . Static variables across requests can mess up state and cause memory leaks, pretty common trap for AEM newbies.

Ajay H. Mar 2, 2026 6:16 am

Nice and straightforward wording, C.

Be respectful. No spam.

Q: 4

A developer is using the Oak query engine. Which query language is recommended?

Options

Q: 5

A developer needs to use the mode in Template Editor which allows template authors to define grid settings for different devices. Which mode should the developer use?

Options

Discussion

Sanjay Feb 18, 2026 8:44 pm

A , Structure is easy to mix up here but grid for devices is definitely Layout mode.

Aisha H. Feb 27, 2026 1:19 pm

Yeah, it's A. Layout mode is specifically for adjusting grid settings per device. Structure looks like a trap, but that's more about base components, not responsive grids. I think Adobe really wants you to catch that distinction here. If someone thinks Structure makes sense, let me know.

Amelia K. Feb 18, 2026 8:16 pm

A is what I'd pick since Layout mode in the Template Editor gives you those device-specific grid controls. Structure mode's more about the base components, not actual layout for different screen sizes. Pretty sure on this, but open to arguments if someone thinks otherwise.

Meera Q. Feb 26, 2026 8:56 am

Probably A here, since grid settings for devices points to Layout mode. If it was just "structure" I'd rethink it.

Alex Y. Feb 21, 2026 4:46 pm

Option A

Reese A. Mar 6, 2026 7:38 pm

I'm with A here, since Layout mode is what lets template authors adjust grid settings based on device type. Structure mode is more about the containers and page hierarchy, not the grids themselves. Unless something's different in recent releases, Layout's still the only one for device grids I think. Anyone using a different approach?

Anita X. Feb 24, 2026 3:15 am

Structure looks tempting but that's for managing containers and hierarchy, not grids by device. You want Layout (A) for grid settings per device. Unless Adobe changed something recently, pretty sure that's still how it works. Disagree?

Aisha L. Mar 4, 2026 7:05 pm

A , Structure always trips people up but only Layout mode lets you set device-specific grids.

Neha H. Feb 27, 2026 9:02 pm

A all the way. Layout mode is the only one here that lets template authors pick grid settings for each device type, which is key for responsive design. Pretty confident, but if anyone's seen Structure used this way in Adobe docs let me know.

AdamG Feb 20, 2026 7:03 am

I don't think it's Structure. Pretty sure A is right since only Layout mode lets you change device-specific grids, Structure feels like a trick here. Anyone see it asked differently on practice exams?

Be respectful. No spam.

Q: 6

A customer has the requirement to use SAML authentication on AEM using their SAML 2.0 compatible IDP. Example: AEM: www.wknd.com/content/siteB/index.html IDP: https://www.idpB.com How should an AEM Developer configure their SAML Authentication Handler?

Options

Discussion

Skyler O. Feb 24, 2026 7:19 pm

Option B You really need path and idpUrl to set up SAML auth in AEM, that's what fits standard configs. A is a trap with the assertionConsumerServiceURL, which isn't for IDP targeting. Open to other views but pretty sure it's B.

Morgan Feb 22, 2026 8:39 pm

Its B - config needs path and idpUrl only for basic AEM SAML setup, not assertionConsumerServiceURL or entityId.

NoraH Feb 25, 2026 9:51 am

I think B. You need to set the handler's path for the protected AEM resource and idpUrl to redirect authentication properly, that's standard for SAML in AEM. Option A is a trap because assertionConsumerServiceURL isn't used that way here. Pretty sure B from similar practice, but happy to hear otherwise if someone knows a catch.

Ishaan T. Feb 19, 2026 7:15 am

Yeah, B looks right. SAML handler in AEM needs path for the protected resource and idpUrl for redirecting to the correct identity provider. Saw a similar question in practice tests. I think it's B, agree?

Neha K. Mar 4, 2026 9:10 pm

Its B, the path and idpUrl properties are what you'd set for SAML auth in AEM if the focus is just authentication. If they wanted custom entity IDs or user provisioning, it'd mention that. Pretty sure this matches exam reports but open to other opinions.

Rowan L. Feb 19, 2026 12:09 pm

B, lots of practice tests and the Adobe docs highlight those two parameters for this handler.

Nathan Feb 20, 2026 7:40 pm

Nah, I don't think A is right since userIntermediatePath isn't for handler mapping. It's B, those are the two core params SAML handler uses in AEM. Option A tries to trick you with similar-sounding config.

Emma Feb 23, 2026 4:00 pm

Probably B, since assertionConsumerServiceURL is only valid on the IDP side, not for config on AEM side.

Robin Mar 3, 2026 7:59 pm

Which official AEM docs or practice test covers SAML handler property mapping best for this scenario? I remember something in the admin guide but not sure which page is most up to date on config properties.

Layla G. Feb 25, 2026 6:22 am

I don't think it's A. B matches standard SAML setup for AEM, since assertionConsumerServiceURL is just a distractor here.

Be respectful. No spam.

Q: 7

A client wants to ensure that only specific components are available to content authors when using an editable template in AEM. Additionally, they require that certain fields within a content fragment model adhere to strict validation rules for data integrity. Which two steps would the developer take to meet both requirements? (Choose two.)

Options

Discussion

SteadyTester5437 Mar 5, 2026 11:13 am

B/E? A is tempting but field validation isn't actually in editable templates. B and E fit what the question asks.

Layla Mar 7, 2026 3:35 pm

Nice catch on B and E. You need policies in the editable template to restrict which components show up (that's E), and content fragment models have their own validation configs (that's B). The others don't really fit those needs. Pretty sure that's how it's done, but open if someone has a different approach.

Rowan N. Feb 27, 2026 4:35 pm

I thought A, editable templates seem like they should cover field validation directly too. Trap answer maybe?

Sara Mar 2, 2026 7:19 pm

Jason K. Feb 19, 2026 11:30 am

Makes sense to pick B and E here. Templates control allowed components (E), and field validation is handled in the content fragment model (B). Not 100% but that's how I read it, open to other takes.

Nathan I. Mar 3, 2026 4:41 pm

B and E imo. Editable template policies (E) let you lock down which components show for authors, and for validation, that has to be set in the content fragment model itself (B), not the template. Other options don't actually enforce those requirements. Pretty sure that's right, correct me if I've missed something.

Quinn Q. Mar 6, 2026 11:11 pm

I'm not sure about B for validations. Wouldn't A handle field validation rules directly in the editable template? I might be missing something with content fragment models though. Can someone clarify?

Aisha T. Mar 4, 2026 2:21 am

B and E make the most sense. From what I remember, field validation has to be set up directly in the content fragment model (so B). For limiting components on editable templates, you define policies (E). Saw a similar question in an exam report. Not 100% sure if workflow (C) could help, but pretty sure it's not the main way. Agree?

Cameron I. Feb 28, 2026 3:34 am

B and E tbh. Only policies on editable templates (E) limit components for authors, while field validation needs to be set in the fragment model itself (B). Trap here is thinking editable templates can handle validation-can't. Seen this come up before, but let me know if I missed something.

Casey S. Feb 24, 2026 10:46 pm

For the part about field validation in content fragment models, why not A? Doesn't editable templates touch validation at all?

Be respectful. No spam.

Q: 8

A developer is creating a set of SPA components, half of which do not require a custom component exporter. The developer needs to override the default exporter for the remaining components. How can the developer meet this goal?

Options

Discussion

KevinC Mar 10, 2026 8:54 am

B , since ComponentExporter lets you set a custom exporter just for the components that need it. A would be overkill for the question as written. Pretty sure that's what Adobe expects here!

Mason X. Feb 19, 2026 10:46 pm

Option B works here. ComponentExporter lets you override the default for specific SPA components, just like the question says. ImplementationPicker (A) is for broader use, not per-component overrides. Seen similar in practice sets, but let me know if anyone found exceptions.

QuietOps1702 Feb 28, 2026 10:02 am

B seen similar wording on practice. Only need to override for some components so ComponentExporter service fits.

Nora W. Feb 27, 2026 2:30 pm

It’s A, this question is so poorly worded on the official exam. Seen similar in other dumps too.

Piya C. Mar 7, 2026 8:58 am

B , ComponentExporter is what you use when you need to override the default exporter for SPA components in AEM. The other options don't deal with export logic. There's a trap with A since ImplementationPicker sounds generic, but it's not for this use case. Pretty sure it's B based on exam practice and Adobe docs.

Parker H. Mar 1, 2026 4:51 pm

Is there any official Adobe doc that clearly shows why B is preferred over A for per-component exporter overrides? Official guide or hands-on labs might help clarify the logic here.

Cameron Mar 3, 2026 12:53 am

Probably B

Jack Mar 3, 2026 8:15 am

Its B here. A is tempting but that's for global logic, not per-component overrides like the question wants.

Quinn Z. Mar 1, 2026 11:59 pm

Had something like this in a mock, pretty sure B is spot on. ComponentExporter lets you override exporters per component, exactly what's needed here instead of a global override. Agree with other posts here.

Nora K. Mar 1, 2026 4:24 am

Not A, it's B. ImplementationPicker is a trap since it's not for SPA component exporter overrides.

Be respectful. No spam.

Q: 9

What is the role of the "Retry Delay" setting in an AEM replication agent's configuration?

Options

Discussion

Luke U. Mar 4, 2026 4:03 pm

A. not D. D tricks you because of the queue mention, but Retry Delay is just for how often failures get another shot. Seen this phrasing on practice sets a few times.

ThoughtfulReviewer1009 Feb 18, 2026 7:44 am

C/D? D looks tempting with queue language, but pretty sure A is the actual behavior for Retry Delay. I've seen similar practice questions where D was a trap because the delay only covers retries after failure, not queue processing. Correct me if I'm missing something though.

Mia A. Feb 25, 2026 8:38 am

Nah, it's A. The "Retry Delay" is specifically how long AEM waits before trying again after a replication failure. D can sound right if you focus on the queue, but that's actually a separate interval setting. Seen this catch people on practice exams.

Reese U. Mar 7, 2026 6:48 pm

Option A. since retry delay only affects how often failed replications are attempted again. D is a common trap, that’s the queue interval not retry logic.

Layla Z. Mar 6, 2026 2:46 am

Its A, but does "Retry Delay" act differently if the replication agent is set to 'On Modification' vs scheduled? I think that would change how B or D might apply.

Luna A. Feb 21, 2026 3:01 pm

C or D but pretty sure it's A in this context since queue interval is different.

Ivy J. Feb 28, 2026 1:15 pm

A tbh

ChrisU Feb 22, 2026 5:20 am

A , D keeps tricking people but it's about failed replications not the queue timer.

FriendlyAuditor9950 Mar 1, 2026 10:44 am

RyanP Feb 25, 2026 11:32 pm

A , that's all Retry Delay handles. It's about how often AEM retries failed replication jobs, not queue intervals or marking failures. Seen this tripping folks up before since the wording on D sounds similar. If anyone's seen a case where it's not A let me know but I'm pretty sure here.

Be respectful. No spam.

Q: 10

A developer is required to create a package with these requirements: Package Name: aem-package Content Path: /content/aem-site Version: 1.0 Group: aem_group What is the correct zip package file created in Adobe Experience Manager package manager?

Options

Discussion

Grace G. Feb 19, 2026 6:52 am

Option C. since packageName-version.zip is what I've used before in some AEM projects. Trap might be with the group field.

Leo I. Feb 24, 2026 2:58 am

I thought it was C because in my projects the zip just uses the package name and version. Didn't realize AEM requires the group in the filename for uniqueness. Maybe I'm mixing up with older versions, correct me if I'm off here.

Nathan P. Feb 28, 2026 12:49 am

C is missing the group in the filename so that's a common trap, but it's A.

Sara L. Mar 10, 2026 6:43 am

D imo

Jason Mar 10, 2026 9:17 am

Had almost this exact scenario in a mock test. For questions with the group provided, A is what you'd get from the package manager output. C would only apply if there was no group. Pretty sure it's A here, but open to being corrected.

Alex Feb 22, 2026 11:00 pm

Group name's required so why would C be right here? Isn't A the correct zip package?

Priya Feb 25, 2026 5:34 pm

Yeah A is correct. Current AEM package manager includes the group in the filename for uniqueness, so you get packageName-group-version.zip. C is what you’d see if there was no group but here it’s clearly listed. Pretty sure this matches the up-to-date approach, unless Adobe changes it in the future.

Sean O. Mar 7, 2026 6:39 am

A/C? Normally it's A (packageName-group-version.zip) since the group helps keep packages unique in AEM. But if you use old versions or skip group, C could happen. I think A for latest, correct me if not.

Leo G. Mar 5, 2026 12:20 pm

Yeah, A makes sense since AEM package filenames are usually structured as packageName-group-version.zip. The group is used for uniqueness and organizing packages. Pretty sure that's standard now, though maybe older projects did it differently. Do you guys remember if this changed in more recent AEM updates?

Cameron B. Mar 6, 2026 4:39 am

Its A, but if the group is omitted then C might fit, rare edge case though.

Be respectful. No spam.

Question 1 of 20 · Page 1 / 2

Premium Access Includes

✓ Quiz Simulator
✓ Exam Mode
✓ Progress Tracking
✓ Question Saving
✓ Flash Cards
✓ Drag & Drops
✓ 3 Months Access
✓ PDF Downloads

Get Premium Access

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE