You are working with a new developer who needs to be able to deploy code and view logs on Magento Commerce Cloud.
What must you do to give them access?
- A . In the .magento.app.yaml file, add their email under Users. They need to enter their SSH public key.
- B . Add their SSH public key to a file named .ssh/authorized_keys and deploy the change.
- C . In the Cloud Project Web UI, click Add User to add their email. They need to enter their SSH public key.
- D . Add a Magento admin user for them and paste the SSH public key into their user’s SSH Key field, which is available only on Magento Commerce Cloud.
B
Explanation:
Reference: https://devdocs.magento.com/cloud/before/before-workspace-ssh.html
You have a Starter project. Your code is ready for testing in the Staging environment, but you need the latest data from Production.
What do you do to update the Staging environment?
- A . Log in to the Project Web UI, choose the Staging environment, and click Sync
- B . Log in to the Project Web UI, choose the Staging environment, and click Merge
- C . Checkout the Staging branch and use the git push origin -f command
- D . Checkout the Production environment and use the magento-cloud sync CLI command
B
Explanation:
Reference: https://devdocs.magento.com/cloud/live/stage-prod-migrate-prereq.html
You need to specify the admin password using an environment variable. You have created an environment variable env:ADMIN_PASSWORD with a valid password. When attempting to log in to the Magento Admin it is not accepting the new password.
How do you correct the environment variable?
- A . The Sensitive option is checked by default and must be disabled
- B . The env:ADMIN_PASSWORD variable can only be used for an initial installation
- C . The environment variable should not have the env: prefix
- D . The ADMIN_PASSWORD variable should be configured via .magento.env.yaml
C
Explanation:
Reference: https://devdocs.magento.com/cloud/env/environment-vars_magento.html
While investigating an inherited Magento Commerce Cloud project, you notice the following SCD_MATRIX configuration in .magento.env.yaml:
stage:
global:
SCD_MATRIX:
"magento/backend":
language:
– en_US
What is the effect of this configuration?
- A . Static content for frontend themes is generated during the deploy phase
- B . All frontend theme static content will be reused from the previous deployment
- C . Only the static content for the adminhtml area will be generated
- D . Static content for all locales will be generated for all frontend themes
D
Explanation:
Reference: https://devdocs.magento.com/cloud/env/variables-deploy.html
A project has a Magento cron job implemented to export new order data to a file. This process can also be triggered by a custom bin/magento command. The functionality uses a lock file in var/locks to prevent concurrent execution.
There are instances when the process gets locked after Production deployments and order data is not exported.
How do you prevent this from happening?
- A . Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
- B . Write a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file
- C . Use the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file
- D . You must access the Production environment and delete the lock file
While launching a site migrated from Magento 1, you are instructed to change the website CNAME record in your DNS provider by Magento for go live.
What is the purpose of setting this record?
- A . Setting this record causes sent email to be properly authenticated and not show in junk folders.
- B . Setting this record enables the page caching service for your site.
- C . Setting this record is needed on Pro to allow upsizing servers without downtime.
- D . Setting this record reduces the time it takes for customers to start seeing your Magento 2 site.
D
Explanation:
Reference: https://devdocs.magento.com/cloud/live/site-launch-checklist.html
While setting up a Magento project, you run the following command:
magento-cloud variable:update ADMIN_USERNAME –value=alice
What will this command do?
- A . Configure the Magento Commerce Cloud tools to use alice for API call authentication.
- B . Change your username to alice for logging into the magento-cloud CLI tool.
- C . Update the Magento cloud/admin/username config variable to alice.
- D . Change the username of the default administrator account to alice.
Exploring the Production environment, you find MYSQL_USE_SLAVE_CONNECTION is enabled.
What is the purpose of this setting?
- A . To split the database tables between the three Production servers and improve performance.
- B . To enable fault tolerance on the MySQL cluster.
- C . To utilize the read-only slave servers and improve the overall performance.
- D . To allow database backups from a MySQL slave server with minimal impact on the Production site.
C
Explanation:
Reference: https://devdocs.magento.com/cloud/env/variables-deploy.html
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
B
Explanation:
Reference: https://devdocs.magento.com/cloud/project/project-conf-files_services-rabbit.html
You are migrating 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 without data loss?
- A . Configure the mysql disk size using a variable in the .magento.env.yaml file
- B . Open a Magento Support ticket to increase the Integration branch disk size
- C . Trim down the database to a smaller size
- D . Configure the mysql disk size in the .magento/services.yaml file
Magento Commerce Cloud comes with a variety of additional features that sets it apart from the on-premise Magento Commerce and Magento Open Source platforms.
What feature improves the release update process and simplifies commands to create a backup of the database, apply custom patches, and verify environment configuration?
- A . Docker environment
- B . Magento Cloud-specific CLI
- C . Cloud configuration wizards
- D . ECE-Tools package
D
Explanation:
Reference: https://devdocs.magento.com/cloud/bk-cloud.html
You need to increase the Admin Session Lifetime up to 86400 seconds for the branch named Integration and children branches, but not for the Staging and Production branches.
How do you update this on the Integration branch and its child branches?
- A . On your local environment, set the Admin Session Lifetime in the Magento admin backend under
Stores > Configuration > Advanced > Admin > Security
then dump this setting into the app/etc/config.php file and commit this file - B . Add the following variable on the Integration branch and set its value to 86400:
env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME - C . Run the following Magento CLI command:
php bin/magento config:set admin/security/session_lifetime 86400 - D . On the Integration environment, set the Admin Session Lifetime in the Magento admin backend under
Stores > Configuration > Advanced > Admin > Security
D
Explanation:
Reference: https://community.magento.com/t5/Magento-1-x-Programming/Magento-1-Admin-Sessiontime-countdown-clock/td-p/106004
You are a technical admin on a Magento Commerce Cloud account. A coworker needs to submit a support request with Magento Support.
What is needed to enable support ticket access?
- A . Ask the account owner to add the user to shared access.
- B . Ask the launch manager to create a support account for this user.
- C . Change the environment access role to contributor for this user.
- D . Update the project role of this user to administrator.
You are upgrading a project to the latest version of Magento Commerce Cloud and part of the process involves a PHP version upgrade. This is now ready to be tested by the QA Team on the Integration environment.
How do you apply the PHP version upgrade?
- A . Change the PHP version in the .magento.app.yaml file and re-deploy
- B . SSH into the Integration environment and upgrade PHP manually
- C . Change the PHP_VERSION configuration in the .magento.env.yaml file and re-deploy
- D . Use the magento-cloud CLI tool to update the PHP_VERSION variable
A
Explanation:
Reference: https://devdocs.magento.com/cloud/project/project-upgrade.html