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

Free AD0-E718 Exam Braindumps (page: 6)

Page 5 of 13
PDF with 50 Questions

A third-party company needs to create an application that will integrate the Adobe Commerce system to get orders data for reporting. The integration needs access to the get /vi/orders endpoint. It will call this endpoint automatically every hour around the clock. The merchant wants the ability to restrict or extend access to resources as well as to revoke the access using Admin Panel.
Which type of authentication available in Adobe Commerce should be used and implemented in a third-party system for this integration?

  1. Use token-based authentication to obtain the Admin Token. The third-party system will utilize the REST endpoint using the admin username and password to get the Admin Token, which will be used as the Bearer Token to authorize.
  2. Use OAuth-based authentication to provide access to system resources. Integration will be registered by the merchant in the panel an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize.
  3. Use token-based authentication to obtain an Integration Token. Integration will be created and activated in the admin panel using default integration token settings to get access to the token, which will be used as the Bearer Token to authorize.

Answer(s): B

Explanation:

To create an application that will integrate the Adobe Commerce system to get orders data for reporting using the get /v1/orders endpoint, you should use OAuth-based authentication to provide access to system resources. OAuth is a token-passing mechanism that allows a system to control which third-party applications have access to internal data without revealing or storing any user IDs or passwords. The integration will be registered by the merchant in the admin panel and will perform an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize. The merchant will have the ability to restrict or extend access to resources as well as to revoke the access using Admin Panel.


Reference:

1
1: https://devdocs.magento.com/guides/v2.3/get-started/authentication/gs-authentication- oauth.html



An Adobe Commerce Architect designs a data flow that contains a new product type with its own custom pricing logic to meet a merchant requirement.
Which three developments are valid when reviewing the implementation? (Choose three.)

  1. Content of the etc/product_types.xml file
  2. Hydrator for attributes belonging to the new product type
  3. Custom type model extended from the abstract Product Type model
  4. A new class with custom pricing logic, extending the abstract Product model class
  5. Data patch to register the new product type
  6. New price model extending \Magento\Catalog\Model\Product\Type\Price

Answer(s): A,C,F

Explanation:

To create a new product type with its own custom pricing logic, you need to consider the following developments:
Content of the etc/product_types.xml file. This file will define the name, label, modelInstance, and priceModel of the new product type. The modelInstance will specify the custom type model that extends from the abstract Product Type model. The priceModel will specify the new price model that extends \Magento\Catalog\Model\Product\Type\Price.
Custom type model extended from the abstract Product Type model. This model will implement the logic and behavior of the new product type, such as how to prepare product for cart, how to process buy request, how to check product options, etc.
New price model extended \Magento\Catalog\Model\Product\Type\Price. This model will implement the custom pricing logic for the new product type, such as how to calculate final price, tier price, minimal price, etc.


Reference:

1
1: https://meetanshi.com/blog/create-custom-product-type-in-magento-2/



A merchant asks for a new category attribute to allow uploading an additional mobile image against categories. The merchant utilizes the content staging and preview feature in Adobe Commerce and wants to schedule and review changes to this new mobile image field. A developer creates the attribute via a data patch and adds it to view/adminhtml/ui_component/category_form.xml. The attribute appears against the category in the main form, but does not appear in the additional form when scheduled updates are made. To change this attribute when scheduling new category updates, which additional action should the Architect ask the developer to take?

  1. The attribute must have its apply_to field set to "staging" in the data patch file.
  2. The attribute must also be added to view/adminhtml/ul_component/catalogstaging_category_update_form.xml.
  3. The attribute must have<item name=''allow_staging'' xsi:type="boolean''>true<item> set in the =category_form.xml file under the attributes config" section.

Answer(s): B

Explanation:

This is because, in order to change the attribute when scheduling new category updates, the attribute must be added to the view/adminhtml/ulcomponent/catalogstagingcategoryupdateform.xml file in order to be displayed in the additional form when scheduling updates. This additional form is used to set the values for the category attributes when scheduling updates.
To change the new category attribute when scheduling new category updates, you need to add the attribute to view/adminhtml/ui_component/catalogstaging_category_update_form.xml. This file defines the form fields that appear in the Schedule New Update form for categories. By adding the attribute to this file, you will be able to schedule and review changes to the new mobile image field using the content staging and preview feature in Adobe Commerce.


Reference:

1
1: https://docs.magento.com/user-guide/v2.3/cms/content-staging-category.html



An Adobe Commerce store owner sets up a custom customer attribute "my.attribute" (type int). An Architect needs to display customer-specific content on the home page to Customers with "my.attribute" greater than 3. The website is running Full Page Cache. Using best practices, which two steps should the Architect take to implement these requirements? (Choose two.)

  1. Use customer-data JS library to retrieve "my.attribute" value
  2. Add a new context value of "my.attribute" to Magento\Framework\App\Http\Context
  3. Add a custom block and a phtml template with the content to the cmsjndexjndex.xml layout
  4. Create a Customer Segment and use "my.attribute" in the conditions
  5. Add a dynamic block with the content to the Home Page

Answer(s): A,C

Explanation:

To display customer-specific content on the home page to Customers with "my.attribute" greater than 3, you need to use the following steps:
Use customer-data JS library to retrieve "my.attribute" value. The customer-data JS library allows you to access the customer data stored in the local storage of the browser. You can use the get() method to get the value of "my.attribute" for the current customer. Add a new context value of "my.attribute" to Magento\Framework\App\Http\Context. The HTTP context is a mechanism that allows you to vary the cache of a page based on some parameters. By adding a new context value of "my.attribute", you can cache separate versions of the home page for customers with different values of "my.attribute".
Add a custom block and a phtml template with the content to the cms_index_index.xml layout. This step will create a block that will display the customer-specific content on the home page. You can use the phtml template to check the value of "my.attribute" and render the content accordingly.


Reference:

: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/cache/page-caching/public- content.html :
https://devdocs.magento.com/guides/v2.3/howdoi/checkout/checkout_customize.html






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

AD0-E718 Discussions & Posts