An Architect needs to review a custom product feed export module that a developer created for a merchant.
During final testing before the solution is deployed, the product feed output is verified as correct. All unit and integration tests for code pass.
However, once the solution is deployed to production, the product price values in the feed are incorrect for several products. The products with incorrect data are all currently part of a content staging campaign where their prices have been reduced.
What did the developer do incorrectly that caused the feed output to be incorrect for products in the content staging campaign?

• A.The developer did not check for an active content staging campaign and emulates the campaign state when retrieving product data.
• B.The developer retrieved product data directly from the database using the entity_id column rather than a collection or repository.
• C.The developer forgot to use the getContentStagingValue() method to retrieve the active campaign value of the product data

Comment: *

Name: *

Email: *

Verification: *

An Adobe Commerce Architect is troubleshooting an issue on an Adobe Commerce Cloud project that is not yet live.
The developers migrate the Staging Database to Production in readiness to Go Live. However, when the developers test their Product Import feature, the new products do not appear on the frontend.
The developers suspect the Varnish Cache is not being cleared. Staging seems to work as expected. Production was working before the database migration.
What is the likely cause?

• A.The Fastly credentials in the Production Database are incorrect.
• B.A deployment should have been done on Production to initialize Fastly caching.
• C.The site URLs in the Production Database are the URLs of the Staging Instance and must be updated.

Comment: *

Name: *

Email: *

Verification: *

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?

• A.The attribute must have its apply_to field set to "staging" in the data patch file.
• B.The attribute must also be added to
  view/adminhtml/ul_component/catalogstaging_category_update_form.xml.
• C.The attribute must have<item name=''allow_staging'' xsi:type="boolean''>true<item> set in the
  =category_form.xml file under the attributes config" section.

Comment: *

Name: *

Email: *

Verification: *

An Architect working on a headless Adobe Commerce project creates a new customer attribute named my_attribure. 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.
• B.
• C.

Comment: *

Name: *

Email: *

Verification: *

A custom cron job has been added to an Adobe Commerce system to collect data for several reports. Its crontab. xml configuration is as follows:

The job is data intensive and runs for between 20 and 30 minutes each night.
Within a few days of deployment, it is noticed that the site's sitemap. xml file has not been updated since the new job was added.
What should be done to fix this issue?

• A.Break the data gathering job into a number of smaller jobs, so that each individual job runs for a maximum of 5 minutes.
• B.Create a new cron group for the reporting job. Specifying
  <use_separate_process>1/use_separate_process>
• C.Change the schedule of the sitemap_generate cron job to 30 o * * * so that it runsafter the aacher_reporcmg_datajob has completed.

Comment: *

Name: *

Email: *

Verification: *