CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Adobe
  5. AD0-E906

Free AD0-E906 Exam Braindumps (page: 7)

Page 6 of 15
PDF with 55 Questions

As part of the configuration of the workfront for Experience Manager enhanced connector, the solutions consultant needs to limit the access of the legal team Specifically, the legal team should only have read access to all of the content in Experience Manager. This group of users will solely be working in Workfront. but will have access to Experience Manager via the enhanced connector. The consultant has created a new user group in Experience Manager that includes the members of the legal team that exist in wf-workfront-users.
How should the solution consultant manage their access?

  1. By adding the legal group to the AEM provided Contributors user group
  2. By applying ACEs to the wf-workfront-users user group
  3. By adding the legal user group to the AEM provided Everyone user group

Answer(s): B

Explanation:

In this case, the solutions consultant needs to limit the legal team's access to read-only for all content in AEM. Since the legal team will be working in Workfront and accessing AEM via the enhanced connector, the best way to manage their access is to apply Access Control Entries (ACEs) to the wf-workfront-users user group.
ACEs allow you to specify detailed permissions for a group or user in AEM, such as granting read-only access to specific resources or folders within the DAM. Options A and C would either grant too much access (as in the case of the Everyone user group) or allow contributions, which is beyond the requirement of just reading access. Refer to AEM Access Control Management documentation to learn more about setting up ACEs and managing permissions.



An AEM application must process a high volume of content ingestion on the author server What Is a key factor to optimize a design for overall performance gain for implementing workflows?

  1. Use Schedulers to the workflow only one weekends
  2. Allocate more RAM for the content ingestion up front
  3. Use Transient workflowers

Answer(s): C

Explanation:

When handling high-volume content ingestion in AEM, transient workflows are a key factor for optimizing performance. Transient workflows do not persist workflow data in the JCR repository, which greatly reduces the load on the repository and improves overall performance. Since content ingestion typically involves processing a large number of assets, using transient workflows prevents unnecessary data accumulation in the repository.
Transient workflows are ideal for operations where you don't need to keep historical data about each workflow instance, such as ingestion processes, thereby making the system faster and more efficient. Option A (using schedulers) is not related to workflow performance, and Option B (allocating more RAM) is a generic solution but not directly tied to optimizing workflow efficiency.

For further guidance, refer to AEM's documentation on workflow optimization and transient workflows.



A user applies a custom metadata schema to a folder in AEM Assets However, the user receives an error message. "Unable to edit properties", when trying to save changes to one of the metadata properties for all assets within that folder.
What are two reasons for receiving this message? (Choose two.)

  1. The user does not have the Modify permission allowed for the folder.
  2. The assets in that folder have been check out/locked by another user.
  3. Two or more metadata properties in the schema are mapped to the same path.
  4. The metadata property being modified is mapped to an invalid path.

Answer(s): A,D

Explanation:

There are two possible reasons for receiving the "Unable to edit properties" error when trying to save metadata properties in AEM:
Insufficient Modify Permission: The user needs to have Modify permissions for the folder or assets within the folder to be able to edit the metadata. Without this permission, changes to metadata cannot be saved.
Invalid Metadata Path: If a metadata property in the schema is mapped to an invalid JCR path, AEM will not be able to save the changes. The system requires valid paths in the JCR to store metadata properties correctly, and any invalid path will result in an error. Option B, involving asset locking, would prevent editing altogether rather than giving an error during property saving. Option C, mapping two properties to the same path, would result in overwriting issues rather than an error about saving properties.
For more details, refer to AEM's Metadata Schema documentation and permissions management.



Given the following workflow launcher configuration:



What change should be made to the configuration to trigger the workflow?

  1. Modify the condition to dc ==image/
  2. Modify the path to /content/dam/.<em>/)en(/.<em>/)
  3. Modify the node type to nt:file

Answer(s): A

Explanation:

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.






Post your Comments and Discuss Adobe AD0-E906 exam with other Community members:

AD0-E906 Discussions & Posts