正解：

Explanation:
Detailed Explanation
The Failover TCP/IP settings (the IPv4/IPv6 address, subnet, and gateway a replicated VM should assume after failover) are a network-adapter property that only applies to the Replica copy of the virtual machine, so they are configured on VM1 as it exists on the Replica server, Server2 - this is the only place the option is exposed in Hyper-V Manager. A virtual switch, on the other hand, must be present and correctly mapped on both the primary host and the Replica host so that the VM ' s virtual network adapter can connect to a switch whether it is running on Server1 (normal operation) or has failed over to run on Server2, which is why virtual switch configuration needs to be addressed for VM1 on both servers.
Official Reference
Configure the Failover TCP/IP settings for a Hyper-V Replica virtual machine - https://learn.microsoft.com
/en-us/windows-server/virtualization/hyper-v/best-practices-analyzer/configure-the-failover-tcpip-settings- that-you-want-the-replica-virtual-machine

正解：

Explanation:
Detailed Explanation
A cloud witness for a Windows Server failover cluster is configured against a standard general-purpose Azure Storage account; premium storage account types are not required or supported for this purpose.
Authentication to the storage account for the cloud witness is performed using the storage account ' s access key (primary or secondary) - the cluster uses this key to generate the token it needs to read/write the witness blob - rather than a shared access signature or an Azure AD (managed identity) credential, neither of which the cloud witness feature supports.
Official Reference
Deploy a cloud witness for a failover cluster - https://learn.microsoft.com/en-us/windows-server/failover- clustering/deploy-cloud-witness

正解：

Explanation:
Detailed Explanation
A pull synchronization using the Web Deployment Agent Service is executed from the destination server and retrieves content from a remote source identified by the computername parameter. The command is therefore run on Server2, with -source pointing at apphostconfig= " Site1 " ,computername=Server1 to reach the remote Web Deploy Agent Service on Server1, and -dest pointing at the local apphostconfig= " Site1 " without a computername value, since the destination is the machine the command is executing on. Adding computername to the destination parameter instead, or omitting it from the source, would reverse the direction of the sync or fail to identify the remote server correctly.
Official Reference
Synchronize IIS by using Web Deploy - https://learn.microsoft.com/en-us/iis/publish/using-web-deploy
/synchronize-iis

正解：

Explanation:
Detailed Explanation
Azure Disk Encryption artifacts (such as the BitLocker/DM-Crypt encryption keys) can be protected in Key Vault by a software-protected key or by a hardware-protected key. Choosing ' key ' (rather than ' certificate ' or ' secret ' ) creates a cryptographic key object that can be used as a key-encryption key to wrap the disk encryption secret before it is written to the vault. Specifying --kty RSA-HSM (as opposed to plain RSA) ensures the key material is generated and protected inside a FIPS 140-validated hardware security module rather than in software, which is the highest level of protection Key Vault offers for this purpose. This matches the completed command shown in the exhibit.
Official Reference
About Azure Key Vault keys - https://learn.microsoft.com/en-us/azure/key-vault/keys/about-keys