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 1 Question 22 Discussion

An Adobe Commerce developer is creating a new module to extend the functionality of the cart. The module is installed in app/code/CompanyName/ModuleName/.How would an Adobe Commerce developer extend the existing CartltemPrices GraphQL schema to include a custom base_price field?
B) Add the following to the module's etc/schema.graphqis file:
A) Create and Configure a for Hagento\QuoteGraphQl\Model\Resolver\CartItemPrices that adds the base_price field in the resolve() function.
C) Add the following to the module's etc/graphqi/di.xmi file:

Adobe AD0-E716 Exam - Topic 1 Question 22 Discussion

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

An Adobe Commerce developer is creating a new module to extend the functionality of the cart. The module is installed in app/code/CompanyName/ModuleName/.

How would an Adobe Commerce developer extend the existing CartltemPrices GraphQL schema to include a custom base_price field?

Show Suggested Answer Hide Answer
Suggested Answer: B

The developer can deal with this issue by modifying the admin path timeout value in seconds in the Fastly Configuration section > Advanced Configuration in the Admin Panel. Fastly is a cloud-based caching service that improves site performance and security for Adobe Commerce Cloud projects. Fastly has a default timeout value of 180 seconds for admin requests, which means that any request that takes longer than 180 seconds will be terminated and result in a timeout error. The developer can increase this value to allow longer processing time for admin requests without causing errors. The developer also needs to save the configuration and upload VCL to Fastly to apply the changes. Verified Reference: [Magento 2.4 DevDocs]


by Truman at May 20, 2024, 03:22 AM

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
Cherelle
10 months ago
B is definitely the correct choice here!
upvoted 0 times
...
Allene
10 months ago
Definitely not C, that doesn't seem right.
upvoted 0 times
...
Annelle
10 months ago
Surprised there's no mention of caching issues with these changes!
upvoted 0 times
...
Shonda
10 months ago
I think A makes more sense for extending functionality.
upvoted 0 times
...
Susana
11 months ago
Option B is the way to go!
upvoted 0 times
...
Stephaine
11 months ago
I have a vague memory of using di.xml for dependency injection, but I'm not confident it applies here for adding a base_price field.
upvoted 0 times
...
Teri
11 months ago
I practiced a similar question about adding fields to GraphQL, and I feel like the schema.graphql file is definitely where we define new fields.
upvoted 0 times
...
Candra
11 months ago
I think option A sounds familiar, but I can't recall if the resolve() function is the right place to add new fields.
upvoted 0 times
...
Margurite
11 months ago
I remember we discussed extending GraphQL schemas in class, but I'm not entirely sure if it's the schema.graphql or di.xml file that needs the changes.
upvoted 0 times
...
Rosenda
11 months ago
This seems straightforward enough. I think the schema.graphql approach is the way to go here. I'll need to carefully craft the field definition and make sure it integrates properly with the existing CartItemPrices schema.
upvoted 0 times
...
Lilli
11 months ago
I'm a bit confused on the difference between the schema.graphql and di.xml approaches. I'll need to research the pros and cons of each to determine the most appropriate solution for this scenario.
upvoted 0 times
...
Judy
11 months ago
Okay, let's think this through step-by-step. I believe the key is to either create a new resolver or update the existing one to include the custom base_price field. I'll need to check the module structure and GraphQL schema to determine the best way to approach this.
upvoted 0 times
...
Hana
11 months ago
Hmm, I'm not too familiar with extending the CartItemPrices schema in Adobe Commerce. I'll need to review the documentation carefully to make sure I understand the right approach.
upvoted 0 times
...
Lavonda
11 months ago
This looks like a pretty straightforward GraphQL extension question. I think I can handle this one.
upvoted 0 times
...
Maira
12 months ago
Oof, this is a lot to keep track of. Rollup summary fields, validation rules, duplicate rules - I'll need to map out how all of those pieces fit together and how they might impact the trigger. Gonna have to really focus on this one.
upvoted 0 times
...
Geraldine
12 months ago
Hmm, I'm a bit confused on this one. I know there are multiple phases in the PKI life-cycle, but I can't quite recall the specific order. I'll have to think this through carefully.
upvoted 0 times
...
Tish
12 months ago
Product options seem irrelevant here. I definitely remember discussing how lead times affect customer satisfaction in class.
upvoted 0 times
...
Broderick
1 year ago
Option A is the way to go. Extending the resolver is the standard way to add custom fields to a GraphQL schema. I'm glad I've been studying my GraphQL best practices for this exam.
upvoted 0 times
Vivan
1 year ago
Good job on studying your GraphQL best practices, it's paying off!
upvoted 0 times
...
Jovita
1 year ago
Option A is the way to go. Extending the resolver is the standard way to add custom fields to a GraphQL schema. I'm glad I've been studying my GraphQL best practices for this exam.
upvoted 0 times
...
Zack
1 year ago
A) Create and Configure a preference for Magento\\QuoteGraphQl\\Model\\Resolver\\CartItemPrices that adds the base_price field in the resolve() function.
upvoted 0 times
...
Sheldon
1 year ago
Definitely, it's important to follow the standard way of extending the resolver for custom fields.
upvoted 0 times
...
Susana
1 year ago
I agree, extending the resolver is the best practice for adding custom fields to a GraphQL schema.
upvoted 0 times
...
...
Noble
1 year ago
Haha, I bet the developers at Adobe are laughing at us for even considering Option B and C. Those look like they were generated by a random JSON generator or something!
upvoted 0 times
...
Tommy
1 year ago
I'm not sure about the correct answer, but Option B and C both look like they involve modifying configuration files, which doesn't seem like the right approach for extending a GraphQL schema.
upvoted 0 times
Abel
1 year ago
C) Add the following to the module's etc/graphql/di.xml file.
upvoted 0 times
...
Magnolia
1 year ago
B) Add the following to the module's etc/schema.graphqls file.
upvoted 0 times
...
Noe
1 year ago
A) Create and Configure a preference for Magento\\QuoteGraphQl\\Model\\Resolver\\CartItemPrices that adds the base_price field in the resolve() function.
upvoted 0 times
...
...
Shawn
1 year ago
Option A is the correct way to extend the existing CartItemPrices GraphQL schema. Creating a preference and adding the base_price field in the resolve() function is the proper way to extend the existing schema.
upvoted 0 times
Dortha
1 year ago
User 2: Yes, that's right. It's important to extend the schema properly.
upvoted 0 times
...
Eva
1 year ago
User 1: I think the correct way is to create a preference for CartItemPrices and add the base_price field in the resolve() function.
upvoted 0 times
...
...
Corinne
1 year ago
Hmm, I see your point. But I still think A) makes more sense because it directly modifies the resolve() function.
upvoted 0 times
...
Latia
1 year ago
I disagree, I believe the correct answer is B) Add the following to the module's etc/schema.graphql file.
upvoted 0 times
...
Corinne
1 year ago
I think the answer is A) Create and Configure a preference for Magento\\QuoteGraphQl\\Model\\Resolver\\CartItemPrices.
upvoted 0 times
...

Save Cancel