Adobe Workfront AD0-E906 Book

When creating a log file in AEM, the proper practice is to configure it under the/apps/myproject/configurationpath for the specific runmode folders (e.g., config.dev, config.stage, config.prod). This ensures that the log file configuration is applied based on the environment.

Runmode-specific configurationensures that logs are generated for the correct environment (development, staging, production), following best practices for AEM development.

Option A suggests using the /apps/systemconfiguration path, which is not the recommended location for project-specific configurations. Option B suggests asking for admin access, but developers typically create logs through code configuration rather than direct access to the console.

Refer toAEM’s logging configuration documentationfor details on setting up logs for specific environments.

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 theinstallfolder within the repository:

The package should be stored in the file;$(maven.multiModuleProjectDirectory)/install 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 theCloud Manager documentation.

Workfront includes adocument checkoutfeature that allows users to lock a document when it is being edited, preventing others from downloading or editing the file simultaneously. This feature effectively stops duplication of effort and ensures that only one person can work on a document at a time.

Document Checkout: By navigating to the document details page and clicking "Check out," the document will be locked for editing by the person who checked it out. Other users will benotified that the document is being edited, and they will not be able to download or make changes until it is checked back in.

Option B is incorrect because changing the document status to "Unavailable" does not prevent downloading or editing. Option C, while helpful for communication, does not enforce restrictions, which could still lead to duplication of effort.

For more detailed information, refer to theDocument Collaboration and Managementsection in the Adobe Workfront documentation, which outlines how the check-in/check-out system works.

To implement conditionalautomatic publishingof assets from Workfront to AEM based on the value of the custom form field, you should:

Check the option "Automatically publish assets when sent from Workfront": This ensures that the assets will be automatically published to AEM when they are sent from Workfront.

Use the custom form field ("auto_publish_assets"): The system needs to check the value of this custom form field, and if it is set to"Yes", the assets will be automatically published.

Set the Custom Form Field Value to "Yes": In the configuration, you’ll specify that automatic publishing only occurs when the field value is "Yes."

Option B incorrectly refers to "Workflow" instead of "Workfront," and Option C refers to publishing to Brand Portal, which is irrelevant since the customer does not have Brand Portal.

Refer toWorkfront for AEM Enhanced Connector documentationfor step-by-step guidance on configuring conditional automatic asset publishing.