An Architect wants to create an Integration Test that does the following:
* Adds a product using a data fixture
* Executes $this->someLogic->execute($product) on the product
* Checks if the result is true.
$this->someLogic has the correct object assigned in the setup() method.
Product creation and the tested logic must be executed in the context of two different store views with IDs of 3 and 4, which have been created and are available for the test.
How should the Architect meet these requirements?

• A.Create two test classes with one test method each. Use the @magentoExecuteinstoreContext 3 and
  $MagentoExecuteinStoreContext 4 annotations on the class level.
• B.Create one test class with two test methods. Use the emagentostorecontext 3 annotation in one method and amagentostorecontext 4 in the other one.
• C.Create one test class with one test method. Use the
  \Magento\TestFramework\store\ExecuteinstoreContext class once in the fixture and another time in the test.

Comment: *

Name: *

Email: *

Verification: *

An Adobe Commerce Architect needs to scope a bespoke news section for a merchants Adobe Commerce storefront. The merchant's SEO agency requests that the following URL structure:
news/{date}/{article_url_key}, where {date} is the publication date of the article, and {article_url_key} is the URL key of the article.
The Architect scopes that a news entity type will be created. The date and URL key data will be stored against each record and autogenerated on save. The values will be able to be manually overridden.

• A.The Architect needs to manage routing this functionality and adhere to best practice. Which two options should the Architect consider to meet these requirements? (Choose two.)
• B.Create a standard controller route and mapping the internal URLs (such as news/article/view/id/i) to rewrites that are generated on save and then stored in the URL rewrites table.
• C.Create a custom router that runs before the standard router and matches the news portion of the URL, then looks for and loads a news article by matching the date and URL key parts of the URL
• D.Create a plugin that intercepts Magento\Framework\App\Action: :(), looks for the news portion of the URL, and if it matches, loads the relevant news article by matching the URL date and URL key parts.
• E.Create a standard controller route and an index/index controller class that loads the relevant news article by matching the URL date and URL key parts.

Comment: *

Name: *

Email: *

Verification: *

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.
Following best practices, how should the Architect add the taxes for all orders?

• A.Add a new observer to the event sales.quote.collecLtotals.before'' and add the custom tax to the quote
• B.Write a before plugin to \Magento\Quote\Model\QuoteManagement::placeOrder() and add the custom tax to the quote
• C.Declare a new total collector in "etc/sales.xmr in a custom module

Comment: *

Name: *

Email: *

Verification: *

An Adobe Commerce Architect designs and implements functionality that introduces a new Complex Product Type to the existing Adobe Commerce website. Besides visual demonstration of the new product type, the changes include adjustments to the price index.
The website utilizes a multi-dimensional indexer feature to store the price index. The Architect decides to cover it with integration tests. After creating and running one test, the Architect discovers that database storage is not being fully cleaned.
The test method has the following annotation declaration:

Which adjustment should the Architect make to fix this issue?

• A.Add annotation @magentoApplsolation enabled to method PHPDoc
• B.Modify method PHPDoc and change annotation @magentoDbIsolation to enabled
• C.Create Customer_ProductType: :Test/_files/{fixture_name)_rollback.php for every fixture

Comment: *

Name: *

Email: *

Verification: *

An Architect working on a headless Adobe Commerce project creates a new customer attribute named my_attribute. Based on the attribute value of the customer, the results of GraphQI queries are modified using a plugin. The frontend application is communicating with Adobe Commerce through Varnish by Fastly. which is already caching the queries that will be modified. The Adobe Commerce Fastly extension is installed, and no other modifications are made to the application.
Which steps should the Architect take to make sure the vcl_hash function of Varnish also considers the newly created attribute?

• A.Create a new ClaSS inheriting from
  Magento\GraphQlCache\Model\CacheId\CacheIdFactorProvidftrInterface and returning the Value of my_attribute from the getFactorValuefunction and my_attribute from the getFactorName function. Then add this class through Dl to the idFactorProviders array ofMagento\GraphQlCache\Model\CacheId\CacheIdCalculator.
• B.Createa new class inheriting from Magento\Framework\GraphQi\Query\Resolver\identityinterfaca and returning the value of my_attributefrom the getidentities function.
  Then specify a ecache(cacheidentity: Path\\To\\identityclass) directive for each GraphQL query to include the newly created IdentityClass to each query that adds the cache tags for each customer.
• C.Create a new class inheriting from Magento\customer\customerData\stctionSourceinterface and returning the value of my_attributefrom the getSectionData function. Then add thisClaSS through the sectionSourceMap array Of Magento\Customer\CustomerData\SectionPoolInterface.

Comment: *

Name: *

Email: *

Verification: *