A client has an in-house design team which manages content on their Magento Commerce Cloud project. This content is rapidly changing and they would like the ability to maintain their own stylesheets in a structured way without affecting site uptime.
How do you achieve this on the Integration branch?
A. Modify the writeable directories on the Integration Environment by using the .magento.env.yaml file.
B. Add a custom command to the build hook in the .magento.app.yaml file to retrieve the stylesheets from a client hosted location.
C. The Magento Infrastructure Team needs to create a writable directory in which the stylesheets can be uploaded.
D. Use the .magento.app.yaml file to create a mount in the pub directory.
You are setting up a third-party integration only for the Production environment, which connects to an external RabbitMQ server.
Where do you put the configuration?
A. In the app/etc/env.php file
B. In the QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI
C. In the env:QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI
D. In the QUEUE_CONFIGURATION variable in the .magento.env.yaml file
You have a project deploying Static Content on the deploy phase. This process is optimized using the SCD_MATRIX 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. Add the --use_scd_matrix flag to the ece-tools build:generate command in the .magento.app.yaml file
C. Move the SCD_MATRIX configuration to the build stage of the .magento.env.yaml file
D. Configure the variable ENABLE_SCD_MATRIX in the .magento.env.yaml file
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
You upgraded an integration branch in your Magento Commerce Cloud project, but received an error during the deploy phase.
What are the two ways to review details about the deployment? (Choose two.)
A. View the logs in the var/reports/ directory on the remote server
B. View the exception.log file in the var/log/ directory
C. View the deploy.log file in the /var/log/ directory
D. View the cloud.log file in the var/log/ directory
You want to move static content deploy to the build phase of deployments.
Which two actions do you take? (Choose two.)
A. Download and commit app/etc/config.php from production
B. Run ece-tools scd-deploy:set build on production
C. Run ece-tools config:dump on production
D. Use scp to copy app/etc/config.php from local to production
You need to disable a module on a Magento Commerce 2.3 Cloud project and remove its database tables. The module uses the declarative schema system to manage its database changes.
Which action do you take?
A. Run bin/magento module:disable MyCompany_MyModule on the local environment and then commit and deploy the app/et/config.php file
B. Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file
C. Delete the module from the git repository leaving the record in app/etc/config.php intact and deploy the changes
D. Remove the module line from the app/etc/config.php file on the local environment and then deploy the 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. 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 to include 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 post_deploy
You want to improve the ability to monitor Production deployments by setting up an email notification system.
How do you achieve this?
A. Enable Deployment Notifications under Configure Environment > Settings in the Project Web UI
B. Build a custom module which hooks into the deployment phase and sends emails in real-time
C. Configure log notifications in the .magento.env.yaml file
D. Use the magento-cloud environment:deploy:email command to enable email notifications