What are the key responsibilities of the Git-based workflow in Adobe Commerce on cloud infrastructure? (Select all that apply.)

Question

Options

• AAuthenticating users for the Admin panel.
• BManaging the versions of PHP and MySQL for the project.
• CStoring backups of the production database.
• DTriggering an automatic build and deploy process when code is pushed to a remote branch.
• ECreating new integration environments by branching from a parent environment.

• A
  4% (1)
• C
  8% (2)
• D
  88% (22)

Explanation

In Adobe Commerce on cloud infrastructure, the Git-based workflow serves as the engine for both deployment automation and environment management. Pushing code to a remote branch triggers the build and deploy pipeline automatically (D) - this is the core DevOps mechanism that compiles code, runs hooks, and deploys to the target environment without manual intervention. Branching from a parent environment (E) is how new integration environments are provisioned: the child branch inherits the parent's codebase, services, and data, making Git branching directly equivalent to environment creation.

Why the distractors are wrong:

• A - Admin panel authentication is handled by Adobe Commerce's application layer (roles, 2FA, SSO), not the Git workflow.
• B - PHP and MySQL versions are declared in .magento.app.yaml and services.yaml config files; Git stores those files, but the workflow itself doesn't manage runtime versions.
• C - Database backups are managed by the cloud platform infrastructure, not by Git operations.

Memory tip: Remember "Git = Deploy + Branch." Every git push deploys, and every git branch builds an environment. Everything else (auth, versions, backups) lives outside the Git workflow.

No community discussion yet for this question.