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.
Sthis->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?
An Architect is working to implement Adobe Commerce into a pre-built ecosystem in a company.
Communication between different company domains uses event-driven design and is driven via AMQP protocol with using RabbitMQ.
The Architect needs to establish the data flow between the ERP system and Adobe Commerce.
The ERP system stores only customer data excluding customer addresses.
The role of Adobe Commerce is to provide Customer Address data to the enterprise ecosystem.
Primary Customer data should not be changed from Adobe Commerce side; it should only be updated by messages data from ERP.
Which three AMQP configurations should be considered to meet these requirements? (Choose three.)
To establish the data flow between the ERP system and Adobe Commerce using AMQP protocol with RabbitMQ, you need to consider the following AMQP configurations:
Create a queue_consumer.xml and communication.xml configuration files for Customer data messages. These files will define the topics, handlers, and consumers that will receive and process the messages from the ERP system. The communication.xml file will also specify the schema for the Customer data messages.
Create a queue_publisher.xml configuration file for Customer Address messages. This file will define the exchange where the Customer Address messages will be published to. The exchange will route the messages to the appropriate queues based on the binding rules.
Create a queue_topology.xml configuration file for Customer Address messages. This file will define the message routing rules and declare the queues and exchanges for the Customer Address messages. The queue_topology.xml file will also specify the connection name and type for RabbitMQ.
1: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/message-queues/config-mq.html
An Adobe Commerce Architect needs to scope a bespoke news section for a merchant's Adobe Commerce storefront. The merchant's SEO agency requests that the following URL structure:
news/{date}/{article_url_key}l 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.
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.)
To manage routing this functionality and adhere to best practice, you need to consider the following options:
Create a standard controller route and an Index/Index index controller class that loads the relevant news article by matching the URL date and URL key parts. This option will create a simple and straightforward way to handle the news requests using the standard Magento routing mechanism. The Index/Index controller class will receive the date and URL key parameters from the request and use them to load the news article model from the database.
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. This option will create a more flexible and customizable way to handle the news requests using a custom router class that implements \Magento\Framework\App\RouterInterface. The custom router class will check if the request path starts with news, then extract the date and URL key parts from the path and use them to load the news article model from the database.
: https://belvg.com/blog/how-to-create-custom-router-in-magento-2.html : https://devdocs.magento.com/guides/v2.4/extension-dev-guide/routing.html
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?
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.
1: https://docs.magento.com/user-guide/v2.3/cms/content-staging-category.html
An Architect is reviewing a custom module that is logging customer activity data on storefront using observers. The client reports that logs were recorded while the client was previewing storefront catalog pages from Admin Panel for a future scheduled campaign, using Adobe Commerce staging preview functionality.
What should the Architect check first to address this issue9
It will allow you to exclude logging observers from being executed during staging preview functionality by adding them to bannedObservers parameter of \Magento\staging\Model\Event\Manager type in di.xml file. This will prevent customer activity data from being logged while previewing storefront catalog pages from Admin Panel for a future scheduled campaign.
The Architect should check the list of logging observers in bannedObservers parameter of \Magento\Staging\Model\Event\Manager type in di.xml. This parameter defines the list of observers that should not be executed during staging preview. The Architect should add the logging observers to this list to prevent them from recording customer activity data while previewing the storefront catalog pages from Admin Panel. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/staging.html
