What is the primary purpose of the 'services.yaml' file in an Adobe Commerce on cloud infrastructure project?

Question

Options

• ATo define the services the application depends on, such as MySQL, Redis, and their versions.
• BTo configure the web server properties and writable mount points.
• CTo set environment-specific variables for different stages of deployment.
• DTo define the application's build hooks and deployment phases.

• A
  74% (28)
• B
  8% (3)
• C
  5% (2)
• D
  13% (5)

Explanation

In Adobe Commerce cloud projects, services.yaml is the dedicated configuration file for declaring external services (like MySQL, Redis, Elasticsearch, RabbitMQ) along with their versions and disk allocations - making A correct.

Why the distractors are wrong:

• B describes .magento.app.yaml, which handles web server properties, mounts, and application-level configuration.
• C describes .magento.env.yaml (or environment variables set via magento-cloud CLI), used for stage-specific settings like CACHE_CONFIGURATION or DATABASE_CONFIGURATION.
• D also describes .magento.app.yaml, specifically its hooks section (build, deploy, post_deploy).

Memory tip: Think of the files by their names - services.yaml = services (the infrastructure your app depends on), .magento.app.yaml = app configuration (hooks, mounts, web server), and .magento.env.yaml = environment variables. Each file owns its domain.

No community discussion yet for this question.