Download Microsoft.AZ-400.Dump4Pass.2024-01-26.198q.tqb

Register your application to use Azure Active Directory. Registering the application means that your developers can use Azure AD to authenticate users and request access to user resources such as email, calendar, and documents.    Reference: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/developer-guidance-for-integrating-applications

1. In Azure portal navigate to the az400-9940427-main app.  2. Scroll down to the Settings group in the left navigation.  3. Select Managed identity.  4. Within the System assigned tab, switch Status to On. Click Save.              Reference: https://docs.microsoft.com/en-us/azure/app-service/overview-managed-identity

When you need to pass a secure value (like a password) as a parameter during deployment, you can retrieve the value from an Azure Key Vault. You retrieve the value by referencing the key vault and secret in your parameter file. The value is never exposed because you only reference its key vault ID. The key vault can exist in a different subscription than the resource group you are deploying to.    Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-keyvault-parameter

With the storage account ready, you can configure backs up in the web app or App Service.  1. Open the App Service az400-11566895-main, which you want to protect, in the Azure Portal and browse to Settings > Backups. Click Configure and a Backup  Configuration blade should appear.  2. Select the storage account.  3. Click + to create a private container. You could name this container after the web app or App Service.  4. Select the container.  5. If you want to schedule backups, then set Scheduled Backup to On and configure a schedule: every five hours 6. Select your retention. Note that 0 means never delete backups.  7. Decide if at least one backup should always be retained.  8. Choose if any connected databases should be included in the web app backup.  9. Click Save to finalize the backup configuration.            Reference: https://petri.com/backing-azure-app-service

Step 1: Create an AKS cluster   Step 2: a system-assigned managed identity To create an RBAC binding, you first need to get the Azure AD Object ID.  1. Sign in to the Azure portal.  2. In the search field at the top of the page, enter Azure Active Directory.  3. Click Enter.  4. In the Manage menu, select Users.  5. In the name field, search for your account.  6. In the Name column, select the link to your account.  7. In the Identity section, copy the Object ID.            Step 3: a RBAC binding Reference:   https://docs.microsoft.com/en-us/azure/developer/ansible/aks-configure-rbac

Box 1: Azure Pipelines service connection   Box 2: Managed Service Identity Authentication The managed identities for Azure resources feature in Azure Active Directory (Azure AD) provides Azure services with an automatically managed identity in Azure AD. You can use the identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without any credentials in your code.    Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-key-vault   https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview

Box 1: Microsoft Visual Studio App Center distribution Groups Distribution Groups are used to control access to releases. A Distribution Group represents a set of users that can be managed jointly and can have common access to releases. Example of Distribution Groups can be teams of users, like the QA Team or External Beta Testers or can represent stages or rings of releases, such as Staging.    Box 2: Shared Shared distribution groups are private or public distribution groups that are shared across multiple apps in a single organization. Shared distribution groups eliminate the need to replicate distribution groups across multiple apps.    Note: With the Deploy with App Center Task in Visual Studio Team Services, you can deploy your apps from Azure DevOps (formerly known as VSTS) to App Center. By deploying to App Center, you will be able to distribute your builds to your users.    Reference: https://docs.microsoft.com/en-us/appcenter/distribution/groups

Use a variable group to store values that you want to control and make available across multiple pipelines.    Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/variable-groups

A: To resolve NPM dependencies, you should first run "npm install" command on the relevant folders before executing the plugin. C: All npm packages contain a file, usually in the project root, called package.json – this file holds various metadata relevant to the project. This file is used to give information to npm that allows it to identify the project as well as handle the project's dependencies. It can also contain other metadata such as a project description, the version of the project in a particular distribution, license information, even configuration data – all of which can be vital to both npm and to the end users of the package.    Reference: https://whitesource.atlassian.net/wiki/spaces/WD/pages/34209870/NPM+Plugin   https://nodejs.org/en/knowledge/getting-started/npm/what-is-the-file-package-json

WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.    Reference: https://azuredevopslabs.com/labs/vstsextend/whitesource/