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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E906 Exam - Topic 3 Question 20 Discussion

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?
B) Get the third party library as AEM package form the translation vendor and directly install it to Production environment using CRX Package Manager.
A) Store the package as part of the customer code repository under the <url>file;$(mnven.multiModuleProjectDirectory)/install</url> folder and deploy it using Cloud Manager.
C) Host the package in a remote public or private repository (password protected) and reference it as part of pon.xml so it is included as part of Cloud Manager deployment

Adobe AD0-E906 Exam - Topic 3 Question 20 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

To synchronize comments on linked documents from Adobe Workfront to Adobe Experience Manager, you need to enable Workfront Event Subscriptions in the enhanced connector configuration properties. Event Subscriptions allow AEM to track changes and updates from Workfront, including comment synchronization.

Workfront Event Subscriptions ensure that comments made in Workfront on linked documents are automatically synced to AEM.

Option A incorrectly references the Advanced tab, and Option C incorrectly states 'Unable' instead of 'Enable' Comment Sync.

Refer to AEM Enhanced Connector documentation on Event Subscriptions for step-by-step configuration.


by Shantay at Mar 24, 2025, 05:42 PM

Limited Time Offer

25%

Off

Get Premium AD0-E906 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Irving
8 months ago
A is definitely the way to go for version control!
upvoted 0 times
...
Rory
8 months ago
Wait, can you really use CRX Package Manager in Production?
upvoted 0 times
...
Talia
9 months ago
I feel like storing the package in the repository is the safest way, but I can't recall if it needs to be in a specific folder.
upvoted 0 times
...
Carolann
9 months ago
C is interesting, but is it really secure to host it remotely?
upvoted 0 times
...
Belen
9 months ago
I think option C sounds familiar from our practice questions, where we referenced external packages in the pom.xml.
upvoted 0 times
...
Floyd
9 months ago
I disagree, B is way simpler for quick installs.
upvoted 0 times
...
Wenona
9 months ago
I’m a bit confused about whether we can use CRX Package Manager for production. I thought it was more for development or testing environments.
upvoted 0 times
...
Frederica
10 months ago
Option A seems like the best practice for deployment.
upvoted 0 times
...
Refugia
10 months ago
I remember something about using Cloud Manager for deployments, but I'm not sure if the package should be in the code repository or installed directly.
upvoted 0 times
...
Sena
10 months ago
Based on my understanding, option A is the way to go. Storing the package in the customer's code repository and using Cloud Manager to deploy it seems like the most secure and reliable method. The other options might work, but they don't align as well with the AEM Cloud Service requirements.
upvoted 0 times
...
Xochitl
10 months ago
I'm a bit confused about the difference between options B and C. Can we install the package directly using the CRX Package Manager, or do we need to host it in a remote repository? I want to make sure I choose the right approach.
upvoted 0 times
...
Esteban
10 months ago
The key here is that the package needs to be deployed to the AEM Cloud Service environment. I think option A looks like the best approach since it involves using Cloud Manager, which is the recommended way to deploy to AEM Cloud.
upvoted 0 times
...
Jodi
11 months ago
This seems like a straightforward deployment question, but I want to make sure I understand the requirements correctly before answering.
upvoted 0 times
...
Jules
11 months ago
I think I'd go with option A. Storing the package in the customer's code repo and deploying it through Cloud Manager seems like the most controlled and reliable approach for an AEM Cloud Service environment. The other options have some potential risks that I'd want to avoid.
upvoted 0 times
...
Martin
11 months ago
Option C looks interesting, hosting the package in a remote repository and referencing it in the pom.xml. That could be a good way to manage the deployment, but I'd want to make sure the repository is secure and accessible for the Cloud Manager deployment.
upvoted 0 times
...
Julieta
11 months ago
Hmm, I'm a bit unsure about this one. Option B seems simpler, but I'm not sure if directly installing the package in production is the best approach for an AEM Cloud Service environment. I'll need to think this through a bit more.
upvoted 0 times
...
Cary
11 months ago
This seems straightforward - I'd go with option A and deploy the package as part of the customer's code repository. That way it's version-controlled and can be easily deployed through Cloud Manager.
upvoted 0 times
...
Teddy
1 year ago
Lol, can you imagine if the vendor's package was filled with malware? That would be a real translation nightmare!
upvoted 0 times
Lashaun
1 year ago
User 3: I agree, we can't take any chances with third party packages.
upvoted 0 times
...
Mammie
1 year ago
User 2: Definitely, we should follow the proper deployment steps to avoid any risks.
upvoted 0 times
...
Raylene
1 year ago
User 1: That would be a disaster! We need to make sure the deployment process is secure.
upvoted 0 times
...
...
Sharmaine
1 year ago
Wait, we can't just 'directly install' stuff to production? Oops, my bad. Cloud Manager it is!
upvoted 0 times
Pansy
1 year ago
A: Wait, we can't just 'directly install' stuff to production? Oops, my bad. Cloud Manager it is!
upvoted 0 times
...
Nikita
1 year ago
C: Host the package in a remote public or private repository (password protected) and reference it as part of pon.xml so it is included as part of Cloud Manager deployment
upvoted 0 times
...
Elin
1 year ago
B: Get the third party library as AEM package form the translation vendor and directly install it to Production environment using CRX Package Manager.
upvoted 0 times
...
Yolande
1 year ago
A: Store the package as part of the customer code repository under the file;$(mnven.multiModuleProjectDirectory)/install folder and deploy it using Cloud Manager.
upvoted 0 times
...
...
Viki
1 year ago
A package installed directly to production? That doesn't sound too safe. I'd go with the Cloud Manager deployment, just to be on the safe side.
upvoted 0 times
Kenny
1 year ago
A package installed directly to production? That doesn't sound too safe. I'd go with the Cloud Manager deployment, just to be on the safe side.
upvoted 0 times
...
Brandee
1 year ago
A) Store the package as part of the customer code repository under the file;$(mnven.multiModuleProjectDirectory)/install folder and deploy it using Cloud Manager.
upvoted 0 times
...
...
Marylin
1 year ago
Hmm, I think option C sounds the most reliable and maintainable. Hosting it in a private repo seems like the way to go.
upvoted 0 times
...
Margart
1 year ago
That's a good point, Mireya. Hosting the package externally could make it easier to manage updates and dependencies. I see the benefits of that approach now.
upvoted 0 times
...
Mireya
1 year ago
I disagree, I believe option C is the way to go. Hosting the package in a remote repository and referencing it in the pon.xml file for Cloud Manager deployment provides more flexibility and control.
upvoted 0 times
...
Beatriz
1 year ago
I'm not sure about the deployment strategy, but I hope the vendor's package is well-documented and secure!
upvoted 0 times
Serina
1 year ago
A: As long as the vendor's package is well-documented and secure, we should be good to go.
upvoted 0 times
...
Ashton
1 year ago
C: Hosting the package in a remote repository and referencing it in pom.xml also sounds like a good option.
upvoted 0 times
...
Deeanna
1 year ago
B: I agree, storing it in the customer code repository and deploying it using Cloud Manager seems secure.
upvoted 0 times
...
Kristine
1 year ago
A: Option A sounds like the best way to deploy the third party library onto AEM Cloud Service.
upvoted 0 times
...
...
Margart
1 year ago
I think option A is the best choice. Storing the package in the customer code repository and deploying it using Cloud Manager seems like a secure and efficient method.
upvoted 0 times
...

Save Cancel