Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Adobe
  5. AD0-E718

Free AD0-E718 Exam Braindumps (page: 3)

Page 2 of 13
PDF with 50 Questions

A company wants to build an Adobe Commerce website to sell their products to customers in their country. The taxes in their country are highly complex and require customization to Adobe Commerce. An Architect is trying to solve this problem by creating a custom tax calculator that will handle the calculation of taxes for all orders in Adobe Commerce. How should the Architect add the taxes for all orders?

  1. Write a before plugin to \Magento\Quote\Model\QuoteManagement::placeOrder() and add the custom tax to the quote
  2. Declare a new total collector in "etc/sales.xml" in a custom module
  3. Add a new observer to the event 'sales_quote_collect_totals_before" and add the custom tax to the quote

Answer(s): B

Explanation:

you can create tax rules in Magento 2 by going to Stores > Taxes > Tax Rules and choosing or adding tax rates. However, this may not be enough for complex tax scenarios that require customization. https://amasty.com/knowledge-base/how-to-configure-tax-calculation-in-magento-2.html To add a new total to the order, the Architect should declare a new total collector in the "etc/sales.xml" file of a custom module. This file defines the order of calculation and rendering of totals. The Architect should also implement a model class that extends \Magento\Quote\Model\Quote\Address\Total\AbstractTotal and overrides the collect() and fetch() methods to handle the logic of adding the custom tax to the quote and order.


Reference:

https://devdocs.magento.com/guides/v2.4/howdoi/checkout/checkout_new_total.html



An Adobe Commerce Architect needs to log the result of a ServiceClass : : ge-Dara method execution after all plugins have executed. The method is public, and there are a few plugins declared for this method. Among those plugins are after and around types, and all have sortOrder specified.
Which solution should be used to meet this requirement?

  1. Declare a new plugin with the sortOrder value higher than the highest declared plugin sortOrder and implement afterGetData method.
  2. Declare a new plugin with the sortOrder value lower than the lowest declared plugin sortOrder and implement aroundGetData method
  3. Declare a new plugin with the sortOrder value higher than the highest declared plugin sortOrder and implement aroundGetData method

Answer(s): C

Explanation:

the sortOrder property from the plugin node declared in di.xml determines the plugin's prioritization when more than one plugin is observing the same method. The Magento\Framework\Interception\PluginListInterface which is implemented by Magento\Framework\Interception\PluginList\PluginList is responsible to define when to call the before, after, and around methods for each plugin.
Therefore, to log the result of a ServiceClass::getData method execution after all plugins have executed, the solution should be:
C. Declare a new plugin with the sortOrder value higher than the highest declared plugin sortOrder and implement aroundGetData method.

https://devdocs.magento.com/guides/v2.3/extension-dev-guide/plugins.html



An Adobe Commerce Architect is asked by a merchant using B2B features to help with a configuration issue.
The Architect creates a test Company Account and wants to create Approval Rules for orders. The Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account.
Which two steps must be taken to fix this issue? (Choose two.)

  1. Set 'Enable Purchase Orders' in the B2B Admin to TRUE
  2. Merchant needs to log out of frontend and then log back in to load new permissions
  3. Set Enable Purchase Orders' on the Company Record to TRUE
  4. Make sure that the 'Purchase Order' payment method is active
  5. Set 'Enable B2B Quote" in the B2B Admin to TRUE

Answer(s): A,C

Explanation:

Enabling Purchase Orders at both the B2B Admin and the Company Record levels is necessary for Approval Rules to appear in the Company section of the Customer Account Menu.
When 'Enable Purchase Orders' is set to TRUE, the system assumes that the company will be making purchases using purchase orders, and the Approval Rules tab becomes visible.

To create Approval Rules for orders, the Architect needs to enable Purchase Orders both in the B2B Admin and on the Company Record. This will allow the Company Administrator to access the Approval Rules tab in the Customer Account Menu and create rules based on various criteria. The Purchase Order payment method and the B2B Quote feature are not required for this functionality.


Reference:

https://docs.magento.com/user-guide/customers/account-dashboard-approval-

rules.html



An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API. The Architect creates a new attribute my_attribute in the admin panel with frontend type select.
Later, the Architect sees that Productinterface already has the field my_atcribute, but returns an mc value. The Architect wants this field to be a new type that contains both option id and label. To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:



After calling command setup:upgrade, the introspection of Productlnterface field xy_attribute remains int.
What prevented the value type of field my_attribute from changing?

  1. The fields of Productlnterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backendjype of product attribute is set for field type.
  2. The interface Productlnterface is already declared in Magento.CatalogGraphQI module. Extending requires use of the keyword -xceni before a new declaration of Productlnterface.
  3. The Magento.CatalogGraphQI module occurs later in sequence than the Magento.GraphQI module and merging output of dynamic attributes schema reader overrides types declared in schema.graphqls

Answer(s): A

Explanation:

According to the Adobe Commerce Developer Guide1, the fields of ProductInterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backend_type of product attribute is set for field type. Therefore, the value type of field my_attribute remains int because it corresponds to the attribute my_attribute that has a frontend type select and a backend_type int.






Post your Comments and Discuss Adobe AD0-E718 exam with other Community members: