[2025年04月] ベストAdobe Workfront学習ガイドはAD0-E906試験問題集
AD0-E906認定ガイド問題と解答トレーニング
Adobe AD0-E906 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
質問 # 34
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?
- A. Establish the holiday promotion as a Program, associate each Protect with the program. create a Pitted Report filtered to the Program, share the Report with the stakeholders
- B. Establish a Program for each marketing platform, associate each Project with the Program create a Program level Custom Form Flew for the holiday promotion, create a Project Repot filtered to the holiday promotion, share the Report with the stakeholders.
- C. Establish the holiday promotion as a Program, associate each Prefect with the Program, create a Project level Custom Form Field for the holiday promotion, create a Protect Report filtered to the holiday promotion, share the Report with the stakeholders.
正解：C
解説：
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.
質問 # 35
A customer sets up a calculated field on a request form. A user manually converts the request to a project and selects a template from the available active templates. How should the administrator configure the Project custom form to make sure the value is passed to the project on conversion?
- A. Add the same field will a different calculation
- B. Add the-same- field but leave the calculation blank
- C. Add a new field with the same name but make it a text field.
正解：B
解説：
When converting a request to a project in Adobe Workfront, it's important to ensure that custom fields and their values are correctly passed from the request form to the project form. To achieve this, you need to add the same custom field on the project form, but in this case, the calculation should be left blank because the calculated value from the request form will be passed over and does not need to be recalculated at the project level.
Same field: The field needs to be exactly the same (same internal name) so the data can flow between the request and the project during the conversion.
Blank calculation: By leaving the calculation blank, you ensure that the field will accept the value from the request without overriding it or attempting to recalculate it.
For more details on setting up custom forms in Workfront and handling calculated fields during request-to-project conversions, refer to the Adobe Workfront Form Customization Guide.
質問 # 36
A developer implements a custom workflow process using the following code:
The code bundle has been deployed to AEM and displays as active in the Web Console. The developer has created a new workflow model, added a process step, and wants to configure that step to use the custom workflow process. However, the custom workflow process does not appear in the dropdown menu.
What should be done to resolve this issue?
- A. Add the process. label property to the @Component annotation in the CustomizationflowProcess class
- B. Add the process. title property to the @Component annotation in the CustomizationflowProcess class
- C. Add the process. name property to the @Component annotation in the CustomizationflowProcess class
正解：C
解説：
In AEM, for a custom workflow process to be available for selection in the dropdown menu of a process step, the process.name property must be set in the @Component annotation. This property defines the unique name under which the custom workflow process will be registered and visible in the workflow model editor.
Here is an example of how this should be added to the existing code:
@Component(service = WorkflowProcess.class,
property = {"process.label=Custom Workflow Process", "process.name=customWorkflowProcess"}) process.label: This is the label that appears in the workflow model editor dropdown.
process.name: This is the internal identifier used by AEM to register the workflow process.
Options A and B would define other properties but will not resolve the issue of the custom workflow not appearing in the dropdown. The key property needed here is process.name.
For more details, refer to the AEM documentation on creating custom workflows and annotating components.
質問 # 37
A company has a workflow where multiple people ate downloading and working on the same document simultaneously, which causes duplication of efforts. The company wants to use a document feature that will stop others from downloading the document when others are working on It.
Which document feature should De used?
- A. Change the document status to Unavailable
- B. Post an update stating mat an employee is editing the document
- C. Go into the document details page and dick Check out
正解：C
解説：
Workfront includes a document checkout feature 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 be notified 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 the Document Collaboration and Management section in the Adobe Workfront documentation, which outlines how the check-in/check-out system works.
質問 # 38
A consultant is working with a customer's Marketing department on an Adobe Workfront engagement. The customer has already had a successful deployment of Workfront in the IT department. This installation has been extremely simple, with a single system administrator, five custom statuses used by the IT department, and some templates and reports. The director of Marketing is adamant that the Marketing department will not be using anything created for IT. The engagement cannot disrupt the existing installation.
Which approach should the consultant take?
- A. Create companies for Marketing and IT create a system administrator for each, and share each department's resources with the company
- B. Create team for Marketing and IT, create a tear administrator fix each, and share each department's resources with the team
- C. Create groups for Marketing and it. create a group administrator for each, and share each department's resources with the group
正解：C
解説：
In this scenario, the best approach is to create separate groups for Marketing and IT within the same Workfront instance. Each group will have its own group administrator, and each department's resources (e.g., custom statuses, templates, reports) can be isolated and managed independently by the group admins.
This solution ensures that:
The existing IT setup is not disrupted.
The Marketing department can have its own customized Workfront environment without overlapping with IT's configurations.
This approach avoids creating unnecessary complexity (as in Option A with companies) or restricting functionality (as in Option B with teams).
Refer to Workfront documentation on group management to learn how to implement group-specific configurations in a single instance.
質問 # 39
A company calculates the benefit of a request based on the answers to 4 questions on a request custom form, this benefit value Is used to approve the request The values can be 0 through 15. Projects are then char ted in benefit groups as follows:
Level 1:0
Level 2: 1 - 5
Level 3: 6 10
Level 4 11-15
- A. Use text mode on the grouping with an aggregator formula to link to the project form
- B. Use a value expression on the view to link to the source request object
- C. In addition to the calculated value on the request, what other calculation should be created to achieve this reporting
- D. Use a calculated expression on the protect custom field to calculate the benefit value
正解：B
解説：
In this scenario, the company is looking to group projects based on a benefit calculation from a custom form. The most efficient way to achieve this grouping and reporting structure in Adobe Workfront is by creating a value expression on the view. This method allows you to dynamically link the benefit value from the request object to other reporting structures, including the project object.
Value Expression on View: The value expression acts as a direct link between the custom form's calculated field and the reporting or view settings, enabling the system to pull the benefit value dynamically from the request.
Request Object Linking: By linking to the source request object through the value expression, it allows for seamless integration of calculated values into the project reporting view, ensuring that the benefit groups (Level 1-4) can be reported accurately based on the defined thresholds (0, 1-5, 6-10, 11-15).
This approach is more efficient compared to creating multiple calculated fields across different objects, and it allows for better maintainability and adaptability in future changes.
References from Adobe Workfront documentation emphasize the use of value expressions in reports and views for linking and utilizing calculated fields across different objects, enhancing the flexibility and power of custom reporting capabilities. Text mode is not necessary here because it is primarily used for custom formatting or more advanced use cases that don't involve simple value transfers between objects.
For more detailed information, you can refer to the official Workfront Help documentation on Custom Forms and Advanced Reporting Techniques in Adobe Workfront, where calculated fields and value expressions are thoroughly covered.
質問 # 40
A developer writes the following code to programmatically copy an existing asset to another folder in the DAM:
After executing this code. The developer receives the following exception:javax.jcr. PathNotFoundException What caused this issue?
- A. The path /content/dam/project does not exist
- B. The user lacks READ permission lo the asset in /content/dam/projectA
- C. The asset in /content /dam/projectA/asset.jpg does not exist
正解：C
解説：
The javax.jcr.PathNotFoundException in this case indicates that the path to the asset /content/dam/projectA/asset.jpg cannot be found. The most likely cause is that the asset does not exist at the specified location, and thus the AssetManager is unable to copy it.
PathNotFoundException: This exception is thrown when the repository path (in this case, the asset path) is not found in the JCR repository, meaning that the asset does not exist or the path is incorrect.
Other possibilities like permissions issues (Option C) would typically result in a PermissionDeniedException, and Option B is incorrect because the issue specifically pertains to the asset path, not the parent folder.
To resolve this, the developer should check if the asset exists at the specified path or if the path is misspelled. For more information, refer to the AEM documentation on handling assets and JCR path exceptions.
質問 # 41
Metadata mappings between Adobe Workfront and the AEM have been configured A user wants to send a document and its metadata from Adobe Workfront to Adobe Experience Manager Assets.
How should the user accomplish this?
- A. Select the document in Workfront. click Send to, choose the Experience Manager integration, and metadata will synch automatically
- B. Select the document in workfront. choose New Version, choose the experience Manager integration, choose the metadata to synch
- C. Select the document in Workfront click Send to. choose the experience Manager integration, choose the metadata to synch
正解：A
解説：
When metadata mappings between Adobe Workfront and AEM are configured, the process of sending a document along with its metadata from Workfront to Adobe Experience Manager (AEM) Assets is streamlined. The user selects the document in Workfront, clicks "Send to," and chooses the Experience Manager integration.
The metadata fields that have been mapped are automatically synchronized along with the document. There is no need for manual selection of metadata at this stage, as the integration ensures that all configured mappings are applied.
This functionality is part of the enhanced connector, which simplifies the workflow between Workfront and AEM Assets by automating the synchronization of mapped metadata fields during the document transfer.
For more details, refer to Adobe's documentation on Workfront for Experience Manager Enhanced Connector, which outlines how automatic metadata synchronization works during document transfers.
質問 # 42
A developer needs to deploy com myCompany.ui.content package to only AEM Cloud Service author environment Which option should the developer choose to meet the requirement?
- A.
- B.
- C.
- D.
正解：A
解説：
The requirement is to deploy the com.myCompany.ui.content package specifically to the AEM Cloud Service author environment. The key here is ensuring that the package is targeted correctly to the author instance, without affecting other environments.
Option A uses the following target:
<target>/apps/my-company-packages/content/install.author</target>
The use of install.author ensures that the package will only be installed on the author environment of AEM as a Cloud Service, meeting the developer's requirement. This is a common approach in AEM Cloud Service projects, where you differentiate between environments using the appropriate subfolder (in this case, author).
Option B (author.install) and Option D are similar but incorrect because they are not standard for specifying the exact environment, while Option C (install/) is too generic and could apply to both author and publish environments.
Refer to the AEM Cloud Service documentation on deployment and package management for more details on targeting specific environments such as author during content deployment.
質問 # 43
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?
- A. Remove the print choices on the dropdown field
- B. Move the print choices to the end of the dropdown list
- C. Hide the print choices on the dropdown field
正解：C
解説：
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.
質問 # 44
An implementation consultant wants to configure the enhanced connector inside a customer's Adobe Experience Manager environment. The customer needs the automatic creation of project linked folder, synchronization of changes in Workfront document custom form values to AEM asset metadata, and the automatic publication of assets to Brand Portal upon project completion.
Which process does each requested functionality rely on?
- A. Workflows
- B. Webhooks
- C. Event Subscriptions
正解：C
解説：
The features requested by the customer, such as automatic folder creation, synchronization of Workfront document custom form values to AEM asset metadata, and automatic publication of assets to Brand Portal upon project completion, rely on Event Subscriptions in the enhanced connector configuration.
Event Subscriptions are triggered when certain events occur, such as project completion or updates to custom form values, ensuring that the correct actions (like folder creation or asset publication) happen automatically.
Option A (Workflows) would be used for content approval processes but not for these specific automatic actions. Option B (Webhooks) can handle external notifications but is not directly relevant for these tasks within AEM and Workfront.
For more information, refer to AEM Enhanced Connector documentation on Event Subscriptions and their use in automating processes.
質問 # 45
A customer finds an Ul issue with component (/apps/<customer-project>/<component-name>) on AEM page It needs to be fixed urgently to avoid miscommunication. The developer has been asked to urgently make the change in AEM production.
How should the developer deploy the change to an AEM Cloud Service production environment?
- A. Fix the component on local AEM and create an AEM package for that specific component that can be deployed to Production using package Manager as a one-off urgent fix
- B. Fix the Ul issue as part of the customer code base and deploy the change to immutable repository using Cloud Manage' pipeline
- C. Due to the urgency of the request. Make the Ul fix directly to the component on AEM Production using CRXOE and then make same change to customer code bate
正解：B
解説：
In AEM Cloud Service, the correct approach to making changes, even urgent ones, is to update the codebase and deploy it through the Cloud Manager pipeline. This ensures that the change is part of the version-controlled, immutable repository and follows best practices for deployment.
Immutable infrastructure: AEMaaCS does not allow direct modifications to production environments (e.g., via CRXDE Lite). All changes must be deployed through Cloud Manager, ensuring consistency and traceability.
Making changes directly on production via CRXDE or deploying one-off fixes using the Package Manager (Options B and C) violates AEMaaCS's immutable infrastructure principle and is not supported.
Refer to Adobe Cloud Manager's documentation for best practices on deploying urgent fixes in AEM as a Cloud Service.
質問 # 46
A user wants to send a new version of a document they have uploaded to Workfront (o make sure that this latest version is now available in Adobe Experience Manager Assets. This document has previously been uploaded into both Workfront and the AEM.
How should the user accomplish this?
- A. Select the document in workfront. make sure it has the same name as the previous version, click Send to. Choose. The experience Manager integration
- B. Select the document in Workfront. select New Version, choose the Experience Manager integration, upload the revised version
- C. Select the document in Workfront rename to include the version number. click Send to. choose the experience Manager integration
正解：B
解説：
To upload a new version of a document and ensure it is available in AEM Assets, the user must select the New Version option in Workfront. This triggers the version control process where the updated file can be uploaded.
By choosing the Experience Manager integration after selecting New Version, the system ensures that the latest version of the document is sent to AEM Assets, where it will replace the previous version without losing version history.
This workflow supports maintaining version control between Workfront and AEM, ensuring that the most current version of the asset is always available in both systems.
Refer to the Workfront-AEM Enhanced Connector Guide for further details on version control and document updates between Workfront and AEM.
質問 # 47
An AEM Developer needs to create a log file for the project.
Which next step should the developer take?
- A. Create a log file under /apps/systemconfiguration... specific runmodp folder(s).
- B. Ask AMS/DevOps for admin access to ceate a log file via console.
- C. Create a log file under /apps/myprotect/configuration.... specific rubmode folder(s).
正解：C
解説：
When creating a log file in AEM, the proper practice is to configure it under the /apps/myproject/configuration path 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 configuration ensures 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 to AEM's logging configuration documentation for details on setting up logs for specific environments.
質問 # 48
An AEM Author wants to search and filter through all assets in the DAM to find assets expiring within the next week.
What is the most efficient way of doing this?
- A. Configure the Assets Admin search rail to include the property Predicate and configure the property name to jcr:content/metadata/prism:expirationDate
- B. Configure the Assets admin Seach rall to include the Date Range Predicate and configure the property name to content to jcr:content/metadata/prism:expirationDate
- C. Configure the Assess Admin Search rail to include the Relative Date Predicate
正解：C
解説：
To search for assets that are expiring within the next week, the most efficient way is to configure the search rail using the Relative Date Predicate. This predicate allows for dynamic filtering based on a relative date range, such as "next week." The Relative Date Predicate automatically adjusts to search for assets within a specific upcoming time frame, such as the expiration date.
Option A and B are more rigid and require specific date or range configurations, which may not be as flexible or user-friendly as the relative date search.
Refer to AEM's Assets Admin Search Rail configuration documentation for more information on predicates and their use in filtering search results.
質問 # 49
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.
正解：A
解説：
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.
質問 # 50
While reviewing the customer's configuration, the consultant lists the following paths as existing within the customer's Experience Manager repository:
/Apps/dam/gui/content/foldermetadatasschemaeditor
/Apps/dam/gui/content/folderscheduleconfiguration
/Apps/dam/gui/content/folderschemaconfigproperties
Which path must be deleted prior to the installation of the Enhanced Connector?
- A. /Apps/dam/gui/content/folderschemaconfigproperties
- B. /Apps/dam/gui/content/folderscheduleconfiguration
- C. /Apps/dam/gui/content/foldermetadatasschemaeditor
正解：C
解説：
Before installing the Enhanced Connector, the path /Apps/dam/gui/content/foldermetadatasschemaeditor should be deleted to avoid conflicts with the new configuration. This path relates to the older folder metadata schema editor, which can interfere with the Enhanced Connector setup.
Paths related to folder scheduling (folderscheduleconfiguration) and configuration properties (folderschemaconfigproperties) are not related to the Enhanced Connector and do not need to be removed.
Refer to the Enhanced Connector installation guide for specific details on preparing the AEM repository for the connector.
質問 # 51
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)
- A. Stage 2 activate when all decisions are made on parent stage and select only one decision required.
- B. Stage 1 activate on proof creation, routing to the creative director, set as a private stage, select do not allow this stage to be deleted
- C. Stage 2 activate when all decisions are approved on parent stage and select only one decision required.
- D. Stage 1 activate on proof creation, routing to the creative director, select do not allow this stage to be deleted.
正解：A、D
解説：
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.
質問 # 52
Given the following workflow launcher configuration:
What change should be made to the configuration to trigger the workflow?
- A. Modify the condition to dc ==image/
- B. Modify the path to /content/dam/.<em>/)en(/.<em>/)
- C. Modify the node type to nt:file
正解：A
解説：
In this scenario, the workflow launcher is configured to trigger a workflow for assets in the path /content/dam/projects/en/designs. However, to ensure that the workflow only triggers for image assets, the condition must be updated to filter the relevant asset types. The condition should be modified to dc:format==image/*, which ensures that only assets with an image format trigger the workflow.
Condition "dc
==image/*": This filters assets based on their format (MIME type), ensuring that the workflow is only triggered for images, which matches the use case of working with assets such as JPGs or PNGs.
Option B suggests modifying the path, but the existing path (/content/dam/projects/en/designs) is correct for the project structure. Option C suggests changing the node type to nt:file, which is incorrect since the node type for assets in AEM is typically dam:Asset.
For more information, refer to AEM documentation on workflow launchers and DAM metadata properties.
質問 # 53
On the dispatcher, the consultant is reviewing what HTTP request methods to allow to /bin/workfront-tools. The following methods are available: GET, HEAD, POST, PUT, and DELETE.
Which requests should be allowed?
- A. DELETE POST and GET
- B. GET, POST, and PUT
- C. HEAD. PUT. and DELETE
正解：B
質問 # 54
An implementation consultant is preparing to configure the enhanced connector between AEM and Workfront. As part of this, the consultant needs to make sure the firewall is properly configured.
Which two critical processes utilized by the enhanced connector does this allow? (Choose two.)
- A. Experience Manager Workflows
- B. Single sign-on (SSD)
- C. Evert Subscriptions
- D. Webhooks
正解：C、D
解説：
To ensure proper functioning of the Enhanced Connector between AEM and Workfront, it is critical that the firewall allows traffic for Event Subscriptions and Webhooks:
Event Subscriptions: These are necessary for synchronizing events between Workfront and AEM, such as when assets are modified or when metadata is updated.
Webhooks: Webhooks enable real-time data exchange and notifications between the two systems, allowing instant updates to flow between Workfront and AEM.
Option A (Experience Manager Workflows) is relevant within AEM but not directly tied to firewall configuration for the connector. Option B (Single Sign-On) is a security feature but not specifically tied to the Enhanced Connector's data synchronization processes.
Refer to the Workfront Enhanced Connector documentation for details on the processes that rely on Event Subscriptions and Webhooks.
質問 # 55
An implementation consultant is configuring the enhanced connector Project Linked holders 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 the project type. The project type is a project custom form field defined by the following:
What Linked Folder Structure defines this correctly?
- A. Portfolio,Program,Name.DE:projectType
- B. Portfolio,Program,Name,projectType
- C. Portfolio,Program,project,Program, project Type
正解：B
解説：
In this case, the customer wants to define the linked folder structure based on the Workfront Portfolio name, Program name, Project name, and Project Type. The Project Type is a custom form field with specific choices like "Campaign," "Product Launch," etc.
The correct format to define the folder structure in AEM based on these elements would be:
Portfolio, Program, Name, projectType: This structure will create a hierarchical folder system in AEM where the folders are nested by Portfolio, Program, Project Name, and Project Type (which is pulled from the custom form field).
Option A includes an incorrect syntax with "DE
," which is not necessary, and Option C repeats the "Program" and misorders the fields.
Refer to Workfront Enhanced Connector documentation for further guidance on defining folder structures using custom form fields.
質問 # 56
An implementation consultant wants to configure the enhanced connector inside a customer's Adobe experience Manager environment. The customer has expressed interest in automatically publishing assets when they ore sent from Adobe Workfront to Adobe Experience Manager. The customer does no! have an instance of Brand Portal running.
The customer has a project custom form field with the following details:
The customer wants this automatic publishing to be conditional on the value of the project custom form field being equal to, Yes.
Which option should be used to implement this feature?
- A. Check the option, 'Automatically publish assets when sent from Workfront' In the advanced tab of the configuration properties. In the Custom from field dropdown select. "CUSTOM FORM auto_publiah_asset', and in the Custom from field value text box. write ''Yes".
- B. Check the option, 'Publish all prefect assets to Brand Portal upon project completion.' In the advanced tab of the configuration properties in the Custom form field dropdown select. 'CUSTOM FORMS auto_publish_assets', and in the Custom form field value text box. write "Yes".
- C. Check the option. 'Automatically publish assets when sent from Workflow' in the advanced tab of the configuration properties in the Custom form field dropdown select. "CUSTOM FORMS Automatically Publish Assets'', and in the Custom form field value lent box, write 'Yes''.
正解：A
解説：
To implement conditional automatic publishing of 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 to Workfront for AEM Enhanced Connector documentation for step-by-step guidance on configuring conditional automatic asset publishing.
質問 # 57
......
ベストAdobe AD0-E906学習ガイドと問題集は2025年に更新されました：https://jp.fast2test.com/AD0-E906-premium-file.html