If you want to know our AZ-802 exam questions before your coming exam, you can just visit our website. And it is easy and convenient to free download the demos of our AZ-802 study guide, you just need to click on it. Then you wil find that all points of the AZ-802 Learning Materials are predominantly related with the exam ahead of you. Every page is full of well-turned words for your reference related wholly with the AZ-802 training prep.
| Section | Objectives |
|---|---|
| Topic 1: Networking and high availability | - High availability and disaster recovery
|
| Topic 2: Compute, storage, and virtualization | - Storage and file services
|
| Topic 3: Secure and manage Windows Server environments | - Security and compliance
|
| Topic 4: Hybrid infrastructure management | - Azure integration
|
If you buy the Software or the APP online version of our AZ-802 study materials, you will find that the timer can aid you control the time. Once it is time to submit your exercises, the system of the AZ-802 preparation exam will automatically finish your operation. After a several time, you will get used to finish your test on time. If you are satisfied with our AZ-802 training guide, come to choose and purchase.
NEW QUESTION # 338
You have an Azure subscription. Your on-premises network connects to Azure by using an Azure VPN gateway named VPN1. You need to monitor the Azure gateway health probe for VPN1. Which TCP port should you use?
Answer: A
Explanation:
Azure virtual network gateways expose an internal health probe on TCP port 8081 that Azure infrastructure uses to verify that the gateway instance is healthy; this port is documented as part of gateway troubleshooting and must not be blocked for the gateway to be monitored and managed correctly. Ports such as 443, 1723, and
3389 are associated with HTTPS, PPTP VPN, and RDP respectively, and 65500 falls outside the actual health- probe port used by the gateway manager, so none of those apply to monitoring the VPN gateway ' s own health probe. If a network security group, on-premises firewall, or custom routing rule blocks port 8081 to the gateway subnet, Azure ' s platform health checks fail even though the VPN tunnel itself may still be passing traffic, which is why this specific port must be excluded from any traffic filtering applied to the GatewaySubnet. Microsoft ' s troubleshooting guidance for Site-to-Site VPN connectivity issues explicitly calls out verifying that port 8081 is reachable to the gateway ' s private IP addresses as an early diagnostic step, since a blocked health probe can itself trigger gateway failover behavior unrelated to the underlying tunnel configuration.
NEW QUESTION # 339
Your network contains an Active Directory Domain Services (AD DS) domain.
The domain contains privileged users who are members of a global security group named Group1 and are located in multiple organizational units (OUs).
The Default Domain Policy configures the password and account lockout policies for standard users.
You need to ensure that only the members of Group1 have different password and account lockout policies.
What should you do?
Answer: D
Explanation:
Fine-grained password policies allow administrators to configure different password and account lockout requirements for specific users or global security groups within an Active Directory domain.
These policies are implemented through Password Settings Objects (PSOs), which define settings such as minimum password length, password complexity, password history, and account lockout thresholds.
Applying a PSO directly to Group1 ensures that its members receive the required restrictions regardless of their organizational unit locations.
Creating an OU-linked GPO containing password policies does not provide the required per-group domain- account password policy. Local Security Policy affects local accounts rather than the intended domain users.
Modifying the Default Domain Policy would affect the general domain password policy instead of targeting Group1.
Therefore, creating a PSO and applying it to Group1 is the correct solution.
NEW QUESTION # 340
Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains the servers shown in the following table.
The domain contains the users shown in the following table.
On Server2. you run the Enable-PSRemoting cmdlet
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
User1 can establish a PowerShell remoting session from Server1 to Server2: No. User2 can establish a PowerShell remoting session from Server2 to DC1: No. User3 can establish a PowerShell remoting session from Server1 to Server2: No.
Establishing a WinRM/PowerShell remoting session to a target requires the connecting user to be a member of the local Administrators group or the local Remote Management Users group on that specific target. A crucial, commonly misunderstood point is that the domain ' s built-in, domain-scoped " Administrators " group is not automatically nested into the local Administrators group of ordinary member servers -- only the Domain Admins (and Enterprise Admins) global groups receive that special, hardcoded automatic nesting at domain-join time. The domain ' s built-in " Administrators " group functions as the de facto local admin group only on domain controllers (since DCs share one AD database with no separate per-machine local SAM); on a member server like Server2, it confers no rights at all unless separately/explicitly granted. So User1 (Contoso\Administrators) has no local rights on Server2 and cannot remote into it. " Remote Management Users " likewise has no domain-level Builtin-container equivalent that would auto-grant WinRM rights on every domain-joined machine (or on domain controllers) -- a domain group of that name must be explicitly added to a target ' s local Remote Management Users group (for example, via Group Policy Restricted Groups) before it has any effect, and no such configuration is described here, so User2 cannot remote into DC1 either. " Power Users " is a legacy local group stripped of special privileges since Windows Vista/7 and does not include remoting rights, so User3 cannot remote into Server2 despite Enable-PSRemoting having been run there (that cmdlet only starts the WinRM listener; it does not itself grant any additional users access).
NEW QUESTION # 341
Your on-premises network contains an Active Directory Domain Services (AD DS) domain.
You plan to implement BitLocker Drive Encryption (BitLocker) for the domain.
You create a Group Policy Object (6P0) and enable the Choose how BitLocker-protected operating system drives can be recovered Group Policy setting.
You need to configure a data recovery agent (DRA) for drive recovery.
What should you use to configure the DRA, and which additional Group Policy setting should you enable? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
Configure the DRA by using: A digital certificate. Enable setting: Choose default folder for recovery password.
A BitLocker data recovery agent is configured using a public-key (PKI) digital certificate issued from a duplicated Key Recovery Agent template that carries the BitLocker Drive Encryption and BitLocker Data Recovery Agent application policies; the certificate ' s public key is added to the domain ' s DRA configuration through Public Key Policies > BitLocker Drive Encryption in Group Policy, after which every computer that later encrypts a drive under that policy automatically protects the drive ' s recovery key with the DRA certificate, letting a holder of the corresponding private key decrypt any protected drive domain-wide. A BitLocker recovery password (a 48-digit numerical key), a user principal name, and a security identifier are all identifiers or credentials associated with individual users or computers rather than the credential type used to configure a data recovery agent itself, so none of those options describes how a DRA is set up. Because a DRA relies on 48-digit numerical recovery passwords being generated and escrowed for each protected drive as the actual recovery mechanism the DRA certificate later decrypts, enabling Choose default folder for recovery password ensures every BitLocker-enabled computer automatically saves a copy of its numerical recovery password to a specified, centrally accessible network folder as each drive is encrypted, giving administrators (and, in effect, the DRA-holding recovery workflow) a reliable location to retrieve recovery data from without depending solely on AD DS storage or manual per-user handling.
NEW QUESTION # 342
You have two on-premises servers named Server1 and Server2 that run Windows Server. Server2 contains a Hyper-V virtual machine named VM1. You have an Azure subscription that contains a Recovery Services vault. You need to configure Azure Site Recovery to replicate workloads from the on-premises environment to Azure. What should you do first?
Answer: C
Explanation:
For Hyper-V-to-Azure replication that is not managed through System Center Virtual Machine Manager, the Azure Site Recovery Provider and the accompanying Recovery Services agent are host-level components that must be installed and registered on every Hyper-V host that will participate in replication, not on the individual guest virtual machines those hosts happen to run. Since VM1 runs on Server2, the first action in this on-premises-to-Azure Site Recovery scenario is to run the AzureSiteRecoveryProvider.exe setup on Server2 itself and complete the registration wizard against the Recovery Services vault already created in Azure, supplying the vault ' s registration key downloaded from the portal. Once that registration succeeds, Server2 ' s Hyper-V site becomes visible as a protectable source within the vault in Azure, and individual virtual machines hosted on it, such as VM1, can then have replication enabled directly from the portal ' s Site Recovery blade. Running the provider setup on VM1 itself would be meaningless, since the provider is a host- level component that talks to the Hyper-V management layer rather than something installed inside a guest OS, and running the unrelated AzureBackupAgentInstaller.exe, on either VM1 or Server2, would only configure the separate MARS backup agent rather than registering the host for Site Recovery replication.
NEW QUESTION # 343
......
Preparing for the AZ-802 real exam is easier if you can select the right test questions and be sure of the answers. The AZ-802 test answers are tested and approved by our certified experts and you can check the accuracy of our questions from our free demo. Expert for one-year free updating of AZ-802 Dumps PDF, we promise you full refund if you failed exam with our dumps.
Exam AZ-802 Outline: https://www.pdf4test.com/AZ-802-dump-torrent.html