Free Preparation Discussions
MENU
Adobe AD0-E906 Exam Questions
- Topic 1: Technical Requirements: This section covers how to utilize Workfront Custom Forms effectively. Given a scenario, show how to manage documents.
- Topic 2: Configuration: This section covers how to use the best practices for managing users. Apply procedural knowledge to adjust existing AEM asset workflows.
- Topic 3: Business Practices: This section covers how to analyze client requirements to recommend suitable workflow strategies. Shows how to set up Workfront approval and proofing workflows. Given a scenario, identify optimal practices.
- Topic 4: Installation and Configuration of Connector: This section covers how to verify prerequisites within AEM. Given a customer use case, identify which features of the connector need to be implemented.
Free Adobe AD0-E906 Exam Actual Questions
Note: Premium Questions for AD0-E906 were last updated On Jul. 29, 2026 (see below)
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?
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.
An AEM server is overloaded with too many concurrently running workflows. The developer decides to reduce the number of concurrent workflows. What should be configured?
In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.
This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI Web Console.
Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.
Refer to the AEM documentation on workflow scaling and performance for more information on how to adjust these settings in the OSGI configuration.
An organization uses a dropdown custom field for the type of creative assets that their internal studio produces. The studio managers use a report grouped by type of asset to determine which assets have been produced by the studio. A decision has been made to concentrate purely on digital work.
which action will prevent the print media options from being selected, while allowing historical data to display on the report?
In this case, the organization wants to prevent users from selecting print media options for new entries while still displaying historical data in reports. The best way to achieve this is to hide the print choices in the dropdown field. This approach ensures that:
Historical data remains unaffected: Since you are only hiding the options and not removing them, existing records with those print media values will continue to display in reports and other views.
No selection of new print options: By hiding these options, users will no longer be able to select them for new records, effectively preventing any further print media classifications.
Removing the print options (Option B) would delete historical data associated with them, which is not desirable for reporting. Moving them to the end of the list (Option C) doesn't restrict users from selecting them, which does not meet the objective of focusing solely on digital work.
This practice aligns with Adobe Workfront's best practices for managing dropdown fields, where options can be hidden but not removed, thus preserving the integrity of historical data while controlling future input.
For more details, refer to the Custom Fields section in Workfront's documentation, specifically around managing dropdown options and preserving historical data visibility in reports.
An AEM application requires a service user WRITE access to children nodes but not on the parent node itself. Which console should the developer use to apply appropriate ACL?
In AEM, when you need to manage access control (ACL) permissions, including setting specific permissions (like WRITE) for a service user on child nodes without affecting the parent node, the Permission Console is the appropriate tool.
The Permission Console allows you to set fine-grained permissions at both node and subnode levels, which is crucial for scenarios where access needs to be applied only to children nodes, not the parent node itself.
Option A (User Management Console) is used for managing user details, and Option C (Group Management Console) manages group settings, but neither of these are used for setting node-level permissions.
Refer to AEM's User and Group Access Management documentation for more information on using the Permission Console to manage ACLs effectively.
A custom field needs to be mapped in AEM metadata mapping the field details are below:
Label - Creative Manager
Name - managerCreative Description
The resource assigned the creative manager role
How is the field from Workfront referenced in AEM?
In Adobe Experience Manager (AEM), when mapping metadata fields from Workfront, custom form fields are referenced using the CUSTOM FORMS prefix followed by the internal name of the field. In this case:
The Label is 'Creative Manager'
The Name is 'managerCreative,' which is the internal field name in Workfront.
To reference this field in AEM metadata, you need to use the CUSTOM FORMS: prefix followed by the field's name, making the correct reference CUSTOM FORMS: managerCreative. This ensures that AEM can correctly pull the metadata value from Workfront when syncing or using the Workfront enhanced connector for AEM.
Options A and B are incorrect because they either lack the proper formatting or are incomplete.
For more details on this configuration, you can refer to Adobe Workfront's enhanced connector documentation for AEM, particularly around metadata mapping and field referencing practices.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Lisa Stewart
13 days agoDonald Murphy
28 days agoJeffrey Perez
1 month agoCharles Young
2 months agoElizabeth Wright
2 months agoJustin Hernandez
3 months agoAmanda Collins
3 months agoJoshua Morgan
3 months agoHeather Young
3 months agoAmy Turner
2 months agoEdward Evans
2 months agoCory
4 months agoCristen
4 months agoLasandra
4 months agoSabrina
4 months agoTammy
5 months agoJerry
5 months agoJosue
5 months agoMargart
6 months agoCarole
6 months agoPamela
6 months agoReynalda
6 months agoEzekiel
7 months agoMilly
7 months agoGilma
7 months agoWhitley
7 months agoLarae
8 months agoVincent
8 months agoRanee
8 months agoElliot
8 months agoJoesph
9 months agoTerry
9 months agoChery
9 months agoIra
9 months agoTammara
10 months agoMarica
10 months agoValentin
10 months agoAlesia
11 months agoCharlesetta
11 months agoLemuel
1 year agoRaelene
1 year agoIra
1 year agoStephaine
1 year agoToi
1 year agoAshleigh
2 years agoSabra
2 years agoWhitley
2 years agoDelbert
2 years agoCrissy
2 years agoBulah
2 years agoOllie
2 years agoJolanda
2 years agoRaymon
2 years agoArt
2 years agoSabine
2 years agoHeike
2 years agoEdison
2 years agoHester
2 years agoMalcolm
2 years agoTasia
2 years agoMiss
2 years ago