Adobe Workfront for Experience Manager Enhanced
Connector Expert Latest Questions and Verified
Answers + Detailed Study Guide | Guaranteed Pass |
Fully Updated
Section 1: Installation & Configuration (Questions 1-56)
1. An implementation consultant is setting up the Workfront for AEM enhanced
connector for a customer. Before installing the connector, which prerequisite must
be validated regarding the AEM environment's firewall and dispatcher settings?
A) The dispatcher must allow only POST requests to /bin/workfront-tools
B) The dispatcher must allow GET, POST, and PUT requests to /bin/workfront-
tools and allow the HTTP headers for authorization, username, and API key
C) The dispatcher must block all requests to /bin/workfront-tools and use a proxy server
instead
D) Only HEAD and DELETE requests should be allowed to optimize performance
Answer: B
Rationale: Prior to installation, the customer must ensure their dispatcher allows for the
HTTP headers for authorization, username, and API key, and that GET, POST, and PUT
requests are allowed to the /bin/workfront-tools path. This path points to the connector
servlet that manages calls on the AEM side .
2. A consultant is preparing to install the enhanced connector for a customer with
an AEM as a Cloud Service environment. When the customer attempts to add the
required packages to the project's pom.xml file, which section should the packages
be added to?
A) <tools>
B) <embedded>
C) <servers>
D) <dependencies>
Answer: B
Rationale: When adding the required packages for the Enhanced Connector in AEM, they
should be added to the Embedded section of the pom.xml for all subprojects. The Embedded
section is used to define dependencies that need to be bundled with the AEM project,
ensuring that the connector's functionality is included in the deployment .
,3. After installing the enhanced connector package, where in AEM does the
consultant navigate to configure the Workfront connection?
A) Tools > General > CRXDE Lite
B) Tools > Cloud Services > Workfront Tools Configuration
C) Tools > Assets > Workfront Integration
D) Tools > Deployment > Workfront Connector
Answer: B
Rationale: After installation, the configuration is found by navigating to Tools > Cloud
Services > Workfront Tools Configuration. From there, select workfront-tools in the left
panel and select Create to configure the connection details .
4. In the Workfront Connection dialog during initial setup, what is the significance
of the "Configuration Title" field?
A) It defines the workflow model used for asset processing
B) The configuration title name is the same name that will get applied to the
document provider custom integration that gets set up on the Workfront side
C) It determines the AEM user group that will have access to the connector
D) It sets the default DAM folder path for linked folders
Answer: B
Rationale: The configuration title name is the same name that will get applied to the
document provider custom integration that gets set up on the Workfront side. Setting the
name here is important in order to identify the correct document custom provider that
gets created in your Workfront environment .
5. When configuring the AEM API endpoint domain in the Workfront connection
settings, what should the consultant enter?
A) The full URL including /bin/workfront-tools
B) The main URL only (without additional paths); the system
appends /bin/workfront-tools automatically
C) The Workfront API endpoint URL
D) The AEM publish instance URL only
Answer: B
Rationale: The configuration automatically appends the path /bin/workfront-tools for the
user. Only the main URL needs to be populated, pointing to the AEM environment. The
system handles the rest of the path automatically .
,6. After configuring the Workfront connection in AEM and clicking "Connect to
Workfront," where should the consultant verify that the connection was
successfully established?
A) In AEM's OSGi Console under Configuration Status
B) In Workfront, navigate to Setup > Documents > Custom Integrations to verify
the API key matches and the connection is Enabled
C) In the AEM error.log file for successful handshake messages
D) In Workfront's System Logs under API Connections
Answer: B
Rationale: To verify the connection, access it in Workfront and verify that the API key is the
same and that the connection is Enabled. Navigate to Setup > Documents > Custom
Integrations in Workfront to perform this verification .
7. A consultant is deploying the enhanced connector to an AEM as a Cloud Service
environment. The customer uses a corporate proxy for outbound connections
from AEM to Workfront. The initial cloud configuration fails with proxy detection
errors. What is the correct approach to resolve this?
A) Install the connector using the Package Manager instead of Maven
B) Create an OSGi configuration file (e.g., org.apache.http.proxyconfigurator-
workfront.cfg.json) in the project's ui.config folder and deploy via Cloud Manager
C) Manually edit the OSGi configurations in the Felix Web Console
(/system/console/configMgr)
D) Disable the proxy and use Direct Connect instead
Answer: B
Rationale: In AEM as a Cloud Service, it is not possible to access the Felix Web Console to
apply OSGi configurations. All OSGi configurations must be created as configuration files
in the project's codebase and deployed using Cloud Manager. The configuration file should
be created in the ui.config folder with the appropriate parameters for host, port, and
credentials .
8. In AEM as a Cloud Service, where can a consultant view active OSGi
configurations after deployment to verify the proxy settings are applied correctly?
A) Package Manager Console
B) Developer Console (via Cloud Manager)
C) CRXDE Lite
D) Workfront Setup Menu
, Answer: B
Rationale: Once deployed, the Developer Console (accessible via Cloud Manager) can be
used to view active OSGi configurations. This provides validation that the configuration
files were picked up correctly by the AEM as a Cloud Service runtime .
9. A customer wants to use the connector's automatic linked folder creation
feature. Which prerequisites must be met in Workfront before this feature will
function correctly?
A) The project must be marked as "Current" status
B) Event subscriptions must be enabled in the Workfront Tools Cloud Service
configuration
C) The Workfront API must be disabled for security
D) All users must have Administrator privileges
Answer: B
Rationale: Event subscriptions are required for three enhanced connector features to
function: automatic creation of project-linked folders, synchronization of Workfront
document custom form value changes with AEM asset metadata, and automatic
publishing of assets to Brand Portal upon project completion. These must be enabled in
the configuration .
10. A consultant is configuring the event subscriptions for the first time. After
navigating to the Event Subscriptions tab and selecting the Workfront custom
integration, what is the next required action?
A) Manually create each event subscription in Workfront's API Explorer
B) Click "Enable Workfront Event Subscriptions" to automatically create the
required subscriptions
C) Restart the AEM instance to apply the configuration
D) Copy the API key from Workfront and paste it into AEM
Answer: B
Rationale: After selecting the Workfront custom integration created during setup, the
consultant must click "Enable Workfront Event Subscriptions" to automatically create the
required event subscriptions. This action triggers the connector to programmatically create
the necessary subscriptions in Workfront .
11. When configuring linked folder structures, the "Linked Folder Structure" field
accepts comma-separated values. Which values can be used to define the
hierarchical folder structure? (Select all that apply)
Connector Expert Latest Questions and Verified
Answers + Detailed Study Guide | Guaranteed Pass |
Fully Updated
Section 1: Installation & Configuration (Questions 1-56)
1. An implementation consultant is setting up the Workfront for AEM enhanced
connector for a customer. Before installing the connector, which prerequisite must
be validated regarding the AEM environment's firewall and dispatcher settings?
A) The dispatcher must allow only POST requests to /bin/workfront-tools
B) The dispatcher must allow GET, POST, and PUT requests to /bin/workfront-
tools and allow the HTTP headers for authorization, username, and API key
C) The dispatcher must block all requests to /bin/workfront-tools and use a proxy server
instead
D) Only HEAD and DELETE requests should be allowed to optimize performance
Answer: B
Rationale: Prior to installation, the customer must ensure their dispatcher allows for the
HTTP headers for authorization, username, and API key, and that GET, POST, and PUT
requests are allowed to the /bin/workfront-tools path. This path points to the connector
servlet that manages calls on the AEM side .
2. A consultant is preparing to install the enhanced connector for a customer with
an AEM as a Cloud Service environment. When the customer attempts to add the
required packages to the project's pom.xml file, which section should the packages
be added to?
A) <tools>
B) <embedded>
C) <servers>
D) <dependencies>
Answer: B
Rationale: When adding the required packages for the Enhanced Connector in AEM, they
should be added to the Embedded section of the pom.xml for all subprojects. The Embedded
section is used to define dependencies that need to be bundled with the AEM project,
ensuring that the connector's functionality is included in the deployment .
,3. After installing the enhanced connector package, where in AEM does the
consultant navigate to configure the Workfront connection?
A) Tools > General > CRXDE Lite
B) Tools > Cloud Services > Workfront Tools Configuration
C) Tools > Assets > Workfront Integration
D) Tools > Deployment > Workfront Connector
Answer: B
Rationale: After installation, the configuration is found by navigating to Tools > Cloud
Services > Workfront Tools Configuration. From there, select workfront-tools in the left
panel and select Create to configure the connection details .
4. In the Workfront Connection dialog during initial setup, what is the significance
of the "Configuration Title" field?
A) It defines the workflow model used for asset processing
B) The configuration title name is the same name that will get applied to the
document provider custom integration that gets set up on the Workfront side
C) It determines the AEM user group that will have access to the connector
D) It sets the default DAM folder path for linked folders
Answer: B
Rationale: The configuration title name is the same name that will get applied to the
document provider custom integration that gets set up on the Workfront side. Setting the
name here is important in order to identify the correct document custom provider that
gets created in your Workfront environment .
5. When configuring the AEM API endpoint domain in the Workfront connection
settings, what should the consultant enter?
A) The full URL including /bin/workfront-tools
B) The main URL only (without additional paths); the system
appends /bin/workfront-tools automatically
C) The Workfront API endpoint URL
D) The AEM publish instance URL only
Answer: B
Rationale: The configuration automatically appends the path /bin/workfront-tools for the
user. Only the main URL needs to be populated, pointing to the AEM environment. The
system handles the rest of the path automatically .
,6. After configuring the Workfront connection in AEM and clicking "Connect to
Workfront," where should the consultant verify that the connection was
successfully established?
A) In AEM's OSGi Console under Configuration Status
B) In Workfront, navigate to Setup > Documents > Custom Integrations to verify
the API key matches and the connection is Enabled
C) In the AEM error.log file for successful handshake messages
D) In Workfront's System Logs under API Connections
Answer: B
Rationale: To verify the connection, access it in Workfront and verify that the API key is the
same and that the connection is Enabled. Navigate to Setup > Documents > Custom
Integrations in Workfront to perform this verification .
7. A consultant is deploying the enhanced connector to an AEM as a Cloud Service
environment. The customer uses a corporate proxy for outbound connections
from AEM to Workfront. The initial cloud configuration fails with proxy detection
errors. What is the correct approach to resolve this?
A) Install the connector using the Package Manager instead of Maven
B) Create an OSGi configuration file (e.g., org.apache.http.proxyconfigurator-
workfront.cfg.json) in the project's ui.config folder and deploy via Cloud Manager
C) Manually edit the OSGi configurations in the Felix Web Console
(/system/console/configMgr)
D) Disable the proxy and use Direct Connect instead
Answer: B
Rationale: In AEM as a Cloud Service, it is not possible to access the Felix Web Console to
apply OSGi configurations. All OSGi configurations must be created as configuration files
in the project's codebase and deployed using Cloud Manager. The configuration file should
be created in the ui.config folder with the appropriate parameters for host, port, and
credentials .
8. In AEM as a Cloud Service, where can a consultant view active OSGi
configurations after deployment to verify the proxy settings are applied correctly?
A) Package Manager Console
B) Developer Console (via Cloud Manager)
C) CRXDE Lite
D) Workfront Setup Menu
, Answer: B
Rationale: Once deployed, the Developer Console (accessible via Cloud Manager) can be
used to view active OSGi configurations. This provides validation that the configuration
files were picked up correctly by the AEM as a Cloud Service runtime .
9. A customer wants to use the connector's automatic linked folder creation
feature. Which prerequisites must be met in Workfront before this feature will
function correctly?
A) The project must be marked as "Current" status
B) Event subscriptions must be enabled in the Workfront Tools Cloud Service
configuration
C) The Workfront API must be disabled for security
D) All users must have Administrator privileges
Answer: B
Rationale: Event subscriptions are required for three enhanced connector features to
function: automatic creation of project-linked folders, synchronization of Workfront
document custom form value changes with AEM asset metadata, and automatic
publishing of assets to Brand Portal upon project completion. These must be enabled in
the configuration .
10. A consultant is configuring the event subscriptions for the first time. After
navigating to the Event Subscriptions tab and selecting the Workfront custom
integration, what is the next required action?
A) Manually create each event subscription in Workfront's API Explorer
B) Click "Enable Workfront Event Subscriptions" to automatically create the
required subscriptions
C) Restart the AEM instance to apply the configuration
D) Copy the API key from Workfront and paste it into AEM
Answer: B
Rationale: After selecting the Workfront custom integration created during setup, the
consultant must click "Enable Workfront Event Subscriptions" to automatically create the
required event subscriptions. This action triggers the connector to programmatically create
the necessary subscriptions in Workfront .
11. When configuring linked folder structures, the "Linked Folder Structure" field
accepts comma-separated values. Which values can be used to define the
hierarchical folder structure? (Select all that apply)
