Adobe AD0-E718 Exam Questions

This will ensure that the reporting job runs in its own process, separate from other cron jobs, and will not interfere with the sitemapgenerate cron job. This will ensure that the sitemapgenerate cron job runs as soon as the reporting job is finished, ensuring that the sitemap.xml is always up to date.

The issue is caused by the reporting job blocking the default cron group from running other jobs. By creating a new cron group for the reporting job and specifying <use_separate_process>1/use_separate_process>, the reporting job will run in a separate PHP process and will not affect the default cron group. This way, the sitemap_generate cron job will run as scheduled. Reference: https://devdocs.magento.com/guides/v2.4/config-guide/cron/custom-cron-ref.html

To ensure validation of the configuration files with unique validation rules for the individual and merged files, you need to do the following steps:

Add the Uniform Resource Name (URN) to the XSD file in the config XML file. The URN is a unique identifier for a resource that follows a specific syntax. For example:

<config xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation='urn:magento:module:Vendor_Module:etc/marketplacefeeds.xsd'>

Provide schema to validate a merged file. The schema defines the structure and constraints of the XML document that represents the merged configuration from all modules. The schema file should be named as <config_file_name>.xsd and placed in the etc directory of the module. For example:

marketplacefeeds.xsd

Provide schema to validate an individual file. The schema defines the structure and constraints of the XML document that represents the configuration from a single module. The schema file should be named as <config_file_name>_merged.xsd and placed in the etc directory of the module. For example:

marketplacefeeds_merged.xsd

By setting the same cookie domain for both websites, the customer base can be shared between both websites, as the customer will be authenticated by the same cookie across both sites. This will ensure that customers don't have to log in twice when switching between the two sites.

Setting Cookie Domain for both websites to ''.example.com'' will allow both websites to use the same customer base. This is because the cookie domain determines which websites can access the customer information stored in the cookie. By using a common domain, both websites can share the same customer cookie.See Multiple websites or stores in the Adobe Commerce Help Center1. Reference: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/multi-sites/ms-overview.html?lang=en1

To ensure validation of the configuration files with unique validation rules for the individual and merged files, you need to do the following steps:

Add the Uniform Resource Name (URN) to the XSD file in the config XML file. The URN is a unique identifier for a resource that follows a specific syntax. For example:

<config xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation='urn:magento:module:Vendor_Module:etc/marketplacefeeds.xsd'>

Provide schema to validate a merged file. The schema defines the structure and constraints of the XML document that represents the merged configuration from all modules. The schema file should be named as <config_file_name>.xsd and placed in the etc directory of the module. For example:

marketplacefeeds.xsd

Provide schema to validate an individual file. The schema defines the structure and constraints of the XML document that represents the configuration from a single module. The schema file should be named as <config_file_name>_merged.xsd and placed in the etc directory of the module. For example:

marketplacefeeds_merged.xsd

To ensure zero downtime during the deployment process of Magento 2 on-premises, the Architect should follow two steps:

Run bin/magento setup:upgrade --keep-generated to upgrade database. This will skip the regeneration of static content and code files during the upgrade process, which can take a long time and cause downtime. The static content and code files should be generated separately before or after the upgrade process.

Enable config flag under deployment/blue_green/enabled. This will enable the blue-green deployment strategy, which creates a copy of the current production environment (blue) and deploys the new code to it (green). Then, it switches the traffic from the blue environment to the green environment without any downtime. This option can be enabled by adding a line like deployment/blue_green/enabled: true to the .magento.env.yaml file.