RemoteApp Application Source for Session-Only Availability

Install and configure apps on a session host

Answer Correct answer: D — Use app attach as the application source to dynamically deliver the application only during the user session.

You have an Azure Virtual Desktop deployment. You need to add a new application for a RemoteApp application group. The application must be available only during a user session. What should you use as an application source?

FSLogix Profile Container
file path
start menu
app attach Correct Answer

Community Votes

67%

33%

67% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

This question tests the difference between locally installed applications and dynamically delivered applications in AVD; the trap is choosing a local source like file path when the requirement specifies session-only availability.

Determining the correct application source for a RemoteApp application group in Azure Virtual Desktop when the application must be available only during a user session. This page establishes that app attach is required to dynamically deliver the app without permanent installation.

Choosing 'file path' (B) because it is a standard method for publishing RemoteApps, but it requires the app to be permanently installed on the session host, violating the session-only constraint.

Community Discussion (7 comments)

Dahkoht 👍 1 Selected: B

Most references seem to state remote app being the specific type of app is more frequently published with the file path , thus leaning towards B on this one.

97cbe9c 👍 1 Selected: D

The application must be available ONLY during a user session. That means that the application is NOT installed on the session host but streamed to the user session. Answer is D app attach

mr_Mojo 👍 3 Selected: D

D. app attach Explanation: "For RemoteApp application groups, you publish applications to stream remotely that are installed locally on session hosts or delivered dynamically using app attach and MSIX app attach and presented to users as individual applications in one of the supported Remote Desktop clients." https://learn.microsoft.com/en-us/azure/virtual-desktop/publish-applications-stream-remoteapp

mr_Mojo 👍 2 Selected: D

According to Copilot and ChatGPT, the correct answer is: D. app attach. "App attach allows you to dynamically deliver applications to users during their session without installing them directly on the session host. This makes the application available only during the user session, meeting your requirement."

jeff1988 👍 2 Selected: B

To add a new application for a RemoteApp application group in Azure Virtual Desktop and ensure it is available only during a user session, you should use the file path as the application source. These options allow you to specify applications that are installed locally on the session hosts and make them available to users during their sessions.

Bonesurfer 👍 2

I also vote for B. Using a file path as the application source for a RemoteApp application group to make the application available only during a user session. This approach is straightforward and minimizes setup complexity. App attach is ideal for virtualizing applications but isn't directly used to publish applications in a RemoteApp application group. https://learn.microsoft.com/en-us/azure/virtual-desktop/publish-applications-stream-remoteapp?tabs=portal#add-applications-to-a-remoteapp-application-group

Darkphoenix126 👍 4

According to Copilot: You should use B. file path as the application source. This approach ensures the application is available only during the user's session by specifying the exact executable path for the RemoteApp.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

App attach (formerly MSIX app attach) is the Azure Virtual Desktop feature designed to dynamically deliver applications to a user session. When an application is delivered via app attach, it is not permanently installed on the session host image; it is attached only when the user logs in and detached when they log out. This perfectly satisfies the requirement that the application must be available only during a user session.

Why the Other Options Are Wrong

Using a "file path" (B) or "start menu" (C) as an application source requires the application to be permanently installed on the session host. While these are valid sources for RemoteApp application groups, the applications are persistently present on the host, not just during the session. "FSLogix Profile Container" (A) is used for roaming user profiles and application data, not as an application source for publishing RemoteApps.

Community Comment Notes

Several users debated between file path and app attach. As one user noted, "App attach allows you to dynamically deliver applications to users during their session without installing them directly on the session host." Another user correctly pointed out that if the application must be available ONLY during a session, "that means that the application is NOT installed on the session host but streamed to the user session." Those advocating for file path missed the strict "only during a user session" constraint.

Official Reference

https://learn.microsoft.com/en-us/azure/virtual-desktop/publish-applications-stream-remotely

Exam Strategy

Pay close attention to keywords like 'only during a user session' which imply dynamic, non-persistent delivery. If an application must not be permanently installed on the session host, app attach is the required mechanism in AVD.

Related Analysis

Practice All AZ-140 Questions

Access 64 questions with complete answers and detailed explanations.

View Full AZ-140 Practice Test →

← Back to AZ-140 Study Guide