AZ-400 Question 178
Select 2You are designing a multi-stage Azure DevOps pipeline to deploy both a .NET web application and its corresponding database changes to Azure SQL Database. The database schema changes are stored in a DACPAC file generated by your build process. Which tasks should you include in your release pipeline to automatically apply the schema updates to Azure SQL Database as part of the same deployment?
- A
Use an Azure Resource Group Deployment task to deploy the database schema from the DACPAC file.
- B
Add an Azure SQL Database Deployment task and point it to the DACPAC file with appropriate parameters for upgrades.
- C
Include an Azure CLI task to run SqlPackage.exe commands against the target Azure SQL Database using the DACPAC file.
- D
Store the DACPAC file in Azure Artifacts but apply the schema changes manually using SQL Server Management Studio.
Show answer and explanation
Correct answers: B, C
Explanation
Combining application and database tasks in a single pipeline is a key DevOps best practice. For Azure SQL Database, recommended approaches include using the Azure SQL Database Deployment task or running SqlPackage.exe via Azure CLI (documented by Microsoft in https://learn.microsoft.com/azure/devops/pipelines/targets/azure-sql-database). Both methods enable automated, controlled deployment of the DACPAC, ensuring the database schema is upgraded as part of the continuous deployment strategy.
- A. Incorrect.
Incorrect. The Azure Resource Group Deployment task primarily handles infrastructure deployment and doesn�t directly apply DACPAC-based schema changes.
- B. Correct.
Correct. The Azure SQL Database Deployment task is specifically designed to deploy DACPAC files, allowing you to configure advanced parameters such as database upgrades and additional options.
- C. Correct.
Correct. Using Azure CLI to call SqlPackage.exe with the DACPAC file is also a valid approach, giving you full control over the schema deployment process.
- D. Incorrect.
Incorrect. Manually applying schema changes outside of the pipeline does not provide a fully automated or repeatable deployment process.