Databricks-DE-Assoc Implementing CI/CD Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  To ensure every developer has full admin access to production.

  Why it's wrong here

  Granting every developer full admin access to production is a major security violation. Environment parity is about configuration and infrastructure consistency, not user permissions. Access should always follow the principle of least privilege, with automated systems handling deployments rather than individual users manually interacting with the production environment.

• ✓

  To minimize failures caused by differences between testing and production.

  Why this is correct

  The biggest risk to a CI/CD process is the 'it worked in staging but failed in production' scenario. Parity ensures that the runtime environment is consistent across stages, allowing for reliable testing. This predictability is vital for high-quality data engineering, as it ensures that pipeline logic is thoroughly validated.

• ✗

  To reduce the cost of compute resources in development workspaces.

  Why it's wrong here

  While teams should manage costs, environment parity is about technical consistency, not cost reduction. In fact, maintaining parity often requires running similar compute resources across stages. The primary value is reliability and stability, not the financial optimization of resources within the development or staging tiers of the project.

• ✗

  To allow for manual code deployments in all environments.

  Why it's wrong here

  Manual deployments are the antithesis of the CI/CD goal of automation and consistency. Environment parity is best achieved through automated infrastructure-as-code tools, which eliminate the variability inherent in manual processes. Encouraging manual deployments would only exacerbate the risk of configuration drift and lead to unpredictable pipeline behavior.