QUESTION: 9

A merchant is using a unified website that supports native Adobe Commerce B2B and B2C with a single store view.
The merchant wants to show the B2B account features like negotiable quotes and credit limits in the header of the site on every page for the logged-in users who are part of a B2B company account. Each B2B company has its own individual shared catalog and customer group, and many customer groups for non B2B customers change. The merchant requests that this should not be tied to customer groups.
Which two solutions should the Architect recommend considering public data and caching? (Choose two.)

Create a plugin that switches the theme when a user is part of a B2B company so the output can be modified accordingly in the alternate theme.
Check if the current user is part of a B2B company within a block class and modify the output accordingly.
Create a new custom condition for customer segments that allow for choosing whether a user is part of a B2B company and then use this segment to modify the output accordingly.
Set whether the current user is part of a B2B company in the customer session and use that data directly to modify the output accordingly.
Create a new HTTP Context variable to allow for separate public content to be cached for users in B2B companies where the output can be modified accordingly.

Answer(s): C,E

Explanation:

C would involve creating a new custom condition for customer segments that allow for choosing if a user is part of a B2B company, and then use this segment to modify the output accordingly. E would involve creating a new HTTP Context variable to allow for separate public content to be cached for users in B2B companies, where the output can be modified accordingly.

To show the B2B account features in the header of the site on every page for the logged-in users who are part of a B2B company account, the Architect should recommend two solutions: C) Create a new custom condition for customer segments that allow for choosing whether a user is part of a B2B company and then use this segment to modify the output accordingly. This solution will allow the merchant to create a customer segment based on the custom condition and use it to display different content in the header for B2B users. E) Create a new HTTP Context variable to allow for separate public content to be cached for users in B2B companies where the output can be modified accordingly. This solution will ensure that the public content cache is varied based on the custom HTTP Context variable, which can be set based on whether the user is part of a B2B company or not. Option A is incorrect because switching the theme based on the user's B2B status is not a scalable or maintainable solution, and it will also affect the entire site's appearance, not just the header. Option B is incorrect because checking the user's B2B status within a block class will not work with public content cache, as it will not vary the cache based on that condition. Option D is incorrect because setting the user's B2B status in the customer session will not work with public content cache, as it will not vary the cache based on that data.

Reference:

https://devdocs.magento.com/guides/v2.4/extension-dev-guide/segmentation.html https://devdocs.magento.com/guides/v2.4/extension-dev-guide/cache/page-caching/public- content.html

Reveal Solution Next Question

QUESTION: 10

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

The plugin for the public method isAllowedObserver() from \Magento\Staging\Model\Event\Manager that alters the return value
The logging observers being copied from etc\events.xml to etc\adminhtml\events.xml with the attribute disabled=''true"
The list of logging observers in bannedObservers parameter of \Magento\staging\Model\Event\Managertype in di.xml

Answer(s): C

Explanation:

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

Reveal Solution Next Question

QUESTION: 11

An Adobe Commerce Architect gets a request to change existing payment gateway functionality by allowing voided transactions only for a certain range of paid amounts. In the vendor module file etc/config.xml, payment method has an option can,_void set to 1.
How should this customization be done?

Extend Magento\Payment\Model\\Method\Adapter and reimplement method void. Use this new class as a new type of payment method facade configuration overriding virtualType type for adapter.
Declare a new plugin for class Magento\Payment\ Gateway\Config\ConfigValueHandler and using the afterHandle method, change the result for Subject can_void.
Add new handler with name can_void to virtualType based on typeMagento payment\Gateway\config\ValueHandlerPool In payment method facade configuration.

Answer(s): C

Explanation:

The Architect should add a new handler with name can_void to virtualType based on type Magento\Payment\Gateway\Config\ValueHandlerPool in payment method facade configuration. This handler will be responsible for determining whether the payment method can void transactions or not, based on the custom logic of the paid amount range. The handler should implement \Magento\Payment\Gateway\Config\ValueHandlerInterface and override the handle() method to return true or false depending on the payment amount. Option A is incorrect because extending Magento\Payment\Model\Method\Adapter and reimplementing method void will not change the can_void option, but rather the logic of voiding transactions. Option B is incorrect because declaring a new plugin for class Magento\Payment\Gateway\Config\ConfigValueHandler and using the afterHandle method will affect all payment methods that use this class, not just the specific one that needs customization.

Reference:

https://devdocs.magento.com/guides/v2.4/payments- integrations/base-integration/integration-model.html

Reveal Solution Next Question

QUESTION: 12

An Adobe Commerce Architect needs to customize the workflow of a monthly installments payment extension. The extension is from a partner that is contracted with the default website PSR which has its own legacy extension (a module using deprecated payment method). The installment payment partner manages only initializing a payment, and then hands the capture to be executed by the PSP. Once the amount is successfully captured, the PSP notifies the website through an IPN. The goal of the IPN is only to create an "invoice" and save the 'capture information' to be used later for refund requests through the PSP itself. The Architect needs the most simple solution to capture the requested behavior without side effects.

Which solution should the Architect implement?

Add a plugin before the $invoice-> () and changes its input to prevent the call of the $payment-> capture()
Change the can_ capture attribute for the payment method under config.xml to be <can_capture>0</can_capture>
Declare a capture command with type Magento\payment\Gateway\Command\NullCommand for the payment method CommandPool in di.zm1

Answer(s): C

Explanation:

The best solution for the Adobe Commerce Architect to implement in order to capture the requested behavior without side effects is to declare a capture command with type Magento\payment\Gateway\Command\NullCommand for the payment method CommandPool in di.xml. This will allow the partner to initialize the payment and then hand the capture over to the PSP, while also preventing the website from calling the $payment->capture() method. It will also allow the PSP to notify the website through an IPN, which will create an "invoice" and save the 'capture information' to be used later for refund requests through the PSP itself. The Architect should implement the solution of declaring a capture command with type Magento\Payment\Gateway\Command\NullCommand for the payment method CommandPool in di.xml. This command will do nothing when the capture method is called on the payment method, which is the desired behavior since the capture is handled by the PSP. The NullCommand class implements \Magento\Payment\Gateway\CommandInterface and overrides the execute() method to return null. Option A is incorrect because adding a plugin before the $invoice->capture() method and changing its input will not prevent the call of the $payment->capture() method, but rather change the invoice object that is passed to it. Option B is incorrect because changing the can_capture attribute for the payment method under config.xml to be <can_capture>0</can_capture> will not prevent the capture method from being called, but rather disable the capture option in the Admin panel.

Reference:

https://devdocs.magento.com/guides/v2.4/payments-integrations/base- integration/facade-configuration.html

Reveal Solution Next Question

Free AD0-E718 Exam Braindumps (page: 3)

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference: