You save $69.98
The team adopts "Restore Defender update connectivity and monitor antivirus definition freshness" for this AVD requirement: "One AVD VM image has outdated malware signatures because it has not contacted security update services". Which explanation is correct?
A running security sensor without current signatures can miss newly recognized threats. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
EDR findings support controlled endpoint investigation and containment of suspicious behavior. This describes the separate situation "Security engineers need to determine whether malicious user processes are performing credential theft on a shared host" but does not justify the selected fix for the current issue. The decisive behavior is: A running security sensor without current signatures can miss newly recognized threats.
Strong identity and device conditions reduce the risk of unauthorized high-impact management activity. This describes the separate situation "Privileged operators connect from untrusted devices to production session hosts without strong authentication controls" but does not justify the selected fix for the current issue. The decisive behavior is: A running security sensor without current signatures can miss newly recognized threats.
JIT access reduces persistent inbound management exposure by opening time-bound authorized paths. This describes the separate situation "Operations staff require emergency access to session hosts only during a time-limited incident" but does not justify the selected fix for the current issue. The decisive behavior is: A running security sensor without current signatures can miss newly recognized threats.
An Azure Virtual Desktop administrator observes: A pooled desktop service must remain available during a single Availability Zone outage. Which response directly addresses this issue?
Distribute appropriate session host capacity across supported availability zones with resilient profile storage. Redundancy at the VM placement layer reduces the impact of a single zonal failure domain. This action directly addresses the conditions in the scenario.
Configure depth-first load balancing with appropriate session limits and autoscale controls. This would be appropriate for the different task-specific situation "An organization wants to consolidate user sessions onto fewer powered-on hosts to reduce compute spend", because Depth-first fills eligible session hosts toward capacity before using additional hosts. It does not directly resolve the stated condition, which calls for Distribute appropriate session host capacity across supported availability zones with resilient profile storage.
Use separate host pools and resource governance boundaries where different controls are required. This would be appropriate for the different task-specific situation "An organization needs different security policy scope for high-risk developers and ordinary staff", because Pool separation supports divergent VM baseline, app and access-policy requirements. It does not directly resolve the stated condition, which calls for Distribute appropriate session host capacity across supported availability zones with resilient profile storage.
Document metadata resource location and session-host VM placement separately. This would be appropriate for the different task-specific situation "Administrators confuse the host pool's Azure region with the physical region of each session host VM", because AVD control-plane resource location and virtual machine compute location are distinct design choices. It does not directly resolve the stated condition, which calls for Distribute appropriate session host capacity across supported availability zones with resilient profile storage.
A Microsoft AZ-140 deployment review finds: A browser extension must be available only for a permitted business department. What is the best corrective action?
Deploy it through managed browser extension policy targeting the allowed user group. Managed browser extension policies control allowed and required extensions without manual per-user installation. This action directly addresses the conditions in the scenario.
Standardize package certificate trust across all eligible host pool session hosts. This would be appropriate for the different task-specific situation "Users can start an App attach application on one VM but not another due to an untrusted package certificate", because Dynamic package activation requires compatible trusted signing across the machines serving users. It does not directly resolve the stated condition, which calls for Deploy it through managed browser extension policy targeting the allowed user group.
Configure and validate shared computer activation for eligible Microsoft 365 Apps installations. This would be appropriate for the different task-specific situation "A shared Windows multi-session host prompts each Microsoft 365 Apps user to activate Office as if it were a personal machine", because Shared computer activation enables supported Microsoft 365 Apps licensing on shared-session environments. It does not directly resolve the stated condition, which calls for Deploy it through managed browser extension policy targeting the allowed user group.
Verify the package image location, share access, identity and host permissions. This would be appropriate for the different task-specific situation "An App attach package is uploaded but users receive a package mounting or accessibility error", because App attach requires session hosts to read or mount the package artifact at the configured storage path. It does not directly resolve the stated condition, which calls for Deploy it through managed browser extension policy targeting the allowed user group.
An enterprise AVD deployment has this requirement: Virtual desktop hosts in one VNet need to reach an Azure Files private endpoint hosted in a peered VNet. Choose the most appropriate implementation.
Review VNet peering, private DNS links, NSGs and routing for the endpoint path. A private endpoint is reachable only when name resolution and permitted routing converge on its private address. This action directly addresses the conditions in the scenario.
Compare client geography and Azure region round-trip latency before selecting a better session-host placement. This would be appropriate for the different task-specific situation "Users in a distant geography report high interactive latency while all session hosts are placed in one remote Azure region", because Remote display performance depends on round-trip distance as well as application resource allocation. It does not directly resolve the stated condition, which calls for Review VNet peering, private DNS links, NSGs and routing for the endpoint path.
Verify supported RDP Multipath client versions and monitor transport failover events. This would be appropriate for the different task-specific situation "Users report session drops when their laptops roam between Wi-Fi and mobile connectivity", because Multipath can switch among viable backup UDP or TCP paths when an active session route degrades. It does not directly resolve the stated condition, which calls for Review VNet peering, private DNS links, NSGs and routing for the endpoint path.
Validate managed-network RDP Shortpath prerequisites and permitted UDP reachability between client and session host. This would be appropriate for the different task-specific situation "Session hosts connect to an on-premises domain controller over ExpressRoute but user sessions still take TCP reverse-connect paths", because RDP Shortpath over a managed network can establish direct UDP transport when client and host have suitable private connectivity. It does not directly resolve the stated condition, which calls for Review VNet peering, private DNS links, NSGs and routing for the endpoint path.
The operations team reports the following symptom: A user requests that a powered-off personal VM start automatically when they open the remote desktop. Which action should be taken first?
Enable Start VM on Connect and validate the requisite AVD service identity permissions. Start VM on Connect powers on supported stopped hosts in response to AVD brokered connection demand. This action directly addresses the conditions in the scenario.
Use supported session management to disconnect or sign out the affected session after appropriate notification. This would be appropriate for the different task-specific situation "Help desk staff can see an active session that is unresponsive but do not want to delete its user profile", because Session control operations are separate from persistent profile storage and application group configuration. It does not directly resolve the stated condition, which calls for Enable Start VM on Connect and validate the requisite AVD service identity permissions.
Limit printer redirection or publish only approved printers in the remote environment. This would be appropriate for the different task-specific situation "Remote desktop users complain that every connection exposes all their local printers to a sensitive session", because Printer redirection can be restricted to reduce unnecessary device exposure and confusion. It does not directly resolve the stated condition, which calls for Enable Start VM on Connect and validate the requisite AVD service identity permissions.
Disable unapproved drive and USB redirection through supported RDP properties or policies. This would be appropriate for the different task-specific situation "Users can see local USB storage devices from the session host despite a data-loss-prevention requirement", because Device redirection may expose local client storage to remote applications unless explicitly restricted. It does not directly resolve the stated condition, which calls for Enable Start VM on Connect and validate the requisite AVD service identity permissions.
Consider this AVD design: One profile share serves users from different environments and has no permissions boundary between departments. The action is "Separate shares or enforce authorized group-based ACLs and share-level role assignments". Which statement explains this choice?
Isolation of users' profile data requires storage authorization in addition to Azure resource permissions. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
Encryption requirements can include explicit key control beyond platform default encryption-at-rest. This describes the separate situation "A profile storage solution must satisfy regulated encryption-at-rest policy with customer-managed keys" but does not justify the selected fix for the current issue. The decisive behavior is: Isolation of users' profile data requires storage authorization in addition to Azure resource permissions.
A private endpoint's existence does not automatically grant connectivity and name resolution from all peered networks. This describes the separate situation "An SMB private endpoint is reachable from one VNet but inaccessible from another peered workspace VNet" but does not justify the selected fix for the current issue. The decisive behavior is: Isolation of users' profile data requires storage authorization in addition to Azure resource permissions.
User profile container consumption depends on application behavior and retention, not only license count. This describes the separate situation "An organization estimates FSLogix capacity using only the number of users and ignores expected application caches" but does not justify the selected fix for the current issue. The decisive behavior is: Isolation of users' profile data requires storage authorization in addition to Azure resource permissions.
For a deployment problem, "The disaster recovery documentation contains a list of backup services but no tested routing or client reconnect process", administrators choose "Write and rehearse a complete failover runbook covering host pools, clients, DNS and user access". Why does that solve it?
End-to-end AVD continuity depends on restoring usable sessions, not merely confirming backups exist. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
Personal desktop recovery may require coordinating the VM, user assignment and profile container. This describes the separate situation "An organization needs to restore deleted personal desktops while keeping user profile data from separate storage" but does not justify the selected fix for the current issue. The decisive behavior is: End-to-end AVD continuity depends on restoring usable sessions, not merely confirming backups exist.
Immutable image release practices reduce long-term configuration divergence across a pooled fleet. This describes the separate situation "Session hosts are patched independently and their application versions drift away from the approved golden image" but does not justify the selected fix for the current issue. The decisive behavior is: End-to-end AVD continuity depends on restoring usable sessions, not merely confirming backups exist.
Update compliance monitoring helps verify that required OS fixes reach the intended session-host fleet. This describes the separate situation "A critical Windows update is required but administrators have no compliance report for AVD VMs" but does not justify the selected fix for the current issue. The decisive behavior is: End-to-end AVD continuity depends on restoring usable sessions, not merely confirming backups exist.
A platform team addresses "A forced-tunnel route sends all AVD session-host egress to an on-premises firewall that blocks required service traffic" with "Review user-defined routes and allow required AVD service endpoints through the approved inspection path". Which technical detail justifies the response?
Routing required control traffic into an unprepared firewall can disrupt AVD broker and agent communication. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
Session-host agents require reliable machine-level service connectivity even when no user is signed in. This describes the separate situation "A web filtering proxy requires interactive authentication and prevents unattended AVD agent HTTPS communication" but does not justify the selected fix for the current issue. The decisive behavior is: Routing required control traffic into an unprepared firewall can disrupt AVD broker and agent communication.
Multipath can switch among viable backup UDP or TCP paths when an active session route degrades. This describes the separate situation "Users report session drops when their laptops roam between Wi-Fi and mobile connectivity" but does not justify the selected fix for the current issue. The decisive behavior is: Routing required control traffic into an unprepared firewall can disrupt AVD broker and agent communication.
RDP Multipath feature availability depends on supported client platforms and minimum Windows App versions. This describes the separate situation "Windows App clients running obsolete builds do not display the expected RDP Multipath transport options" but does not justify the selected fix for the current issue. The decisive behavior is: Routing required control traffic into an unprepared firewall can disrupt AVD broker and agent communication.
The approved remediation for "A failed primary Azure region requires users to reach precreated secondary host pools" is "Prepare alternate workspace or host pool access and validated user entitlement during regional failover". Which Azure or Windows behavior explains this?
AVD recovery requires both healthy secondary session hosts and discoverable authorized desktop resources. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
Point-in-time snapshots help recover profile volumes from accidental modification or corruption. This describes the separate situation "Azure NetApp Files stores FSLogix data but no immutable recovery schedule is defined" but does not justify the selected fix for the current issue. The decisive behavior is: AVD recovery requires both healthy secondary session hosts and discoverable authorized desktop resources.
Controlled rollback minimizes user disruption while the incompatible image change is investigated. This describes the separate situation "A new AVD image release changes an agent component and only a subset of hosts can reconnect" but does not justify the selected fix for the current issue. The decisive behavior is: AVD recovery requires both healthy secondary session hosts and discoverable authorized desktop resources.
Update rings and drain procedures reduce the number of users affected by bad or disruptive updates. This describes the separate situation "A production pooled host pool needs monthly Windows security updates with minimal user disruption" but does not justify the selected fix for the current issue. The decisive behavior is: AVD recovery requires both healthy secondary session hosts and discoverable authorized desktop resources.
An architect must address this AVD condition: An admin excludes the entire user profile from FSLogix roaming to reduce storage cost. What should the team implement?
Use narrow documented exclusions and preserve persistent user folders and application settings. Overly broad exclusions undermine the purpose of a roaming profile container. This action directly addresses the conditions in the scenario.
Use supported FSLogix storage plus an independently tested snapshot and backup strategy. This would be appropriate for the different task-specific situation "A tenant wants both profile portability and recoverable historical profile data", because FSLogix provides profile roaming, while separate storage protection covers deletion and corruption recovery. It does not directly resolve the stated condition, which calls for Use narrow documented exclusions and preserve persistent user folders and application settings.
Implement FSLogix App Masking rule sets and assign their scope through user groups. This would be appropriate for the different task-specific situation "An application that is installed on all pooled session hosts must be hidden from nonlicensed users", because App Masking can control application visibility without reinstalling the app per user. It does not directly resolve the stated condition, which calls for Use narrow documented exclusions and preserve persistent user folders and application settings.
Configure a compatible FSLogix ODFC container for relevant Microsoft 365 data. This would be appropriate for the different task-specific situation "An organization uses a third-party profile method but needs Outlook and other Office cache data to roam", because ODFC targets specific Office application data rather than replacing the full Windows user profile. It does not directly resolve the stated condition, which calls for Use narrow documented exclusions and preserve persistent user folders and application settings.
The team adopts "Configure breadth-first load balancing in the pooled host pool" for this AVD requirement: "A finance department prioritizes even interactive responsiveness by distributing users across healthy hosts". Which explanation is correct?
Breadth-first spreads new sessions across available hosts to balance user counts instead of packing hosts tightly. This is the specific underlying behavior that makes the proposed remediation fit the stated problem.
A single resource-intensive app does not by itself prove every user needs dedicated desktop infrastructure. This describes the separate situation "A planning team proposes replacing all pooled desktops with personal VMs after noticing one application's high CPU use" but does not justify the selected fix for the current issue. The decisive behavior is: Breadth-first spreads new sessions across available hosts to balance user counts instead of packing hosts tightly.
AVD control-plane resource location and virtual machine compute location are distinct design choices. This describes the separate situation "Administrators confuse the host pool's Azure region with the physical region of each session host VM" but does not justify the selected fix for the current issue. The decisive behavior is: Breadth-first spreads new sessions across available hosts to balance user counts instead of packing hosts tightly.
Azure VM SKU and GPU availability varies by region and subscription quota. This describes the separate situation "A customer requires GPU-intensive design apps but cannot find its selected GPU VM family in the planned region" but does not justify the selected fix for the current issue. The decisive behavior is: Breadth-first spreads new sessions across available hosts to balance user counts instead of packing hosts tightly.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
