Exam AZ-400 topic 9 question 4 discussion

Answer is incorrect, but this is also a repeated question. 1. Create a SP 2. In Project1, create a service connection 3. In Pipeline1, authorize the service connection But correct me if I'm wrong.

Create a service principal in Azure AD. In Project1, create a service connection. In Pipeline1, authorize the service connection.

Project1 create service connection Project1 configure permissions Pipeline1 authorize https://learn.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml

Project1: Create a service connection for webapp1. (Note: Service principal will be created automatically during service connection creation.) Pipeline1: Authorize the service connection. In Project1: Configure permissions.

Create a Managed Identity: Managed Identity is used to provide an identity to your application, in this case, the pipeline, without needing to manage the credentials. It helps secure access to Azure resources. In Project1, create a service connection: A service connection in Azure DevOps is a way to connect to an external service or resource. In this case, it's used to connect to Azure. In Pipeline1, authorize the service connection: After creating the service connection, you need to authorize it in the specific pipeline (Pipeline1 in this case) where you want to use it. This step allows the pipeline to use the credentials provided by the service connection to deploy code to the Azure web app (webapp1).

1. Create a Managed Identity (SP will also work) 2. In Project1, create a service connection. While creating service connection make sure Not to check the box 'Grant access permission to all pipelines' 3.Configure pipeline permissions - Click on newly created pipeline. Click on 'Security' displayed under '...'. Under 'Pipeline Permssions', select your pipeline and authorize it

Provided answer seems correct -> login to azure devops => Create new service connection -> Azure Resource Manager => leave the default selection & click next => you are prompted to authorize the service connection -> save Once completed you will see that this has created automatically a service principal. If you select the manual process => it will require a service principal prior creating the service connection itself. Same is valid for the 2nd and 3rd options -> Service principal automatic/manual.

I believe both SP and managed Identity will work. when creating a new Service connection, you have the following options: New Azure service connection (Azure Resource Manager) Authentication method 1.Service principal (automatic) Recommended 2.Service principal (manual) 3.Managed identity 4.Publish Profile

1. Create a Managed Identity 2. In Project1, create a service connection 3. In Pipeline1, authorize the service connection I think SP works too. I guess this question may accepted different answer.

For deploy an Azure web app with Azure devops pipelines you need: 1. In Proyect1, create a service connection. This connection in Azure devops allows pipelines access to Azure web app. 2. In Pipeline1, create a variable. To reference values that can be used throughout the pipeline execution, for example the service connection created in the previous step. 3. In Pipeline1, authorize the service connection. This step ensure that the pipeline has the necessary access to Azure web app using the service connection during deployments proccess.

I think it is 1. Create a Service Principal 2. Create a Service Connection and 3. Authorize the Service Connection

To ensure that Pipeline1 can deploy code successfully to an Azure web app named webapp1 while restricting Pipeline2's permission to webapp1, you should perform the following three actions in sequence: 1. Create a system assigned managed identity in Microsoft Azure AD, part of MS Entra: Create a system assigned managed identity for the Azure web app webapp1. This managed identity will be used by Pipeline1 to authenticate and access webapp1 during the deployment process. 2. in Project1, configure permissions: Within Azure DevOps Project1, configure the permissions to grant the necessary access rights to Pipeline1. This can involve assigning appropriate roles or permissions within the project, ensuring that Pipeline1 has the required privileges to deploy to webapp1. 3. In Project1, create a service connection: Create a service connection in Azure DevOps Project1 that represents the connection between Pipeline1 and webapp1. This service connection will use the managed identity created in step 1 to authenticate and authorize Pipeline1's access to webapp1.