New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E906 Exam - Topic 4 Question 28 Discussion

Actual exam question for Adobe's AD0-E906 exam
Question #: 28
Topic #: 4
[All AD0-E906 Questions]

As part of the configuration of the workfront for Experience Manager enhanced connector, the solutions consultant needs to limit the access of the legal team Specifically, the legal team should only have read access to all of the content in Experience Manager. This group of users will solely be working in Workfront. but will have access to Experience Manager via the enhanced connector. The consultant has created a new user group in Experience Manager that includes the members of the legal team that exist in wf-workfront-users.

How should the solution consultant manage their access?

Show Suggested Answer Hide Answer
Suggested Answer: B

In this case, the solutions consultant needs to limit the legal team's access to read-only for all content in AEM. Since the legal team will be working in Workfront and accessing AEM via the enhanced connector, the best way to manage their access is to apply Access Control Entries (ACEs) to the wf-workfront-users user group.

ACEs allow you to specify detailed permissions for a group or user in AEM, such as granting read-only access to specific resources or folders within the DAM.

Options A and C would either grant too much access (as in the case of the Everyone user group) or allow contributions, which is beyond the requirement of just reading access.

Refer to AEM Access Control Management documentation to learn more about setting up ACEs and managing permissions.


Contribute your Thoughts:

0/2000 characters
Desmond
1 day ago
Option C is too broad. Everyone shouldn't have access.
upvoted 0 times
...
Kayleigh
6 days ago
I prefer option B too. We need to protect sensitive info.
upvoted 0 times
...
Lauryn
12 days ago
Option A seems risky. Contributors can do more than read.
upvoted 0 times
...
Dominic
17 days ago
Agreed! Limiting access is crucial for security.
upvoted 0 times
...
India
22 days ago
I’m surprised they didn’t mention how to handle permissions better!
upvoted 0 times
...
Freida
27 days ago
Option C would give them too much access, not a good idea.
upvoted 0 times
...
Elvera
1 month ago
Wait, can they really only have read access? That seems risky.
upvoted 0 times
...
Beckie
1 month ago
I disagree, option A makes more sense for limiting access.
upvoted 0 times
...
Cory
1 month ago
They should definitely go with option B. ACEs are the way to control access.
upvoted 0 times
...
Jina
2 months ago
Option A is the clear winner here. Can't go wrong with the tried and true Contributors group.
upvoted 0 times
...
Shakira
2 months ago
Hmm, I wonder if the legal team will actually use this feature or just stick to email and phone calls. Lawyers, am I right?
upvoted 0 times
...
Emerson
2 months ago
C is definitely not the right choice. Everyone group would give them way too much access.
upvoted 0 times
...
Winfred
2 months ago
This is a good question. I'm thinking option A might be the way to go, as adding the legal group to the AEM Contributors group would give them the necessary read-only access across the entire repository. But I'd want to double-check the specifics of the Contributors group to make sure that's the right approach.
upvoted 0 times
...
Beula
2 months ago
I'm not sure about applying ACEs to the wf-workfront-users group. Seems like that could have unintended consequences.
upvoted 0 times
...
Dominic
3 months ago
I think option B is the best choice. ACEs give precise control.
upvoted 0 times
...
Valentine
3 months ago
Option A seems like the way to go. Contributors should give the legal team the read-only access they need.
upvoted 0 times
...
Kenneth
3 months ago
I've worked with the enhanced connector before, and this sounds like a pretty straightforward access management issue. I'd go with option B and apply the appropriate ACEs to the wf-workfront-users group to give the legal team the required read-only permissions.
upvoted 0 times
...
Daniela
3 months ago
Okay, let me think this through. The key details are that the legal team needs read-only access to all content in Experience Manager, and they'll be working solely in Workfront. I think the solution might involve adding the legal user group to the AEM Contributors group, but I'm not 100% sure.
upvoted 0 times
...
Emerson
4 months ago
Hmm, this seems like it's about controlling access for a specific group of users in Workfront who need to access Experience Manager. I'm guessing the solution has to do with setting up the appropriate permissions in AEM.
upvoted 0 times
...
Vivan
4 months ago
I'm not entirely sure about this one. I think it might involve managing user access in Experience Manager, but I'm not familiar with the specifics of the enhanced connector.
upvoted 0 times
Ty
2 months ago
I think the legal team should have limited access.
upvoted 0 times
...
...
Alesia
4 months ago
I practiced a similar question where we had to limit access, and I think ACEs were the key to managing permissions effectively.
upvoted 0 times
...
Erick
4 months ago
Adding the legal user group to the Everyone group seems too broad; I feel like that would give them more access than just read.
upvoted 0 times
...
Lisbeth
4 months ago
I think applying ACEs to the wf-workfront-users group might be the best option, but I need to double-check how that works with Experience Manager.
upvoted 0 times
...
Gilma
5 months ago
I remember we discussed user groups in class, but I'm not sure if adding them to the Contributors group is the right approach for read-only access.
upvoted 0 times
...

Save Cancel