A solutions consultant needs to configure the enhanced connector for a customer. The customer has asked the solutions consultant to make sure that changes to metadata in Experience Manager will be synced back to Workfront on linked Workfront documents. Two of the fields that the customer wants synced are Content Type and Effort They are defined in workfront and Experience Manager as the following:
Document custom form fields in Workfront:
To accomplish this work, the solutions consultant configures a workflow model. The workflow model has a single step, Workfront-Map Property'.
What Property Assignments will make sure changes in Experience Manager are reflected in Workfront?
A)
B)
C)
To ensure that changes in metadata in Adobe Experience Manager (AEM) are synced back to Workfront for the fields Content Type and Effort, the correct property assignment should map the Workfront custom form fields to the corresponding paths in the AEM JCR repository.
In Option A:
CUSTOM FORMS
is mapped to /jcr:content/metadata/content-type
CUSTOM FORMS
is mapped to /jcr:content/metadata/effort
This configuration ensures that changes made in AEM's content-type and effort metadata properties will be reflected in the respective custom fields in Workfront.
Options B and C use incorrect prefixes (e.g., 'DE:') and would not map the properties correctly for synchronization between Workfront and AEM.
Refer to the Workfront Enhanced Connector documentation for detailed instructions on configuring metadata synchronization between AEM and Workfront.
A multi-faceted holiday promotion requires inputs from many different teams that manage promotional advertisements across varying marketing platforms Each marketing platform (i.e, social media and email blast) has different requirements for the ads. Each asset associated with the holiday promotion has its own workflow, which is unique to the team responsible for producing the asset. This holiday promotion is considered one of the most critical promotions for the year and is tracked in a campaign Portfolio Leadership needs visibility to the promotion assets to make sure they are tracking for an on-time delivery as they progress.
what is the correct way to track the assets associated with this promotion using a Program?
For a multi-faceted holiday promotion involving several teams and unique workflows, the best way to track the associated assets is to:
Establish the holiday promotion as a Program: This allows all related projects, each corresponding to a specific marketing platform (e.g., social media, email), to be grouped under a single program for easy tracking.
Associate each project with the Program: This ensures that all related assets and workflows are linked to the holiday promotion and can be reported on collectively.
Create a Project-level Custom Form Field: This will capture specific details related to the holiday promotion for each project, allowing for more tailored reporting.
Create a Project Report filtered to the holiday promotion: This report will enable leadership and stakeholders to track the progress of all assets related to the promotion and ensure on-time delivery.
Option A involves creating a Program for each platform, which adds unnecessary complexity. Option B is similar but lacks the specific tracking of custom fields at the project level.
Refer to Workfront's documentation on managing Programs and custom forms for details on setting up and reporting on large campaigns.
A customer wants to support translations on AEM Cloud Service environment. They have an existing third party vendor who will provide a pre-build package that must be deployed to AEM so it can be leveraged as port of the workflow process.
How should the developer deploy this third party library onto AEM Cloud Service?
In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project's codebase under the install folder within the repository:
The package should be stored in the <url>file;$(maven.multiModuleProjectDirectory)/install</url> directory.
Once stored, the deployment will be handled through Cloud Manager's deployment pipeline.
This ensures the third-party package is included in the standard deployment process and follows AEMaaCS's immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.
Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.
For more information, refer to AEMaaCS deployment best practices and the Cloud Manager documentation.
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.
A creative agency submits proofs for review to stakeholders from multiple companies on a regular basis prior to releasing final assets the creative agency only requires one decision from a company prior to releasing a final asset.
Before the proofs are sent to the stakeholders, the creative director must review the proof. Since this is a standard workflow used for the majority of the work, a proofing workflow template can be set up to expedite the proof approval.
In which two ways may this proofing workflow template be set up? (Choose two)
In this scenario, the proofing workflow needs two stages:
Stage 1: This stage routes the proof to the creative director upon proof creation. By selecting 'do not allow this stage to be deleted,' the workflow ensures that the creative director must always review the proof before it is sent to stakeholders. This ensures consistency in the review process and makes sure the creative director is always involved.
Stage 2: This stage activates when all decisions are made on the parent stage (i.e., the creative director's approval). Additionally, since the creative agency only requires one decision from each company, the 'only one decision required' setting is appropriate to speed up the process while ensuring the necessary approvals are gathered.
Option B is incorrect because setting the stage as private may hinder collaboration, and Option C suggests waiting until all decisions are approved, which is not necessary in this scenario.
Refer to Workfront documentation on proofing workflows for details on setting up multi-stage approval processes.
