Page 1 of 50
Adobe Workfront for Experience Manager
Enhanced Connector Expert Latest
Questions and Verified Answers +
Detailed Study Guide | Guaranteed Pass |
Fully Updated & Trusted by DO Students
1. An implementation consultant is configuring the enhanced
connector's Project Linked Folders feature for a customer. The
customer wants the linked folder structure to be defined using the
Workfront Portfolio name, Workfront Program name, Workfront
Project name, and a custom form field "Project Type" with values
like 'Campaign' and 'Product Launch.'
Which Linked Folder Structure configuration defines this
correctly?
,Page 2 of 50
A) Portfolio, Program, Name, DE:Project Type
B) Portfolio, Program, Name, projectType
C) Program, Portfolio, Name, DE:Project Type
D) Portfolio, Name, Program, DE:Project Type
Answer: A) Portfolio, Program, Name, DE:Project Type
Rationale: The customer wants the folder hierarchy to be
Portfolio, then Program, then Project Name, and finally Project
Type (custom form field). The correct syntax uses DE: prefix for
custom form fields. DE:Project Type correctly references the
custom form field. Options B and C have incorrect ordering or
missing the DE: prefix required for custom form fields.
Q2. An Experience Manager user group needs to be created for
all Workfront users who use the enhanced connector. How are
Workfront users added to this group?
,Page 3 of 50
A) Manually import users using the "Import People" option in
Workfront
B) Automatically by the connector when users authenticate
C) Through the Adobe Admin Console user sync
D) By manually adding each user to the AEM user group
Answer: B) Automatically by the connector when users
authenticate
Rationale: When configuring the Workfront Enhanced Connector
in AEM, Workfront users who will use the connector are
automatically added to a corresponding AEM user group (wf-
workfront-users) via the connector. This automatic process ensures
permissions and group assignments sync correctly. The "Import
People" option in Workfront is for importing users into
Workfront, not for syncing to AEM.
, Page 4 of 50
Q3. On the AEM Dispatcher, a consultant is reviewing what HTTP
request methods to allow for /bin/workfront-tools. The following
methods are available: GET, HEAD, POST, PUT, and DELETE.
Which requests should be allowed?
A) DELETE only
B) HEAD and DELETE
C) GET, POST, and PUT
D) GET and HEAD only
Answer: C) GET, POST, and PUT
Rationale: When configuring allowed HTTP request methods
for /bin/workfront-tools, the safest and most appropriate
methods are GET (retrieve data), POST (submit data), and PUT
(update data). DELETE should be restricted unless absolutely
necessary to prevent unintended deletions. HEAD is typically not
required for this use case.
Adobe Workfront for Experience Manager
Enhanced Connector Expert Latest
Questions and Verified Answers +
Detailed Study Guide | Guaranteed Pass |
Fully Updated & Trusted by DO Students
1. An implementation consultant is configuring the enhanced
connector's Project Linked Folders feature for a customer. The
customer wants the linked folder structure to be defined using the
Workfront Portfolio name, Workfront Program name, Workfront
Project name, and a custom form field "Project Type" with values
like 'Campaign' and 'Product Launch.'
Which Linked Folder Structure configuration defines this
correctly?
,Page 2 of 50
A) Portfolio, Program, Name, DE:Project Type
B) Portfolio, Program, Name, projectType
C) Program, Portfolio, Name, DE:Project Type
D) Portfolio, Name, Program, DE:Project Type
Answer: A) Portfolio, Program, Name, DE:Project Type
Rationale: The customer wants the folder hierarchy to be
Portfolio, then Program, then Project Name, and finally Project
Type (custom form field). The correct syntax uses DE: prefix for
custom form fields. DE:Project Type correctly references the
custom form field. Options B and C have incorrect ordering or
missing the DE: prefix required for custom form fields.
Q2. An Experience Manager user group needs to be created for
all Workfront users who use the enhanced connector. How are
Workfront users added to this group?
,Page 3 of 50
A) Manually import users using the "Import People" option in
Workfront
B) Automatically by the connector when users authenticate
C) Through the Adobe Admin Console user sync
D) By manually adding each user to the AEM user group
Answer: B) Automatically by the connector when users
authenticate
Rationale: When configuring the Workfront Enhanced Connector
in AEM, Workfront users who will use the connector are
automatically added to a corresponding AEM user group (wf-
workfront-users) via the connector. This automatic process ensures
permissions and group assignments sync correctly. The "Import
People" option in Workfront is for importing users into
Workfront, not for syncing to AEM.
, Page 4 of 50
Q3. On the AEM Dispatcher, a consultant is reviewing what HTTP
request methods to allow for /bin/workfront-tools. The following
methods are available: GET, HEAD, POST, PUT, and DELETE.
Which requests should be allowed?
A) DELETE only
B) HEAD and DELETE
C) GET, POST, and PUT
D) GET and HEAD only
Answer: C) GET, POST, and PUT
Rationale: When configuring allowed HTTP request methods
for /bin/workfront-tools, the safest and most appropriate
methods are GET (retrieve data), POST (submit data), and PUT
(update data). DELETE should be restricted unless absolutely
necessary to prevent unintended deletions. HEAD is typically not
required for this use case.
