070-535日本語試験無料問題集「Microsoft Architecting Microsoft Azure Solutions (070-535日本語版) 認定」
正解：
Explanation
Wire data is consolidated network and performance data collected from Windows-connected and Linux-connected computers with the OMS agent, including those monitored by Operations Manager in your environment. Network data is combined with your other log data to help you correlate data.
In addition to the OMS agent, the Wire Data solution uses Microsoft Dependency Agents that you install on computers in your IT infrastructure. Dependency Agents monitor network data sent to and from your computers for network levels 2-3 in the OSI model, including the various protocols and ports used. Data is then sent to Log Analytics using agents.
Box 1: Deploy the Microsoft Dependency Agent to the VMs
Box 2: Use the OMS Wire Data Solution
Not Azure Monitor: Azure Monitor provides base-level infrastructure metrics and logs for most services in Microsoft Azure
正解：
Explanation
For blob storage, there is a retry policy implemented by default, so if you do nothing, it will do what's called exponential retries. It will fail, then wait a bit of time and try again; if it fails again, it will wait a little longer and try again, until it hits the maximum retry count.
References:
https://www.simple-talk.com/cloud/platform-as-a-service/azure-blob-storage-part-3-using-the-storage-client-libr
正解：
Explanation
Number of DMP servers: 1
Centralize the management of all backups.
Number of Azure backup vaults: 2
References: https://docs.microsoft.com/en-us/azure/backup/backup-azure-dpm-introduction
正解：
Explanation
Step 1: Create an Azure Key Vault
Step 2:
The key vault must be enabled for template deployment.
Scenario: Must use version-controlled Azure Resource Manager (ARM) templates to manage Azure resources.
Note: 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.
References:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-keyvault-parameter