Free Magento Magento-Certified-Professional-Cloud-Developer Practice Exam with Questions & Answers | Set: 2

When you add a variable. the build stage is being skipped because the codebase has not been changed You must push a commit to trigger a full deploy

Deploy scripts read configuration from the environment variable calledmagento_cloud_variables. which contains an array of variables which were set without the env: prefix

Variables which are set using the Project Web Ul are not available on the build phase the admin password variable should be

set in the . magento.env. yaml file

The sensitive option is required for env:ADMIN PASSWORDvariable

Use the magento-cloud route:add command to create a route to the Staging URL

Modify the yA3EXT0_CLOUD_R0UTES environment variable on your staging environment

Enter the proper URL in the Routes tor Staging under the Environment Settings in the Project Web Ul

Configure UPDATE_URLSto true in the .magento.env.yaml file

The build phase runson a separate server and variables are not available there you must keep the credentials in the auth. j son file, but you can replace the password with its hash

Add the env:coMPOSER_AUTH variable on the projectlevel and make it visible on the build phase

Putthe composer credentials into/mnt/build/.config/composer/auth.json

Add the composer_auth variable with the sensitive option enabled

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

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

Request the vendor make the directory configurable in the Magento admin

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

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

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

Modify the post_deploy hook in the .magento.app.yamlfile to include the URLs as arguments to the ece-tools command

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

Commit the patch because the pre-commit hook will abort the commitit any hotfix causes an issue

Run the command git apply m2-hotfixea/extension-fix.patch

Run the command bin/magento setup:hotfix:apply --patch=m2-hctfixes/extension-fix.patch

Configure a deploy hook in .magento.app.yamlthat executes

vendor/bin/ece-tools hotfix:apply —dry-run

Setting this record causes sent email to be property authenticated and not show in junk folders

Setting this record enables the page caching service for your site

Setting this record is needed on Pro to allow upsizing servers without downtime

Setting this record reduces the time it takes for customers to start seeing your Magento 2 site

Move static content deploy the build phase

Commit var.view_preprocessed to git so it already exists duringthe deployment phase

Set stage /global/SKIP_SCD to true.

Reduce the number of store view website