Magento Certified Professional Cloud Developer: MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER

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.yaml file or in the Project Web UI.

What prevents the usage of the .magento.env.yaml file?

A. Child environments inherit the variable when you use the .magento.env.yaml file

B. The code from integration would be merged into the Staging and Production branches

C. The .magento.env.yaml file can contain only deployment configuration options, which are only available if static assets generation runs on the deploy phase

D. Only variables which are set using the Project Web UI has the option visible during build

You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension-fix.patch.

Before committing the patch to the repository you want to test it locally.

How do you test a patch in a clean working copy?

A. Commit the patch because the pre-commit hook will abort the commit if any hotfix causes an issue

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

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

D. Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run

After making changes to custom commands in the deploy and build phases, you deploy to Staging. The deployment takes much longer than expected, and Staging is in maintenance mode for most of this time.

What do you do to reduce site downtime?

A. Set the SKIP_MAINTENANCE_SCD variable to true in the .magento.env.yaml file.

B. Add a custom command to the post_deploy phase to activate deferred deployment.

C. Move custom commands from the deploy phase to the build phase.

D. Update the SCD_MATRIX variable to include only necessary custom commands.