McAfee-Secured Website

Exam Bundle

Exam Code: AZ-140

Exam Name Configuring and Operating Microsoft Azure Virtual Desktop

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Virtual Desktop Specialty

Microsoft AZ-140 Bundle $44.99

100% Microsoft AZ-140 Guaranteed Success With Testking Training Materials

Get Real AZ-140 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-140 Questions & Answers

    372 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-140 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-140 Video Course

    AZ-140 Video Course

    79 Video Lectures

    AZ-140 Video Course is developed by Microsoft Professionals to help you pass the AZ-140 exam.

    Description

    This course will improve your knowledge and skills required to pass Configuring and Operating Microsoft Azure Virtual Desktop exam.
  • Study Guide

    AZ-140 Study Guide

    430 PDF Pages

    Developed by industry experts, this 430-page guide spells out in painstaking detail all of the information you need to ace AZ-140 exam.

Configuring and Operating Microsoft Azure Virtual Desktop (AZ-140) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    372 Questions

    $124.99
  • AZ-140 Video Course

    Video Course

    79 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    430 PDF Pages

    $29.99

Microsoft AZ-140 Practice Test 33

Question 320

In the Parkside Commerce pilot environment, a controlled verification is required for: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. What evidence best demonstrates that the reported AVD issue is resolved?

  1. The pilot host joins Entra, registers in AVD, and allows an entitled Entra user to complete a supported desktop sign-in.
  2. A user changes the authorized print setting but cannot install a privileged driver or modify protected system files.
  3. The technician can manage designated user sessions while a test attempt to delete unrelated VM resources is denied.
  4. A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path.

Explanation

Correct Answer

D:

A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path. This is an independently observable result of the targeted change: Configure the supported managed-domain join, required DNS, password synchronization and profile-access prerequisites for the selected identity approach. It closes the specific Parkside Commerce failure: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically.

Incorrect Answers

A:

The pilot host joins Entra, registers in AVD, and allows an entitled Entra user to complete a supported desktop sign-in. This is evidence for a DIFFERENT remediation: Evaluate Microsoft Entra-joined AVD session hosts and supported identity and FSLogix scenarios before introducing unnecessary domain services. That remediation addresses: A fully cloud-managed company has no traditional AD DS deployment but the plan adds domain controllers only to register its modern AVD Windows hosts. It does not establish resolution of the Parkside Commerce problem: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. The required outcome here is: A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path.

B:

A user changes the authorized print setting but cannot install a privileged driver or modify protected system files. This is evidence for a DIFFERENT remediation: Apply specific user rights and device or printer policies without granting local administrator rights to standard desktop users. That remediation addresses: AVD session users receive local Administrators membership by default so they can change one printing preference, violating workstation least privilege. It does not establish resolution of the Parkside Commerce problem: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. The required outcome here is: A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path.

C:

The technician can manage designated user sessions while a test attempt to delete unrelated VM resources is denied. This is evidence for a DIFFERENT remediation: Assign a narrowly scoped built-in AVD RBAC role with only required session-management rights and remove the excessive Owner assignment. That remediation addresses: A service desk technician must sign out disconnected AVD sessions but receives broad subscription Owner rights to perform this routine task. It does not establish resolution of the Parkside Commerce problem: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. The required outcome here is: A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path.

Question 321

At Parkside Commerce, a ecommerce administration organization prioritizing reliable employee sign-in, administrators observe this issue: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. Which targeted engineering action most directly resolves the reported problem?

  1. Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes.
  2. Configure the supported managed-domain join, required DNS, password synchronization and profile-access prerequisites for the selected identity approach.
  3. Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in.
  4. Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy.

Explanation

Correct Answer

C:

Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. This directly addresses the Parkside Commerce failure: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The necessary acceptance evidence is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Incorrect Answers

A:

Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. This could resolve a DIFFERENT AVD issue: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. It does not fix the reported Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

B:

Configure the supported managed-domain join, required DNS, password synchronization and profile-access prerequisites for the selected identity approach. This could resolve a DIFFERENT AVD issue: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. It does not fix the reported Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

D:

Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy. This could resolve a DIFFERENT AVD issue: Remote contractors authenticate to AVD using passwords only despite a corporate requirement for phishing-resistant sign-in methods. It does not fix the reported Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Question 322

The ecommerce administration desktop team at Parkside Commerce requires independent proof of remediation for: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. What measurable result should the reviewer require before closing the incident?

  1. An approved passwordless user completes an AVD sign-in while a password-only control attempt is rejected as expected.
  2. Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.
  3. The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.
  4. A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path.

Explanation

Correct Answer

C:

The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication. This is an independently observable result of the targeted change: Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. It closes the specific Parkside Commerce failure: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration.

Incorrect Answers

A:

An approved passwordless user completes an AVD sign-in while a password-only control attempt is rejected as expected. This is evidence for a DIFFERENT remediation: Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy. That remediation addresses: Remote contractors authenticate to AVD using passwords only despite a corporate requirement for phishing-resistant sign-in methods. It does not establish resolution of the Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

B:

Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception. This is evidence for a DIFFERENT remediation: Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. That remediation addresses: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. It does not establish resolution of the Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

D:

A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path. This is evidence for a DIFFERENT remediation: Configure the supported managed-domain join, required DNS, password synchronization and profile-access prerequisites for the selected identity approach. That remediation addresses: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. It does not establish resolution of the Parkside Commerce problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Question 323

For the professional services workload at Bluewater Advisory, the host pool team reports: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. What is the most appropriate first corrective action for this AVD scenario?

  1. Assign the appropriate application group management role at the minimum resource scope required for that delegated responsibility.
  2. Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes.
  3. Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model.
  4. Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in.

Explanation

Correct Answer

D:

Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. This directly addresses the Bluewater Advisory failure: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The necessary acceptance evidence is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Incorrect Answers

A:

Assign the appropriate application group management role at the minimum resource scope required for that delegated responsibility. This could resolve a DIFFERENT AVD issue: A delegated team can read host pool settings but cannot create application group assignments because it lacks the necessary Desktop Virtualization role. It does not fix the reported Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

B:

Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. This could resolve a DIFFERENT AVD issue: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. It does not fix the reported Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

C:

Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. This could resolve a DIFFERENT AVD issue: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. It does not fix the reported Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The relevant proof here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Question 324

The Bluewater Advisory operations group needs acceptance evidence before signing off: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. Which outcome validates this fix rather than an unrelated system improvement?

  1. Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.
  2. The delegated operator can create a test assignment without gaining general resource group Contributor permissions.
  3. A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.
  4. The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Explanation

Correct Answer

D:

The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication. This is an independently observable result of the targeted change: Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. It closes the specific Bluewater Advisory failure: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration.

Incorrect Answers

A:

Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception. This is evidence for a DIFFERENT remediation: Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. That remediation addresses: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. It does not establish resolution of the Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

B:

The delegated operator can create a test assignment without gaining general resource group Contributor permissions. This is evidence for a DIFFERENT remediation: Assign the appropriate application group management role at the minimum resource scope required for that delegated responsibility. That remediation addresses: A delegated team can read host pool settings but cannot create application group assignments because it lacks the necessary Desktop Virtualization role. It does not establish resolution of the Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

C:

A signed-in pilot user mounts their authorized profile container without interactive network credential prompts. This is evidence for a DIFFERENT remediation: Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. That remediation addresses: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. It does not establish resolution of the Bluewater Advisory problem: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. The required outcome here is: The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.

Question 325

The virtual desktop support team at Stonewell Manufacturing investigates the following failure during a change review: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. How should the Azure Virtual Desktop administrator correct this specific failure?

  1. Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in.
  2. Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario.
  3. Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes.
  4. Use explicit compliant-device conditions, named exclusions, and tested emergency access design for the AVD Conditional Access deployment.

Explanation

Correct Answer

C:

Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. This directly addresses the Stonewell Manufacturing failure: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The necessary acceptance evidence is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Incorrect Answers

A:

Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. This could resolve a DIFFERENT AVD issue: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. It does not fix the reported Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

B:

Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario. This could resolve a DIFFERENT AVD issue: A Windows Server-backed AVD deployment depends on smart-card logon but the user is prompted for password because the certificate and identity path is incomplete. It does not fix the reported Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

D:

Use explicit compliant-device conditions, named exclusions, and tested emergency access design for the AVD Conditional Access deployment. This could resolve a DIFFERENT AVD issue: A Conditional Access rule blocks all desktop users from unsupported unmanaged devices, including the operations team that needs emergency recovery access. It does not fix the reported Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Question 326

An AVD incident at Stonewell Manufacturing can be closed only after proving that this issue is fixed: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. Which controlled test result independently verifies successful remediation?

  1. Noncompliant pilot devices are denied but designated recovery access succeeds and the policy's sign-in logs explain both decisions.
  2. A supported smart-card user authenticates successfully while an invalid certificate is denied without falling back silently.
  3. The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.
  4. Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Explanation

Correct Answer

D:

Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception. This is an independently observable result of the targeted change: Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. It closes the specific Stonewell Manufacturing failure: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver.

Incorrect Answers

A:

Noncompliant pilot devices are denied but designated recovery access succeeds and the policy's sign-in logs explain both decisions. This is evidence for a DIFFERENT remediation: Use explicit compliant-device conditions, named exclusions, and tested emergency access design for the AVD Conditional Access deployment. That remediation addresses: A Conditional Access rule blocks all desktop users from unsupported unmanaged devices, including the operations team that needs emergency recovery access. It does not establish resolution of the Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

B:

A supported smart-card user authenticates successfully while an invalid certificate is denied without falling back silently. This is evidence for a DIFFERENT remediation: Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario. That remediation addresses: A Windows Server-backed AVD deployment depends on smart-card logon but the user is prompted for password because the certificate and identity path is incomplete. It does not establish resolution of the Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

C:

The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication. This is evidence for a DIFFERENT remediation: Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. That remediation addresses: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. It does not establish resolution of the Stonewell Manufacturing problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Question 327

An AVD deployment review at Granite Network Team must resolve this condition while preserving secure private access: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. Which proposed implementation change best meets the documented requirement?

  1. Evaluate Microsoft Entra-joined AVD session hosts and supported identity and FSLogix scenarios before introducing unnecessary domain services.
  2. Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy.
  3. Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes.
  4. Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model.

Explanation

Correct Answer

C:

Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. This directly addresses the Granite Network Team failure: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The necessary acceptance evidence is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Incorrect Answers

A:

Evaluate Microsoft Entra-joined AVD session hosts and supported identity and FSLogix scenarios before introducing unnecessary domain services. This could resolve a DIFFERENT AVD issue: A fully cloud-managed company has no traditional AD DS deployment but the plan adds domain controllers only to register its modern AVD Windows hosts. It does not fix the reported Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

B:

Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy. This could resolve a DIFFERENT AVD issue: Remote contractors authenticate to AVD using passwords only despite a corporate requirement for phishing-resistant sign-in methods. It does not fix the reported Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

D:

Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. This could resolve a DIFFERENT AVD issue: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. It does not fix the reported Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The relevant proof here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Question 328

After corrective work at Granite Network Team, the acceptance reviewer tests this original failure: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. Which observed outcome is the strongest evidence that the correction worked?

  1. A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.
  2. The pilot host joins Entra, registers in AVD, and allows an entitled Entra user to complete a supported desktop sign-in.
  3. Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.
  4. An approved passwordless user completes an AVD sign-in while a password-only control attempt is rejected as expected.

Explanation

Correct Answer

C:

Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception. This is an independently observable result of the targeted change: Configure the session host's VNet DNS to resolve the AD DS domain and permit necessary directory connectivity through controlled routes. It closes the specific Granite Network Team failure: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver.

Incorrect Answers

A:

A signed-in pilot user mounts their authorized profile container without interactive network credential prompts. This is evidence for a DIFFERENT remediation: Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. That remediation addresses: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. It does not establish resolution of the Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

B:

The pilot host joins Entra, registers in AVD, and allows an entitled Entra user to complete a supported desktop sign-in. This is evidence for a DIFFERENT remediation: Evaluate Microsoft Entra-joined AVD session hosts and supported identity and FSLogix scenarios before introducing unnecessary domain services. That remediation addresses: A fully cloud-managed company has no traditional AD DS deployment but the plan adds domain controllers only to register its modern AVD Windows hosts. It does not establish resolution of the Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

D:

An approved passwordless user completes an AVD sign-in while a password-only control attempt is rejected as expected. This is evidence for a DIFFERENT remediation: Select supported Entra authentication methods such as passkeys or other phishing-resistant methods and enforce the requirement through policy. That remediation addresses: Remote contractors authenticate to AVD using passwords only despite a corporate requirement for phishing-resistant sign-in methods. It does not establish resolution of the Granite Network Team problem: AD DS joined session hosts deployed into a locked-down subnet cannot find a domain controller because their DNS configuration points to a public resolver. The required outcome here is: Domain discovery, secure channel checks, and a test AVD connection all succeed without a local hosts-file exception.

Question 329

During an Azure Virtual Desktop rollout for Northgate Collaboration, engineers document this operational problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. Which remediation addresses the root cause without making an unrelated configuration change?

  1. Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model.
  2. Audit supported Windows App, host OS, and Entra identity prerequisites for AVD single sign-on and remediate the incompatible component.
  3. Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in.
  4. Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario.

Explanation

Correct Answer

A:

Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. This directly addresses the Northgate Collaboration failure: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The necessary acceptance evidence is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

Incorrect Answers

B:

Audit supported Windows App, host OS, and Entra identity prerequisites for AVD single sign-on and remediate the incompatible component. This could resolve a DIFFERENT AVD issue: An administrator enables an SSO RDP property but client sign-in still requests another password because the session host and client versions do not meet prerequisites. It does not fix the reported Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The relevant proof here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

C:

Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. This could resolve a DIFFERENT AVD issue: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. It does not fix the reported Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The relevant proof here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

D:

Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario. This could resolve a DIFFERENT AVD issue: A Windows Server-backed AVD deployment depends on smart-card logon but the user is prompted for password because the certificate and identity path is incomplete. It does not fix the reported Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The relevant proof here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

Question 330

In the Northgate Collaboration pilot environment, a controlled verification is required for: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. What evidence best demonstrates that the reported AVD issue is resolved?

  1. A supported smart-card user authenticates successfully while an invalid certificate is denied without falling back silently.
  2. A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.
  3. The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication.
  4. The updated client and session host complete the same documented SSO flow without an unexpected second password prompt.

Explanation

Correct Answer

B:

A signed-in pilot user mounts their authorized profile container without interactive network credential prompts. This is an independently observable result of the targeted change: Implement the supported hybrid identity and Kerberos or cloud Kerberos trust path for the selected file share and session-host identity model. It closes the specific Northgate Collaboration failure: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares.

Incorrect Answers

A:

A supported smart-card user authenticates successfully while an invalid certificate is denied without falling back silently. This is evidence for a DIFFERENT remediation: Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario. That remediation addresses: A Windows Server-backed AVD deployment depends on smart-card logon but the user is prompted for password because the certificate and identity path is incomplete. It does not establish resolution of the Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The required outcome here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

C:

The VM reports expected Entra join and AVD agent health and the eligible test user completes authentication. This is evidence for a DIFFERENT remediation: Apply the current Entra-join prerequisites and compatible session-host deployment settings for the host pool and client sign-in. That remediation addresses: A newly enrolled Entra-joined AVD VM cannot register because the selected image and join workflow omit the required supported identity configuration. It does not establish resolution of the Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The required outcome here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.

D:

The updated client and session host complete the same documented SSO flow without an unexpected second password prompt. This is evidence for a DIFFERENT remediation: Audit supported Windows App, host OS, and Entra identity prerequisites for AVD single sign-on and remediate the incompatible component. That remediation addresses: An administrator enables an SSO RDP property but client sign-in still requests another password because the session host and client versions do not meet prerequisites. It does not establish resolution of the Northgate Collaboration problem: A hybrid desktop rollout assumes Microsoft Entra-only access automatically provides SMB Kerberos credentials for traditional on-prem FSLogix shares. The required outcome here is: A signed-in pilot user mounts their authorized profile container without interactive network credential prompts.