A client has an in-house design team which manages content on their Magento Commerce Cloudproject 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. Use the, magento, app, yaml file to create a mount in the pub directory
• 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. Modify the writeable directories on the Integration Environment by using the . magento. env. yaml file
• D. The Magento Infrastructure Team needs to create a writeable directory in which the stylesheets can be uploaded.

You want to improve the ability to monitor Production deployments by setting up an email notification system How do you achieve this?

• A. Configure log notifications in the.magento.env.yaml file
• B. Enable Deployment Notifications under Configure Environment > Settings in the Protect Web
• C. Use the magento-cloud environment:deploy:email command to enable email notifications
• D. Build a custom module which hooks into the deployment phase and sends emails in real-time

A custom module that adds a new console command for bin/magento has just been built Deploying this to the Production environment on your Pro plan site causes the build phase to fall.
You find this occurs when you inject certain Magento core classes in your console command class The command works on your local environment Why does this occur?

• A. Files were written to the root Magento directory. which is read-only on Magento Commerce Cloud
• B. A connection to the database was attempted which Is not available during the build phase
• C. The three webservers generated different content which causes the build to be rolled back for safety
• D. The injected class logged to the exception logrile, but a different logging implementation is used during deployment

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing project. You have confirmed that your services. yaml file is configured appropriately However, after your most recently deployment, you notice the search engine is still set to MySQL What additional step must be completed?

• A. Find an appropriate Elasticsearch module to require with Composer
• B. Configure the relationships Section of the .magento.app.yaml file
• C. Remove the MySQL service from the services. yaml file
• D. SpecifyElasticsearch as the search engine in the Magento Admin panel