Questions for the AD0-E716 were updated on : Dec 01 ,2025
An Adobe Commerce developer is about to deploy a critical feature to their Adobe Commerce Cloud
(Pro Plan) production. They want to create a snapshot in order to be able to rollback if there is an
issue with the feature.
How would they create the snapshot?
A
Explanation:
The developer can create a snapshot before deploying a critical feature to their Adobe Commerce
Cloud (Pro Plan) production by using the dedicated button on Project Web Interface. A snapshot is a
backup of an entire environment, including code, data, media files, and configuration settings. A
snapshot can be used to restore an environment to a previous state in case of any issues or errors
during deployment or testing. The developer can create a snapshot by accessing the Project Web
Interface, choosing an environment, and clicking Create Snapshot. Verified Reference: [Magento 2.4
DevDocs]
For security reasons, merchant requested to a developer to change default admin url to a unique url
for every branch/environment of their Adobe Commerce Cloud project.
Which CLI command would the developer use update the admin url?
B
Explanation:
The CLI command that the developer would use to update the admin url is magento-cloud
variable:set ADMIN_URL. This command sets an environment variable called ADMIN_URL with a
custom value for the admin url on a specific environment. Environment variables are configuration
settings that affect the behavior of the Adobe Commerce Cloud application and services. By setting
an environment variable for ADMIN_URL, the developer can change the default admin url to a
unique url for every branch/environment of their Adobe Commerce Cloud project. Verified
Reference: [Magento 2.4 DevDocs]
On an Adobe Commerce Cloud platform, what type of environment will be provisioned when
launching the CLI for Commerce command magento-cloud environment:branch <environment-
name> <parent-environment-id>?
C
Explanation:
The type of environment that will be provisioned when launching the CLI for Commerce command
magento-cloud environment:branch <environment-name> <parent-environment-id> is an
integration environment with the code and database from the parent environment. Integration
environments are temporary environments that are used for testing and development purposes on
the Adobe Commerce Cloud platform. They can be created from any branch of code and have their
own dedicated database and services. When creating an integration environment using the CLI for
Commerce command, the code and database from the parent environment are copied to the new
integration environment, creating an exact replica of the parent environment. Verified Reference:
[Magento 2.4 DevDocs]
During database migration in the Adobe Commerce Cloud integration environment, a developer
experienced a disk space error causing the database import to fail.
How would the developer fix this issue?
A
Explanation:
The developer can fix this issue by increasing the disk space of the database service. The database
service is one of the services that run on the Adobe Commerce Cloud platform and provide
functionality for the application. The database service uses MySQL as the database engine and stores
data for products, customers, orders, etc. The disk space of the database service determines how
much data can be stored and processed by the database. If the disk space is insufficient, the database
import can fail with a disk space error. The developer can increase the disk space of the database
service by modifying the .magento/services.yaml file and redeploying the environment. Verified
Reference: [Magento 2.4 DevDocs]
An Adobe Commerce Cloud developer wants to be sure that, even after transferring database from
Production to Staging, the payment configurations are still valid on the Staging environment.
What does the developer need to add to be sure that the configurations are always properly set?
C
Explanation:
The developer needs to add environment level environment variables to be sure that the payment
configurations are always properly set on the Staging environment. Environment variables are
configuration settings that affect the behavior of the Adobe Commerce Cloud application and
services. Environment variables can be set at the project level or the environment level. Project level
variables apply to all environments, while environment level variables override the project level
variables for a specific environment. The developer can use environment level variables to customize
the payment configurations for the Staging environment without affecting other environments.
Verified Reference: [Magento 2.4 DevDocs]
A Project Architect needs to add a new developer who needs to be able to push code in an Adobe
Commerce Cloud project. No integration with a third-party repository provider is setup.
What two actions would be required to ensure the developer has access? (Choose Two.)
B, C
Explanation:
To ensure the developer has access to push code in an Adobe Commerce Cloud project, the
developer’s email must be added under Users in the Cloud Project Web UI and the developer needs
to add SSH public key in the Cloud Account dashboard settings. The Cloud Project Web UI is a web
interface that allows managing and configuring Adobe Commerce Cloud projects and environments.
The developer’s email must be added under Users to grant them access to the project and assign
them a role and permissions. The Cloud Account dashboard settings is a web interface that allows
managing and configuring Adobe Commerce Cloud accounts and SSH keys. The developer needs to
add SSH public key in the settings to enable secure connection to the project and environments via
SSH. Verified Reference: [Magento 2.4 DevDocs]
A developer wants to deploy a new release to the Adobe Commerce Cloud Staging environment, but
first they need the latest code from Production.
What would the developer do to update the Staging environment?
A.
1. Log in to the Project Web Interface.
2. Choose the Staging environment, and click Sync
B.
1. Log in to the Project Web Interface.
2. Choose the Staging environment, and click Merge
C.
1. Checkout to Production environment
2. Use the magento-cloud synchronize <environment-ID> Commerce CLI Command
A
Explanation:
The developer can update the Staging environment with the latest code from Production by logging
in to the Project Web Interface, choosing the Staging environment, and clicking Sync. This will
synchronize the code, data, and media files from Production to Staging, creating an exact copy of
Production on Staging. The developer can then deploy the new release to Staging and test it before
pushing it to Production. Verified Reference: [Magento 2.4 DevDocs]
A new customer registered on the Integration environment of an Adobe Commerce Cloud project but
did not receive a welcome email What would be blocking the email from being sent?
C
Explanation:
The reason why the new customer did not receive a welcome email is that the Outgoing Emails
setting is disabled in the Environment Settings in the Project Web Interface. This setting controls
whether emails are sent from the application or not. By default, this setting is disabled for
integration environments to prevent spamming or testing emails from being sent to real customers
or recipients. The developer can enable this setting if they want to test email functionality on
integration environments. Verified Reference: [Magento 2.4 DevDocs]
What are two features with Adobe Commerce Cloud that come out of the box? (Choose Two.)
A, D
Explanation:
Two features that come out of the box with Adobe Commerce Cloud are Support ACL and Fastly.
Support ACL is a feature that allows the developer to manage access control lists for different users
and roles on the Adobe Commerce Cloud platform. The developer can create and assign permissions
for different actions and resources on the project and environment levels. Fastly is a cloud-based
caching service that improves site performance and security for Adobe Commerce Cloud
projects.
Fastly provides features such as CDN, image optimization, WAF, DDoS protection, etc.
Verified Reference: [Magento 2.4 DevDocs] 3
On an Adobe Commerce Cloud platform, at what level is the variable env: composer_auth located in
the Project Web Interface?
C
Explanation:
The variable env: composer_auth is located in the Project variables section in the Project Web
Interface. This variable is used to store the authentication credentials for Composer repositories that
require access keys or tokens.
The developer can set this variable at the project level to apply it to all
environments, or override it at the environment level if needed. Verified Reference: [Magento 2.4
DevDocs] 2
How would a developer turn on outgoing emails on an Adobe Commerce Cloud Staging
environment?
C
Explanation:
The developer can turn on outgoing emails on an Adobe Commerce Cloud Staging environment by
accessing the Project Web Interface and selecting the Staging environment. Then, the developer can
select Configure environment and toggle Outgoing emails On.
This will enable the SMTP service for
the Staging environment and allow emails to be sent from the application. Verified Reference:
[Magento 2.4 DevDocs] 1
A merchant is experiencing performance issues on integration environments of their Adobe
Commerce Cloud Pro plan and wants to upgrade to Enhanced Integration Environments.
What are the steps necessary prior to redeploying in order to upgrade to Enhanced Integration
Environments?
A.
1. Limit the number of Integration branches to two
2. Submit a support ticket requesting the upgrade
B.
1. Limit the number of Integration branches to three
2. Set the ENV.ENVIRONMENT in .magento.env.yaml to ENHANCEDJNTEGRATION
C.
1. Limit the number of Integration branches to four
2. Configure integration environments in the cloud GUI and set the Enhanced switch to On
A
Explanation:
The steps necessary prior to redeploying in order to upgrade to Enhanced Integration Environments
are to limit the number of integration branches to two and to submit a support ticket requesting the
upgrade. Enhanced Integration Environments are an improved version of integration environments
that offer better performance, stability, and security. They have a limit of four active branches at a
time, but only two branches can be migrated from standard integration environments. The developer
needs to delete or deactivate any extra branches before requesting the upgrade from Adobe support.
Verified Reference: [Magento 2.4 DevDocs]
A developer is working on an Adobe Commerce Cloud project and wants to get connection data for
the environment's deployed services. The developer has all of the necessary permissions to do this.
Which two options would the developer take to get the connection credentials? (Choose Two.)
AD
Explanation:
Two options to get the connection credentials for the environment’s deployed services are to run the
magento-cloud relationships CLI command and to connect to the server via SSH and read
$_ENV[‘services’] variable. The magento-cloud relationships CLI command displays information
about the relationships between an environment and its services, such as database, cache, search,
etc. The developer can use this command to get the connection data for each service in JSON
format.
Alternatively, the developer can connect to the server via SSH and read the $_ENV[‘services’]
variable, which contains the same information as the CLI command output. Verified Reference:
[Magento 2.4 DevDocs] 3
ECE-Tools provides a set of tools that can be used to manage and maintain your Adobe Commerce
Cloud environment. What are some of the features provided by ECE-Tools?
A
Explanation:
Some of the features provided by ECE-Tools are building application, applying custom patches, and
dumping configuration for static content deployment. ECE-Tools is a set of scripts and tools designed
to manage and deploy Adobe Commerce Cloud projects.
It provides commands for building
application code, applying patches for Magento core issues or custom modules, and dumping
configuration settings for static content deployment optimization. Verified Reference: [Magento 2.4
DevDocs] 2
An Adobe Commerce Cloud project is using Enhanced Integration Environments with two install a
new payment module.
The developer is using Cloud CLI for Commerce tool.
What would a developer do to test this new feature under the integration environment?
C
Explanation:
The developer can test the new feature under the integration environment by deactivating one of
the active integration environment branches, creating a new active branch from integration and
installing the module, and pushing the changes. This is because Enhanced Integration Environments
have a limit of four active branches at a time, and each branch has its own dedicated database and
services.
The developer can use the Cloud CLI for Commerce tool to manage the branches and
deploy the code changes. Verified Reference: [Magento 2.4 DevDocs] 1