Adobe AD0-E722 Exam - Topic 4 Question 21 Discussion

Actual exam question for Adobe's AD0-E722 exam

Question #: 21
Topic #: 4

An Architect needs to integrate an Adobe Commerce store with a new Shipping Carrier. Cart data is sent to the Shipping Carrier's API to retrieve the price and display to the customer. After the feature is implemented on the store, the API hits its quota and returns the error "Too many requests". The Shipping Carrier warns the store about sending too many requests with the same content to the API.

In the carrier model, what should the Architect change to fix the problem?

Aln_doShipmentRequest()f call canCollectRates() before sending request to the API.

BOverride getResponse, save the response to a variable, check if the response exists, then return.

CImplement _setCachedQuotes() and _getCachedQuotes(), return the data if the request matches.

Show Suggested Answer

Suggested Answer: B, C, E

The Architect can take the following steps to ensure validation of the configuration files with unique validation rules for the individual and merged files:

Create validation rules in marketplace.schema.xsd. This file defines the structure and constraints of the XML elements and attributes for the marketplace.feeds.xml configuration file. The Architect can use this file to specify the required and optional elements, data types, values, and patterns for the configuration file.

Provide schema to validate a merged file. This schema is used to validate the final configuration file that is generated after merging all the individual configuration files from different modules. The Architect can use this schema to check the consistency and completeness of the merged configuration file.

Provide schema to validate an individual file. This schema is used to validate each individual configuration file from each module before merging them. The Architect can use this schema to check the syntax and validity of each configuration file.

by Twila at Jul 10, 2024, 08:56 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Mattie

3 months ago

Can we really trust caching to solve the problem? Sounds risky.

upvoted 0 times

...

Stefany

3 months ago

Wow, I didn't realize APIs had such strict quotas!

upvoted 0 times

...

Leah

3 months ago

Not sure about B, seems a bit complicated for this issue.

upvoted 0 times

...

Phuong

4 months ago

I think A is a solid choice too, checking before sending is smart.

upvoted 0 times

...

Florinda

4 months ago

Option C seems like the best way to cache responses.

upvoted 0 times

...

Marylin

4 months ago

C sounds familiar because caching seems to be a common strategy in these scenarios. I just hope I remember the implementation details correctly!

upvoted 0 times

...

Paola

4 months ago

I feel like we practiced a similar question where we had to manage API requests. I think saving the response like in option B could also be a solution, but I'm not confident.

upvoted 0 times

...

Polly

4 months ago

I'm not entirely sure, but I think we discussed using canCollectRates() in class. That might help with the request issue, so option A could be worth considering.

upvoted 0 times

...

Susana

5 months ago

I remember something about caching responses to avoid hitting API limits, so maybe option C is the right choice?

upvoted 0 times

...

Thurman

5 months ago

This seems like a good opportunity to demonstrate my understanding of caching and API rate limiting. I think option C is the way to go, but I'll double-check the details to make sure I'm not missing anything.

upvoted 0 times

...

Alba

5 months ago

I'm a bit confused by the wording of the question. I'll need to re-read it a few times to make sure I'm understanding the problem correctly before I can decide on the best approach.

upvoted 0 times

...

Dean

5 months ago

Okay, let me think this through. I'm leaning towards option C, which talks about implementing caching for the quotes. That could help reduce the number of API calls and avoid hitting the quota.

upvoted 0 times

...

Donte

5 months ago

Hmm, the key here seems to be the issue with the API hitting its quota. I think the solution might involve some kind of caching or rate limiting to prevent too many requests.

upvoted 0 times

...

Roxane

5 months ago

This seems like a tricky one. I'll need to carefully read through the question and options to make sure I understand the problem and the potential solutions.

upvoted 0 times

...

Cristy

5 months ago

Hmm, I'm a bit confused by the wording here. I'll need to re-read the question a few times and make sure I understand what it's asking for exactly.

upvoted 0 times

...

Kallie

5 months ago

Hmm, I remember something similar from our case study. Was it Total Product Value? I just can't recall.

upvoted 0 times

...

Carin

10 months ago

I'm leaning towards option C as well. Caching the quotes just seems like the most logical and maintainable solution. Plus, it'll keep the Shipping Carrier happy and prevent any more diva-like behavior from them.

upvoted 0 times

...

Aretha

10 months ago

Haha, the Shipping Carrier sounds like a real drama queen, warning the store about too many requests. Option A seems like the easiest fix, but who knows, maybe the Architect is feeling spicy and wants to go with the caching approach in option C.

upvoted 0 times

Eloisa

8 months ago

I think option C could be a good long-term solution to prevent hitting the API quota in the future.

upvoted 0 times

...

Stevie

8 months ago

Yeah, I think the Architect should go with option A to avoid any more drama from the Shipping Carrier.

upvoted 0 times

...

Rory

8 months ago

I agree, the Shipping Carrier is being a bit dramatic. Option A does seem like the simplest solution.

upvoted 0 times

...

Goldie

10 months ago

I'm feeling option B. Overriding the getResponse method and checking if the response exists before returning it sounds like a solid solution. Might be a bit more work, but it could give us better control over the API interactions.

upvoted 0 times

Aretha

9 months ago

I think it's worth the extra work to have more control over how we interact with the API.

upvoted 0 times

...

Coral

9 months ago

User 3: Yeah, having better control over the requests sent to the API could prevent the 'Too many requests' error in the future.

upvoted 0 times

...

Leatha

9 months ago

Yeah, it might take a bit more effort to implement, but it could prevent hitting the quota limit.

upvoted 0 times

...

Gilma

9 months ago

User 2: Agreed, it might require some extra work but it could help us manage the API interactions more effectively.

upvoted 0 times

...

Glenn

9 months ago

I agree, option B seems like a good way to handle the API quota issue.

upvoted 0 times

...

Raylene

9 months ago

User 1: I think option B is a good choice. Checking the response before returning it could prevent hitting the API quota.

upvoted 0 times

...

Karrie

10 months ago

Option C seems like the way to go. Caching the quotes will help reduce the number of API calls and prevent hitting the quota. Plus, it's a more efficient approach compared to the other options.

upvoted 0 times

Twanna

9 months ago

User 2: Yeah, it's a smart way to prevent hitting the quota and improve efficiency.

upvoted 0 times

...

Judy

10 months ago

User 1: I agree, caching the quotes will definitely help with reducing the number of API calls.

upvoted 0 times

...

Ruthann

10 months ago

I see both points, but I think option B) might also work. By saving the response and checking its existence before returning, we can prevent hitting the quota.

upvoted 0 times

...

Shayne

11 months ago

I disagree, I believe option C) is the way to go. By implementing cached quotes, we can retrieve the data without making unnecessary requests to the API.

upvoted 0 times

...

Isaac

11 months ago

I think option A) is the best choice. By checking if rates can be collected before sending the request, we can avoid hitting the API quota.

upvoted 0 times

...