Although basic configuration files can be used to deploy less complex workloads, more complex workloads and configurations that you plan to reuse should be handled with templates. A deployment manager template is a file that's imported and used as a type in a configuration. Deployment manager templates allow you to break out a configuration into multiple pieces that you can reuse with different solution deployments. In this lesson, I'm going to show you a basic deployment manager template and its architecture. The template we're going to look at is called demovm.jinja. We'll use it later in this course to deploy a VM. On the screen, you can see our basic demovm deployment template in Jinja format. I created this in preparation for this exercise. In this template, we're defining the name of our VM instance with the name value. In addition to providing a name for our VM, we need to specify the type of resource we're deploying. We do this with the type value. Since we're deploying a VM instance, we need to specify compute.v1.instance as the type. Using the properties value, we need to specify the zone where we want to deploy to and the machine type. In this example, we're deploying an n1-standard-1 machine to the us-central1-a region. The disks value allows us to specify disk information. For this exercise, we're specifying a persistent boot disk called boot and we're configuring the disk for autoDelete so that it's removed when the VM instance is removed. Under initializeParams, we're using the sourceImage value to tell GCP that we want to deploy a debian-9 virtual machine. With the networkInterfaces setting, we're configuring the VM to connect to the default network. In the next lesson, we'll compare configuration files with deployment manager templates. After that, we'll deploy a VM from our demovm deployment manager template.