Most Recent Microsoft AZ-802 Exam Dumps

ntdsutil.exe is a command-line management utility for the AD DS database itself, used for tasks such as performing authoritative restores, seizing or transferring FSMO roles, database integrity checks and defragmentation, managing application directory partitions, and Directory Services Restore Mode password resets; it has no built-in command, menu, or capability for browsing individual object attributes such as the ms-FVE-RecoveryPassword value stored on a msFVE-RecoveryInformation child object, and it provides no interface at all for reading or exporting BitLocker recovery data. Retrieving a BitLocker recovery password stored in AD DS requires either the BitLocker Recovery Password Viewer snap-in for Active Directory Users and Computers, which adds a dedicated tab to a computer object's properties specifically to display associated recovery passwords, or direct inspection of the msFVE-RecoveryInformation child objects through a general-purpose LDAP tool such as ADSI Edit or an equivalent PowerShell query against the directory; ntdsutil operates at the database/role-management level and simply has no code path that surfaces this attribute value to an administrator. Because running ntdsutil.exe on a domain controller does not read, display, or export any BitLocker recovery password, and no combination of its available commands can be used to obtain one, this solution does not meet the stated goal of identifying Server1's recovery key.

The storage account used for Azure virtual machine boot diagnostics must be a standard-performance-tier account, since Microsoft documents that attempting to use a premium storage account for boot diagnostics returns a StorageAccountTypeNotSupported error when the virtual machine is started, and it also cannot use zone-redundant storage, since ZRS is likewise unsupported for this specific resource and produces the same class of error. Looking at the four accounts in the table, storage3 and storage4 are both Premium-tier accounts, which immediately rules both of them out regardless of their redundancy setting, and storage2, despite being Standard tier, uses zone-redundant storage, which independently rules it out as well. That leaves storage1, which is both Standard performance tier and uses geo-redundant storage rather than zone-redundant storage, satisfying both documented requirements simultaneously. Because storage1 is the only one of the four accounts that avoids both the premium-tier restriction and the ZRS restriction at the same time, it is the only valid choice among the options offered for configuring VM1's boot diagnostics storage.

Azure Site Recovery recovery plans support inserting automated steps before or after each failover group within the plan, and the mechanism used to run that automation is an Azure Automation runbook invoked directly from the recovery plan. Runbooks can call Azure Resource Manager operations, PowerShell workflows, or other custom orchestration logic, which makes them a natural fit for replacing a manual step such as reconfiguring a load balancer, updating DNS records, or validating application health once the 200 virtual machines have failed over. An Azure Desired State Configuration virtual machine extension enforces configuration state on a running VM rather than integrating with the recovery plan's action framework, an Azure PowerShell function run outside of Automation has no native hook point within a recovery plan, and a Custom Script Extension executes a script inside a VM rather than as an orchestrated recovery-plan action. Because Azure Automation runbooks are the specific, documented integration point Site Recovery recovery plans use for automating manual actions, that is the correct choice for automating one of the plan's three manual steps.

Azure managed disks support expanding (increasing) a data disk's size without deallocating the VM, and Microsoft's documentation confirms this applies to Standard HDD, Standard SSD, and Premium SSD disks as long as the resize stays at or below 4 TiB (crossing the 4 TiB boundary does require deallocating and detaching first; Premium SSD v2 and Ultra Disk have no such restriction at any size). Disk2 is a 512 GiB Standard HDD data disk, well under the 4 TiB threshold, so increasing its size can be performed online, with no VM downtime. Decreasing (shrinking) an Azure managed disk's size is never supported at all, with or without downtime, regardless of disk type, due to the risk of data loss -- the only workaround is creating a new, smaller disk and copying the data across, not an in-place shrink. Changing a managed disk's encryption type (for example, switching between platform-managed and customer-managed keys) and changing its storage type (for example, from Standard HDD to Premium SSD) are both operations that Microsoft documents as requiring the VM to be stopped/deallocated (and, in many cases, the disk detached) before the change can be applied, since these operations affect how the disk is provisioned and served at the storage layer. Therefore, among the four choices, only increasing Disk2's size can be performed without causing downtime to VM1.

Because the four test devices use manually configured static IP addresses rather than addresses leased from the DHCP server, they never register a DHCP client lease or reservation binding tied to their MAC address; the DHCP server (Server1) has no built-in awareness that those addresses are already statically claimed. A DHCP reservation ensures a specific DHCP client (identified by MAC address) always receives the same address when it requests one via DHCP -- it does not protect addresses a device has been configured with statically outside of DHCP, so reserving addresses for devices that never request a DHCP lease has no protective effect. The simplest, lowest-effort fix that actually addresses the problem -- Server1 potentially leasing those same four addresses to other DHCP clients while the test devices are powered off -- is to add an exclusion range covering those four addresses, permanently removing them from the pool Server1 can hand out, regardless of whether the test devices are online or offline. Scope options configure settings such as default gateway or DNS servers delivered with a lease and have no bearing on which addresses get leased. Policies allow conditional assignment of options or ranges based on client criteria (such as vendor class), unnecessary complexity for simply reserving four fixed addresses out of the pool. Therefore, creating an exclusion range for the four addresses is the correct, minimal-effort solution.