After deploying to Staging for the first time with the Fastly module installed, you notice that Fastly is not caching pages. Page caching works properly in a local development environment.
What two steps are required to make Fastly cache pages?
Choose 2 answers

• A. Populate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.
• B. Activate the module by setting Caching Application to Fastly CDN.
• C. Enable the Fastly connection by running magento-Cloud fastly:setup.
• D. Connect the Fastly shield using the Shield setting in the Magento admin.

You want to move staticcontent deploy to the build phase of deployments Which two actions do you take? Choose 2 answers

• A. Download and commit app/etc/config.php from production
• B. Use scp to copy app/etc/config.php from local to production
• C. Run ece-tools config:dump on production
• D. Run ece-tools scd-deploy:set build on production

You want to exclude some themes from static assets generation only for integration environments You are trying to choose where to set the scd_exclude_themes variable in the . magento.env.yamltile or in the Project WeD Ul.
What prevents the usage of the . magento. env.yaml file?

• A. The .magento.env.yama file can contain only deployment configuration options, which are only available it static assets generation runs on the deploy phase
• B. Only variables which are set using the Project Web Ul has the option visible during build
• C. Child environments inherit the variable when you use the . magento. env. yaml file
• D. The code from integration would be merged into the Staging and Production branches

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. Set stage /global/SKIP_SCD to true.
• B. Move static content deploy the build phase
• C. Commit var.view_preprocessed to git so it already exists duringthe deployment phase
• D. Reduce the number of store view website

You aremigration an existing Magento 2 website to Magento Commerce Cloud. After setting up the project you would like to migrate the database to the integration branch. The database import fails with a disk space error.
How do you migrate the database data loss?

• A. Trim down the database to a smaller size
• B. Configure the mysql disk Size in the .magento/services.yamlfile
• C. Configuration the mysql disk size using a variable in the , magento,evn,yaml file
• D. Open a Magento Support ticket to increase the Integration branch disk size