Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E906 Topic 3 Question 16 Discussion

Actual exam question for Adobe's AD0-E906 exam
Question #: 16
Topic #: 3
[All AD0-E906 Questions]

An implementation consultant needs to configure metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties. Which Iwo types of custom forms can the implementation consultant use to define these mappings? (Choose two)

Show Suggested Answer Hide Answer
Suggested Answer: A, B

When configuring metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties, you can use Issue and Document custom forms to define these mappings. These types of forms are commonly used for tracking and managing work items and documents, both of which need to have their metadata synchronized between the two systems.

Issue custom forms: Used for tracking work requests, such as issues or tasks.

Document custom forms: Specifically used for managing metadata related to documents, which can be mapped directly to AEM assets.

Options C (Portfolio) and D (Program) are not typically used for metadata mapping related to assets or documents.

Refer to Workfront Enhanced Connector documentation for more information on mapping custom forms to AEM metadata properties.


Contribute your Thoughts:

Cristy
1 days ago
I agree with Fausto. Document and Portfolio custom forms make sense for defining mappings between Adobe Workfront and Adobe Experience Manager.
upvoted 0 times
...
Fausto
5 days ago
I think the implementation consultant can use Document and Portfolio custom forms for the mappings.
upvoted 0 times
...
Corazon
5 days ago
Haha, I love how they're trying to trip us up with this one. Obviously the answer is B and D - you can't map custom forms to issues or portfolios, that would be crazy! Although I did once have a boss who thought we could use custom forms to track the progress of his daily sandwich orders. Talk about metadata overload...
upvoted 0 times
...
Precious
8 days ago
I'm going with B and D as well. Mapping custom forms to AEM metadata seems like a pretty straightforward task, and those two options just make the most sense to me. Although I do have to wonder - why is there no 'All of the above' option? That's usually the safest bet on these exams!
upvoted 0 times
...
Whitley
10 days ago
Hmm, I think the answer is B and D. You can definitely map custom form fields to metadata in AEM for documents, and I'm pretty sure you can do it for programs too. Although I'm not sure why they'd have us choose programs over portfolios - maybe the consultants just really hate portfolios, who knows?
upvoted 0 times
Adelle
2 days ago
Yeah, I agree. It makes sense to map custom form fields for documents and programs in this case.
upvoted 0 times
...
Kaycee
5 days ago
I think you're right, B and D are the correct options for mapping custom form fields to metadata in AEM.
upvoted 0 times
...
...

Save Cancel