You upgraded an integration branch in your Magento Commerce Cloud project, but received an error during the deploy phase What are the two ways toreview details about the deployment?
Choose 2 answers

• A. View the exception.log file in the var/log/ directory
• B. View the depioy.log file in the /var/log/ directory
• C. View thecloud.log file in the var/log/ directory
• D. View the logs in the var/reports/ directory on the remote server

You have a project deploying Static Content on the deploy phase. This process is optimized using the scd_katrix configuration in the deploy Stage Of the .magento.env.yaml file After moving the process to the build phase Static Content Deployment Is no longer optimized and all themes and all locales are generating How do you resolve this?

• A. The SCD_MATRIX configuration is only used on the deploy phase
• B. Move the scd_matrix configuration to the build stage of the .magento.env.yaml file
• C. Add the -use_scd_matrix flag to the ece-tools build:generate command in the.magento.app.yaml fife
• D. Configure the variable ENABLE_SCD_MATRIX In the .magento.env.yaml file

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. Use the Magento Admin to configure Fastly to cache the pages after deployment
• B. Use the warm_up_PAGES variable in the .magento.env.yaml file to cache the pages during postdeploy
• C. Create a custom build command and use CURL to cache the page
• D. Modify the post_deploy hook in the .magento.app.yaml file toinclude the URLs as arguments to the ece-tools command

A merchant slates the downtime during the deployment phase is too long
After analysis, it is determined the static content deployment is the longest process Static content needs to be available immediately after deployment How can the static content deployment time to be reduced?

• A. Reduce the number of store view website
• B. Set stage /global/SKIP_SCD to true.
• C. Commit var.view_preprocessed to git so italready exists during the deployment phase
• D. Move static content deploy the build phase

You added a grunt autoprefixer command, which adds CSS vendorprefix like -webkit- and -moz- to CSS files generated by the setup:static-connect: deploy command.

After deployment you still see CSS files without prefixes. The hooks section in the .magento. app. Yaml file is:
Considering static assets are being generated on the build phase why are CSS prefixes missing?

• A. The static assets were not generated yet when the grunt command ran
• B. CSS vendor prefixes must be added to CSS files locally and committed as part of a theme
• C. Custom commands can be run only on the deploy phase
• D. The custom command was run before static assets were transferred into the init directory