YAML Configuration File Challenge

Lab Steps

YAML Configuration File Challenge
Need help? Contact our support team

Here you can find the instructions for this specific Lab Step.

If you are ready for a real environment experience please start the Lab. Keep in mind that you'll need to start from the first step.


Your Mission

The company you work for are migrating their existing IT systems to the cloud. One system is comprised of a web application and MySQL database. This system has been deemed to be legacy. It is poorly documented and it's internals are not well understood.

In order to migrate it with the minimum of effort, a separate development team is working on software to wrap the system so that it can easily run on modern cloud resources.

You have been tasked with creating a configuration file in YAML to store database connection data for the migrated system.

The following instructions prepare you to work on this challenge.


  1. The in-browser integrated development environment (IDE) is starting up while you see Setup in progress on the Validation Steps tab.

    It takes approximately 1 minute for the development environment to startup at which point you can begin using the IDE to complete the challenge.

  2. Click the Go to Validation Steps button below to perform the tasks and complete the challenge.

    When you are ready, click the Check button to check your solution:


    Note: In order for the checks to pass you must save your YAML file before clicking Check.

Validation checks
Create a YAML File

Create a file called config.yaml

Create a Database Host Mapping

Create a top-level mapping key called database that contains a mapping key called host with the value db.example.net

Create a Port Mapping

Under the database key, add a mapping key called port with the value 3306

Create a Enabled Mapping

Under the database key, add a mapping key called enabled with the value true

Create a Legacy Mapping

Under the database key, add a mapping key called legacy with the value yes

Re-use the Database Configuration

Re-use the database mapping data so that the following are satisfied:

  • A new top-level mapping called database_new exists
  • The database mapping has an anchor called common
  • The database_new mapping has an alias called common