You are a technical admin on a Magento Commerce Cloud account A coworker needs to submit a support request with Magento Support.

What is needed to enable support ticket access"?

A. Ask the account owner to add the user to shared access

B. Ask the launch manager to create a support account for this user

C. Change the environment access role to contributor for this user

D. Update the project role of this user to administrator

You are reviewing a third party extension for Magento Commerce Cloud compatibility.

You discover the module writes to a custom directory called internal/ within the Magento base directory.

The directory has to be shared by all web servers.

What do you do so the module can be used on Magento Commerce Cloud?

A. Create a symlink from /top/internal to the internal/ folder

B. Declare a shared mount for the internal/directory in .magento. app.yaml

C. Request the vendor make the directory configurable in the Magento admin

D. Add a patch for extension so it uses the subdirectory var/internal/ instead

You built a custom command that runs during the build phase, but it is not generating files property Magento Support provided a patch that you added to theproject.

What must you do to ensure this command runs after the patch has been applied?

A. Ensure your custom command runs after the ece-tools build hooks

B. Move your custom command to run in the deploy phase

C. Apply the patch manually in your custom command, because patches are always applied at the end of deployment

D. Nothing because patches are already applied when any hook runs

You are tasked to improve the user experience of the most visited product pages after deploying releases to Production. The aim is to reduce initial page load times.

How do you achieve this?

A. Create a custom build command and use CURL to cache the page

B. Use the Magento Admin to configure Fastly to cache the pages after deployment

C. Modify the post_deploy hook in the .magento.app.yaml file toinclude the URLs as arguments to the ece-tools command

D. Use the warm_up_PAGES variable in the .magento.env.yaml file to cache the pages during postdeploy

You need to get code with a backend order placement security related fix into production as quickly as possible.

The project currently deploys static content during the build phase with both stags/global/SKIP_SCD and stage/deploy/STATIC_STATIC_CONTENT_SYMLINK set to false.

What setting in.magento,env,yaml minimizes the overall deployment time?

A. Remove all themes from stages/global/SCD_MATRIX so they will not be generated

B. Set stage/global/Static_CONTENT_SYMLINK to true to symlink static assets to the init directory

C. Set stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead

D. Set stage/global/SKIP_SCD to true to completely avoid static content processing