An Adobe Commerce developer is examining all of the Adobe Commerce Cloud configuration files that can configure application settings, routes, and deploy actions. Which two are valid cloud configuratio

Question

Options

• A.magento.app.yaml
• B.magento.services.yaml
• C.magento.vars.yaml
• D.magento.env.yaml

• A
  85% (23)
• B
  11% (3)
• C
  4% (1)

Explanation

.magento.app.yaml is the primary application configuration file - it controls PHP version, build/deploy hooks, cron jobs, and web server settings, making it central to "application settings and deploy actions." .magento.env.yaml is equally valid; it overrides default configuration for the build, deploy, and post-deploy pipeline phases, giving developers fine-grained control over environment-specific deploy behavior.

Option B is a trap: the real services configuration file lives at .magento/services.yaml (inside a .magento/ subdirectory), not as a flat .magento.services.yaml file at the project root - the naming pattern is subtly different. Option C (.magento.vars.yaml) simply does not exist as a valid Cloud configuration file; environment variables are managed via .magento.env.yaml or the Cloud CLI/Console.

Memory tip: The two correct files both follow the pattern .magento.[keyword].yaml at the project root - app for application/infrastructure config, env for environment/deploy overrides. If an option changes the directory structure (.magento/) or invents a new keyword (vars), it's wrong.

No community discussion yet for this question.