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-E716 Exam - Topic 3 Question 40 Discussion

An Adobe Commerce developer is tasked with adding custom data to orders fetched from the API. While keeping best practices in mind, how would the developer achieve this?
C) Create a before plugin on Magento\sales\model\ResourceModel\order\collection: :load and alter the query to fetch the additional data. Data will then be automatically added to the items fetched from the API.
A) Create an extension attribute on Nagento\sales\Api\E)ata\orderinterface and an after plugin on Magento\Sales\Model\Order: :getExtensionAttributes() to add the custom data.
B) Create an extension attribute On Magento\Sales\Api\Data\OrderInterface and an after plugin On Magento\Sales\Api\OrderRepositoryInterface On geto and getListo to add the custom data.

Adobe AD0-E716 Exam - Topic 3 Question 40 Discussion

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

An Adobe Commerce developer is tasked with adding custom data to orders fetched from the API. While keeping best practices in mind, how would the developer achieve this?

Show Suggested Answer Hide Answer
Suggested Answer: C

The type of environment that will be provisioned when launching the CLI for Commerce command magento-cloud environment:branch <environment-name> is an integration environment with the code and database from the parent environment. Integration environments are temporary environments that are used for testing and development purposes on the Adobe Commerce Cloud platform. They can be created from any branch of code and have their own dedicated database and services. When creating an integration environment using the CLI for Commerce command, the code and database from the parent environment are copied to the new integration environment, creating an exact replica of the parent environment. Verified Reference: [Magento 2.4 DevDocs]


by Shaun at Jan 25, 2025, 01:53 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dawne
7 months ago
Is it really necessary to use plugins for this? Seems overkill.
upvoted 0 times
...
Dorthy
7 months ago
Totally agree with B, it’s cleaner and more efficient!
upvoted 0 times
...
Dorthy
7 months ago
Wait, C sounds risky. Altering the query could cause issues.
upvoted 0 times
...
Roosevelt
7 months ago
I think A is better, more straightforward.
upvoted 0 times
...
Joesph
7 months ago
Option B is the way to go for best practices!
upvoted 0 times
...
Remedios
8 months ago
I’m a bit confused about the difference between the after and before plugins. I hope I can recall the right one during the exam!
upvoted 0 times
...
Asha
8 months ago
I feel like using a before plugin might not be the best practice since it could affect performance. I’m leaning towards option A.
upvoted 0 times
...
Chaya
8 months ago
I think option B sounds familiar; we practiced something similar where we added custom data to the order repository.
upvoted 0 times
...
Glory
8 months ago
I remember we discussed extension attributes in class, but I'm not sure if the after plugin is the right approach for this scenario.
upvoted 0 times
...
Cordelia
8 months ago
I'm feeling pretty confident about this one. The key is to use extension attributes to extend the order data, and then leverage plugins to inject the custom data. Shouldn't be too difficult to implement.
upvoted 0 times
...
Stephen
8 months ago
Okay, I think I've got a strategy. I'll create an extension attribute on the OrderInterface and use an after plugin on the OrderRepositoryInterface to add the custom data. That should do the trick while following best practices.
upvoted 0 times
...
Eliseo
8 months ago
Hmm, I'm a bit confused by the different plugin options. I'll need to double-check the differences between after, before, and around plugins.
upvoted 0 times
...
Leota
8 months ago
This looks like a tricky one. I'll need to review the Magento API documentation carefully to understand the different options and best practices.
upvoted 0 times
...
Nelida
1 year ago
Option A sounds like the way to go. Extending the API interface is the cleanest approach, and the after plugin is a nice way to encapsulate the custom data injection.
upvoted 0 times
Tyra
1 year ago
Yes, extending the API interface and using a plugin is a clean way to add custom data to orders.
upvoted 0 times
...
Adela
1 year ago
I agree, creating an extension attribute and using an after plugin is a good practice.
upvoted 0 times
...
Precious
1 year ago
I think option A is the best choice. It keeps the code clean and organized.
upvoted 0 times
...
...
Nana
1 year ago
Option A all the way! Clean, extensible, and follows best practices. Plus, it's the easiest to maintain in the long run.
upvoted 0 times
...
Percy
1 year ago
Haha, Option C is a bit of a hack, isn't it? Altering the collection query directly? That's a bit too much work if you ask me.
upvoted 0 times
Emiko
1 year ago
Clay: Definitely, it's important to follow best practices when working with APIs.
upvoted 0 times
...
Tommy
1 year ago
Geraldo: Definitely, it's important to maintain good coding standards.
upvoted 0 times
...
Clay
1 year ago
User 2: I agree, it follows best practices and keeps the code clean.
upvoted 0 times
...
Geraldo
1 year ago
User 2: I agree, it follows best practices and keeps the code clean.
upvoted 0 times
...
Verona
1 year ago
User 1: Option A seems like the best approach, creating an extension attribute and using an after plugin.
upvoted 0 times
...
Twana
1 year ago
User 1: Option A seems like the best approach, creating an extension attribute and using an after plugin.
upvoted 0 times
...
...
Chauncey
1 year ago
I was considering Option B, but you're right, Option A is probably the more robust solution. Extending the API interface is a better practice than modifying the repository.
upvoted 0 times
...
Karan
1 year ago
I personally prefer option B because it involves creating an extension attribute on the order interface and using an after plugin on the order repository interface. This way, the custom data can be easily accessed when fetching orders from the API.
upvoted 0 times
...
Tammara
1 year ago
I agree with Franklyn. Option A follows best practices and ensures that the custom data is added in a clean and efficient way.
upvoted 0 times
...
Lindsey
1 year ago
Option A seems the best approach to me. Extending the OrderInterface is the recommended way to add custom data, and using an after plugin on getExtensionAttributes() is a clean way to inject it.
upvoted 0 times
Ashton
1 year ago
User 2: I agree, it's the recommended approach for adding custom data to orders fetched from the API.
upvoted 0 times
...
Carmelina
1 year ago
User 1: I think option A is the way to go. Extending the OrderInterface and using an after plugin seems clean.
upvoted 0 times
...
...
Franklyn
1 year ago
I think option A is the best approach because it involves creating an extension attribute on the order interface and using an after plugin to add custom data.
upvoted 0 times
...

Save Cancel