Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E134 Exam - Topic 3 Question 56 Discussion

A developer is using sling context-aware configuration trying to get the configuration resource using:This works as intended in author and in publish when logged in lo publish as admin. However this gives a null when run as anonymous. Which method is going to fix the issue?
A) Applying read permissions to anonymous user for /content directory
B) Applying write permissions to anonymous user for/conf directory.
C) Applying read permissions to anonymous user for /etc directory.
D) Applying read permissions to anonymous user for /cont directory

Adobe AD0-E134 Exam - Topic 3 Question 56 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 56
Topic #: 3
[All AD0-E134 Questions]

A developer is using sling context-aware configuration trying to get the configuration resource using:

This works as intended in author and in publish when logged in lo publish as admin. However this gives a null when run as anonymous. Which method is going to fix the issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

The issue arises because the anonymous user does not have the necessary read permissions for the /content directory. When using Sling context-aware configurations, access to the configuration resource is required. If the anonymous user lacks read permissions, the configuration cannot be retrieved, resulting in a null value.

To fix this issue, you need to grant read permissions to the anonymous user for the /content directory.

Steps to apply read permissions:

Access CRXDE Lite: Log into your AEM instance and navigate to CRXDE Lite (http://localhost:4502/crx/de).

Navigate to the /content Directory: In the CRXDE Lite interface, browse to the /content directory.

Set Permissions:

Right-click on the /content directory and select 'Permissions'.

Add the anonymous user (if not already present).

Grant read permissions to the anonymous user.

Save Changes: Apply the changes and ensure that they are saved correctly.

Test the Configuration: Log out of the AEM instance and test the context-aware configuration as an anonymous user to ensure that the configuration resource can now be retrieved.

By granting read permissions to the anonymous user for the /content directory, you allow access to the necessary configuration resources, resolving the issue.


Adobe Experience Manager Security Permissions

by Joesph at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium AD0-E134 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Trinidad
3 months ago
D seems wrong. /cont isn’t a standard path. A or C feels right.
upvoted 0 times
...
Cathern
3 months ago
I’m leaning towards C. /etc is often where configs are stored.
upvoted 0 times
...
Victor
4 months ago
I think option A makes sense. Read permissions for /content should help.
upvoted 0 times
...
Solange
4 months ago
This question is tricky. I feel like permissions are key here.
upvoted 0 times
...
Jacquelyne
4 months ago
C seems off, /etc isn't usually for content access.
upvoted 0 times
...
Chaya
4 months ago
I’m surprised that it works for admin but not for anonymous.
upvoted 0 times
...
Winfred
4 months ago
Wait, why would you give write permissions to anonymous users? B is a no-go.
upvoted 0 times
...
Janey
4 months ago
Totally agree, that makes sense!
upvoted 0 times
...
Wilda
5 months ago
A) Applying read permissions to anonymous user for /content directory is the way to go.
upvoted 0 times
...
Mozell
5 months ago
D is just silly, who even uses /cont? A is clearly the right choice here.
upvoted 0 times
...
Leonora
5 months ago
Haha, I bet the developer forgot to check the permissions. Classic rookie mistake!
upvoted 0 times
...
Burma
6 months ago
I agree, A is the way to go. Permissions are key when dealing with context-aware configs.
upvoted 0 times
...
Berry
6 months ago
Option A is the correct answer. Applying read permissions to the anonymous user for the /content directory should fix the issue.
upvoted 0 times
...
Han
6 months ago
I think I saw a similar scenario where we had to give access to the /etc directory for anonymous users. Could that be the answer here?
upvoted 0 times
...
Vince
6 months ago
I feel like applying read permissions to the /content directory makes sense, but I can't recall if that's the right path for this specific issue.
upvoted 0 times
...
Tommy
6 months ago
This reminds me of a practice question where we had to adjust permissions for different user roles. I think read permissions are usually the key here.
upvoted 0 times
...
Micheal
6 months ago
I remember something about permissions affecting access, but I'm not sure if it's read or write that we need to change for anonymous users.
upvoted 0 times
...
Virgina
7 months ago
I'm feeling pretty confident about this one. The question mentions the configuration resource, so I think the best approach is to make sure the anonymous user can read from the /etc directory, which is where a lot of configuration stuff is typically stored. Option C seems like the way to go.
upvoted 0 times
...
Peggie
7 months ago
Okay, let me think this through. The question says the configuration resource is being accessed, so I don't think the issue is with the /conf directory. My money's on option C - applying read permissions to the /etc directory.
upvoted 0 times
...
Larue
7 months ago
Hmm, I'm a bit confused. Is the issue that the anonymous user can't access the configuration resource? If so, I'd guess that option A, applying read permissions to the /content directory, might be the way to go.
upvoted 0 times
...
Rory
7 months ago
This looks like a tricky one. I'm not too familiar with sling context-aware configuration, but I think the key is figuring out where the configuration resource is located and making sure the anonymous user has the right permissions.
upvoted 0 times
Mireya
3 months ago
I think option A makes the most sense. Read permissions for /content should do the trick.
upvoted 0 times
...
Theresia
3 months ago
Definitely! The anonymous user needs access to the right directories.
upvoted 0 times
...
Junita
3 months ago
I agree, permissions are crucial here.
upvoted 0 times
...
...

Save Cancel