Explanation:
In Azure Data Factory (ADF) continuous integration and continuous deployment (CI/CD) scenarios, when you have a development instance (ADFdev) connected to Azure DevOps Git and need to deploy artifacts to a production instance (ADFprod), the first step is to create a release pipeline in Azure DevOps.
Option A (Modify Git configuration): This is unnecessary since ADFdev is already properly connected to the Git repository. Modifying Git configuration doesn't facilitate deployment to ADFprod.
Option B (Create a linked service): Linked services are for data source connections within ADF, not for deployment between ADF instances. This doesn't address the deployment requirement.
Option D (Update the main branch): The main branch is already being used for publishing to ADFdev. Updating it further doesn't initiate the deployment process to ADFprod.
The optimal workflow is:
This approach follows Microsoft's recommended CI/CD practices for Azure Data Factory and ensures reliable, automated deployments between environments.
Ultimate access to all questions.
You have two Azure Data Factory instances named ADFdev and ADFprod. ADFdev is connected to an Azure DevOps Git repository. After publishing changes from the main branch to ADFdev, you need to deploy the artifacts from ADFdev to ADFprod. What is the first step you should take?
A
From ADFdev, modify the Git configuration.
B
From ADFdev, create a linked service.
C
From Azure DevOps, create a release pipeline.
D
From Azure DevOps, update the main branch.
No comments yet.