AZ-400 Korean試験無料問題集「Microsoft Designing and Implementing Microsoft DevOps Solutions (AZ-400 Korean Version) 認定」

Explanation:

Box 1: Secret
Store credential in Azure Key Vault by reference secret stored in key vault.
To reference a credential stored in Azure Key Vault, you need to:
* Retrieve data factory managed identity
* Grant the managed identity access to your Azure Key Vault. In your key vault-> Access policies -> Add Access Policy, search this managed identity to grant Get permission in Secret permissions dropdown. It allows this designated factory to access secret in key vault.
* Create a linked service pointing to your Azure Key Vault.
* Createdata store linked service, inside which reference the corresponding secret stored in key vault.
Box 2: Access policy
Reference:
https://docs.microsoft.com/en-us/azure/data-factory/store-credentials-in-key-vault

解説: (GoShiken メンバーにのみ表示されます)

Explanation:

Box 1: A key Vault advanced access policy

Box 2: RBAC
Management plane access control uses RBAC.
The management plane consists of operationsthat affect the key vault itself, such as:
* Creating or deleting a key vault.
* Getting a list of vaults in a subscription.
* Retrieving Key Vault properties (such as SKU and tags).
* Setting Key Vault access policies that control user and application access tokeys and secrets.
References:https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-tutorial-use- key-vault

解説: (GoShiken メンバーにのみ表示されます)

See the solution below in explanation.
Explanation:
To configure a virtual machine template in your DevTest Labs environment namedaz400-38443478-dtl1with Windows Server 2016 Datacenter that includes the Selenium tooland the Google Chrome browser, follow these steps:
* Create a Custom Image with Windows Server 2016 Datacenter:
* In the Azure Portal, go to your DevTest Labaz400-38443478-dtl1.
* Navigate toConfiguration and policies>Custom images.
* Use an existing VM or create a new one with Windows Server 2016 Datacenter.
* After setting up the VM, capture it to create a custom image1.
* Install Selenium and Google Chrome on the VM:
* Connect to the VM via RDP.
* Download and install the Selenium WebDriver for your preferred programming language from the official Selenium website2.
* For Google Chrome, download the offline installer from the official website and install it on the VM3.
* Generalize the VM:
* Run thesysprepcommand to generalize the VM, which prepares it to be used as a template.
* Shutdown the VM aftersysprepcompletes.
* Capture the Generalized VM to Create a Template:
* In the Azure Portal, navigate to the VM and selectCapture.
* Provide the required details and create the image.
* Add Selenium and Google Chrome Artifacts to the Template:
* Go back to the DevTest Labaz400-38443478-dtl1.
* SelectArtifactsand add Selenium and Google Chrome artifacts to the template.
* Ensure these artifacts are configured to install during the VM creation process.
* Create VMs from the Template:
* Now, when youcreate a new VM in the DevTest Lab, select the custom image you created.
* The VM will be provisioned with Windows Server 2016 Datacenter, and the Selenium tool and Google Chrome browser will be installed automatically.
By following these steps, you can ensure that all virtual machines created from this template in your DevTest Lab will have the required operating system, tools, and browser installed. Remember to replace placeholder names with the actual names of your resources where necessary.

解説: (GoShiken メンバーにのみ表示されます)

Explanation:

Step 1: Create a Desired State Configuration (DSC) configuration file that has an extension of .ps1.
Step 2: Run the Import-AzureRmAutomationDscConfiguration Azure Powershell cmdlet TheImport-AzureRmAutomationDscConfiguration cmdlet imports an APS Desired State Configuration (DSC) configuration into Azure Automation. Specify the path of an APS script that contains a single DSC configuration.
Example:
PS C:\>Import-AzureRmAutomationDscConfiguration -AutomationAccountName "Contoso17"- ResourceGroupName "ResourceGroup01" -SourcePath "C:\DSC\client.ps1" -Force This command imports the DSC configuration in the file named client.ps1 into the Automation account named Contoso17. The command specifies the Force parameter. If there is an existing DSC configuration, this command replaces it.
Step 3: Run the Start-AzureRmAutomationDscCompilationJob Azure Powershell cmdlet The Start-AzureRmAutomationDscCompilationJob cmdlet compiles an APS Desired State Configuration (DSC) configuration in Azure Automation.
References:
https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/import- azurermautomationdscconfiguration
https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/start- azurermautomationdsccompilationjob

解説: (GoShiken メンバーにのみ表示されます)

解説: (GoShiken メンバーにのみ表示されます)

Explanation:
1 -> TFVS Refer : https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/control-access-team-foundation- version-control?view=azure-devops
2 -> TFVS Refer :https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies?view=azure- devops
3 -> Git Refer : https://docs.microsoft.com/en-us/azure/devops/repos/git/share-your-code-in-git-xcode?
view=azure-devops
4 -> TFVS Refer :https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions?
view=azure-devops#tfvc

解説: (GoShiken メンバーにのみ表示されます)