Question 1

A merchant notices that product price changes do not update on the storefront.

The index management page in the Adobe Commerce Admin Panel shows the following:

* All indexes are set to 'update by schedule'

* Their status is 'ready'

* There are no items in the backlog

* The indexes were last updated 1 minute ago

A developer verifies that updating and saving product prices adds the relevant product IDs into the catalog_product_price_cl changelog table.

Which two steps should the Architect recommend to the developer to resolve this issue? (Choose two.)

AInvalidate the catalog_product_price indexer in the Adobe Commerce Admin Panel so that it is fully reindexed next time the cron runs.

BManually reindex the catalog_product_price index from the Command line:bin\magentor indexer:reindex catalog_product_price.

CMake sure that no custom or third-party modules modify the changelog and indexing process.

DMake sure that the version_id for the price indexer in the mview_state table is not higher than the last entry for the same column in the changelog table and re-synchronize.

EReduce the frequency of the cron job to 5 minutes so the items have more time to process.

Answer : C, D

To resolve the issue of product price changes not updating on the storefront, you need to take the following steps:

Make sure that no custom or third-party modules modify the changelog and indexing process. Some modules might interfere with the normal functioning of the indexing mechanism and cause data inconsistency or corruption. You can disable any custom or third-party modules that are related to indexing and check if the issue persists.

Make sure that the version_id for the price indexer in the mview_state table is not higher than the last entry for the same column in the changelog table and re-synchronize. The version_id column in the mview_state table indicates the current state of each indexer. If this value is higher than the last entry in the changelog table, it means that the indexer has skipped some records and needs to be re-synchronized. You can use the bin/magento indexer:reset command to reset the state of the price indexer and then run bin/magento indexer:reindex to reindex it.

: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html : https://devdocs.magento.com/guides/v2.4/config-guide/cli/config-cli-subcommands-index.html

Question 2

Since the last production deployment, customers can not complete checkout. The error logs show the following message multiple times:

The Architect finds a deployed feature that should limit delivery for some specific postcodes.

The Architect sees the following code deployed in/webapi_rest \di .xml and etc\frontend\di xml

Which step should the Architect perform to solve the issue?

AInject an instance of \Magentro\Quote\API\CartRepostoryInterface and receive cart instance via$this->cartRepository->get($this-session->getQucteId())

BReplace the injected dependency \Magento\Checkout\Model\Session\With\Magento\Framework\Session\SessionManagerInterface

CChange 'after' plugin with 'around' plugin. The issue is being caused by calling the result provider code after the code of the original method.

Answer : C

The 'after' plugin is not suitable for modifying the arguments or return value of the original method. The 'around' plugin allows the plugin method to wrap around the original method and modify its behavior and output. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/plugins.html#around-methods

Question 3

An Adobe Commerce system is configured to run in a multi-tier architecture that includes:

* A cache server with Varnish installed

* A backend web server with Adobe Commerce installed

* A database server with MySQL installed

When an Adobe Commerce Architect tries to clean the cache from the Store Admin by using the "Flush Magento Cache" in Cache Management, the Full Page Cache does not clear.

Which two steps should the Architect take to make the Full Page Cache work properly? (Choose two.)

ASet the backend destination host to the frontend server's address in the Store Admin
Stores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Host

BSet the backend port destination to the frontend server's Varnish port in the Store Admin
Stores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Port

CSet the cache type to 'Varnish Caching' in the Store Admin.
Stores > Configuration > Advanced > System > Full Page Cache > Caching Application

DUse 'Flush Cache Storage' instead of 'Flush Magento Cache'

ESet the cache destination host using magento CLI bin/magento setup:config:set --http-cache-hosts<cache_server>:<varrnish port>

Answer : C, E

To use Varnish as the full page cache, the cache type must be set to ''Varnish Caching'' in the Store Admin. This will enable the ''Flush Magento Cache'' button to send a purge request to Varnish. Additionally, the cache destination host must be specified using the magento CLI command to tell Magento which Varnish servers to purge. Reference: https://devdocs.magento.com/guides/v2.4/config-guide/varnish/config-varnish.html

Question 4

Due to a marketing campaign, a website is experiencing a very large number of simultaneously placed orders, which is affecting checkout performance. The website is in the production deploy mode.

Which two website settings can an Architect optimize to decrease the impact on checkout performance? (Choose two.)

AAsynchronous indexing admin panel Setting (Stores > Settings > Ccr.f iguraticr. > Advanced > developer > Grid Settings > Asynchronous
indexing) can be enabled by executing the following CLI command: tm/magento config:set dev/grid/async_ini*xmg 1

BMultithreaded checkout processing admin panel setting (stores > s ettmgs > Configuration > Sales > Checkout > General Settings > Asynchronous) can be set to a higher value representing the number of PHP threads used exclusively for checkout

CAsynchronous email notifications admin panel Setting (stores > Settings > Configuration > Sales > Sales Emails > General Settings > Asynchronous) can be enabled

DA new database can be created and the Split Database feature can be automatically configured with the following command: bin/Magento
setup:db-schema:split-sales-sales --host=''<checkout db host or ip>' ---dbname='<name>' ---username''<checkout db username>'' ---password=' '

EThe website deploy mode can be set to si-g- by executing the following CLI command: bin/magento deploy:mode:set siege. Provided that it will be changed back to production as soon as the number of simultaneously placed orders decreases to acceptable levels

Answer : A, D

Asynchronous indexing allows Magento to process indexers in the background without affecting the storefront performance. Splitting the database allows Magento to use a separate database for checkout-related tables, which reduces the load on the main database and improves checkout performance. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#asynchronous-indexing https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html

To decrease the impact on checkout performance, the Architect should do two things:

Enable asynchronous indexing admin panel setting. This will allow Magento to update indexes using cron jobs instead of doing it on the fly during checkout. This option can be found under Stores > Settings > Configuration > Advanced > Developer > Grid Settings > Asynchronous indexing. It can also be enabled by executing the following CLI command: bin/magento config:set dev/grid/async_indexing 1

Create a new database and use the Split Database feature. This will allow Magento to separate the sales data from the main database and reduce the load on the database server. This option can be configured with the following command: bin/magento setup:db-schema:split-sales --host='<checkout db host or ip>' --dbname='<name>' --username='<checkout db username>' --password=''

https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-asynchronous-indexing

https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html

Question 5

An Adobe Commerce Architect creates a new functionality called Customs Fee, which adds a new total that applies to additional costs for handling customs clearance expenses. The extension allows specifying fee value for every website separately via the Adobe Commerce Configuration System.

The Architect plans to cover new functionality with integration tests. One test case needs to confirm if the total is calculated correctly on different websites.

How should the Architect make sure that test configuration data is added to test methods according to best practices?

AOverride setuo () method, receive instance of \Magento\TestFramework\App\config, and specify value via setValue () method

BSpecify @magentoconfigFixture annotations for the test methods in PHPDoc

CCreate a fixture file to configure Adobe Commerce and specify it in test method PHPDoc using the @magentoconfigFixture annotation