Google Cloud Deployment Manager Essentials Quiz Quiz

Challenge your understanding of Google Cloud Deployment Manager with scenario-based questions focused on its configuration, templates, deployment tools, and best practices. This quiz is designed for those seeking practical knowledge of automating and managing cloud infrastructure using declarative templates.

  1. Understanding Deployment Manager Configurations

    Which file format is primarily used by Deployment Manager to define resource configurations, such as virtual machines and networks, in a structured and readable manner?

    1. CSV
    2. DOCX
    3. XML
    4. YAML

    Explanation: YAML files are the primary format for writing Deployment Manager configurations because they are structured, easy to read, and widely supported for configuration tasks. CSV and XML are common data formats but are not typically used for declarative infrastructure in this context. DOCX is a document format and is not supported at all for configuration purposes.

  2. Template Language Selection

    When creating reusable templates for consistent infrastructure deployment, which scripting languages are officially supported by Deployment Manager for writing templates?

    1. Java and C++
    2. Ruby and Go
    3. Python and Jinja2
    4. PHP and Perl

    Explanation: Deployment Manager officially supports Python and Jinja2 for creating templates, making it possible to add logic and reusability to your templates. Ruby, Go, Java, C++, PHP, and Perl are not supported languages for this specific purpose, although they may be used elsewhere in software development.

  3. Resource Lifecycle Management

    Suppose you need to update the properties of an existing cloud resource managed by Deployment Manager. Which approach allows you to safely apply the changes while preserving managed resources?

    1. Updating the configuration file and redeploying
    2. Making direct changes in the cloud provider's console
    3. Editing the YAML file but not redeploying
    4. Deleting and recreating the deployment every time

    Explanation: The correct approach is to modify the configuration file and redeploy the deployment, which safely applies changes while managing dependencies and minimizing disruptions. Deleting and recreating deployments can cause loss of state, while direct changes in the console will not persist when redeploying from configuration. Simply editing the YAML file without redeploying will not produce any actual changes.

  4. Parameterization in Templates

    A team wants to deploy several similar environments with minor differences using a single Deployment Manager template. Which feature allows them to pass in different values at deployment time for resources such as machine type or region?

    1. Fixed variables
    2. Resource labels only
    3. Hardcoded literals
    4. Input properties

    Explanation: Input properties allow users to parameterize templates, making it possible to specify different values such as machine types or regions at deployment time. Fixed variables and hardcoded literals lack flexibility for repeated deployments. Resource labels serve as metadata and do not affect core template parameterization.

  5. Preview Mode Utility

    Before finalizing a deployment, which Deployment Manager feature lets users see the proposed changes and resource creation plan without affecting real infrastructure?

    1. Preview mode
    2. Quick deploy
    3. Instant update
    4. Live modification

    Explanation: Preview mode allows users to review what changes would be made during a deployment, providing a chance to verify configurations before making actual changes to infrastructure. Quick deploy initiates deployment without previewing details. Live modification and instant update do not exist as features for reviewing proposed changes.