An Adobe Commerce developer is tasked to add a file field to a custom form in the administration panel, the field must accept only .PDF files with size less or equal than 2 MB. So far the developer has added the following code within the form component xml file, inside the fieldset node:

How would the developer implement the validations?
A)
Add the Validations Within the HyVendor\MyModule\Controller\Adminhtml\CustomEntity\UploadPdf Controller

B)
Add a virtual type forMyvendor\MyModuie\Modei\customPdfupioader specifying the aiiowedExtensions and the maxFiiesize for the constructor, within the module's di.xmi:

C)
Add the following code inside the<settings> node:

• A. Option A
• B. Option B
• C. Option C

An Adobe Commerce developer has been asked to modify the PageBuilder slider content type to allow a new custom content type (other than slide) to be assigned as a child. The developer has already created the new content type called improved_slide in their module. They now need to create a new view/adminhtml
/pagebuilder/content_type/slider. xml file in their module to allow the new content type to be a child of slider content types.
What is the correct xml to accomplish this?

• A.
  
• B.
  
• C.
  

An Adobe Commerce developer is working on a Magento 2 instance which contains a B2C and a B2B website, each of which contains 3 different store views for English, Welsh, and French language users. The developer is tasked with adding a link between the B2C and B2B websites using a generic link template which is used throughout the sites, but wants these links to display in English regardless of the store view.
The developer creates a custom block for use with this template, before rendering sets the translate locale and begins environment emulation using the following code:

They find that the template text is still being translated into each stores language. Why does this occur?

• A. startEnvironmffntEmulation() SetS and locks the locale by Using the setLocale() Optional Second
  $lock parameter, i.e. setLocale($newLocaleCode,
  true), to override and lock the locale of the emulated store. If this is set and locked initially then the environment emulation will not be able to override this.
• B. setLocate() does not change translation locale after it has been initially set, the $this->_translate-
  >emulate($newLocaiecode) method exists to temporarily modify this by pushing the new locale to the top of the current emuiatedLocales stack.
• C. startEnvironmentEmuiation() resets the translation locale to the one of the emulated stores, which overrides the locale the developer has set when the order of setLocate and startEnvironmentEmulation is used as displayed above.

When attempting operations that require lengthy processing, a merchant on Adobe Commerce Cloud receives a timeout error after 180 seconds.
How would the developer deal with this issue?

• A. 1. Modify admin timeout into .magento.app.yamifile.
  2. Commit and push that code from the local environment.
  3. Move code to Production environment.
• B. 1. Modify admin timeout into app/etc/config.php file.
  2. Commit and push that code from the local environment.
  3. Submit a support ticket to apply the changes.
• C. 1. In the Fastly Configuration section > Advanced Configuration.
  2. Set the Admin path timeout value in seconds.
  3. Save config and Upload VCL to Fastly.