Payroll and recruitment executables are installed on all pooled hosts and published as standard RemoteApps in one application group. Members assigned to that group can discover both. The requirement is separate publication entitlement for the payroll and recruitment populations. What should change?

✓ Correct answer

• Place the application sets in separate RemoteApp groups and assign the corresponding populations.

Standard RemoteApp entitlement is assigned at application-group level. Separate groups provide the required assignment boundary between the two application sets. Option explanations: A. Use the host pool’s Preferred application group type to choose an executable per user.: The preference selects Desktop versus RemoteApp presentation for dual-assigned users, not individual executables. B. Place the application sets in separate RemoteApp groups and assign the corresponding populations.: Separate group assignments let each population discover its authorized published application set. C. Create a user assignment directly on each standard executable entry inside the same group.: The standard model does not use an independent per-app user assignment inside one application group. D. Grant the payroll users Desktop Virtualization Contributor.: A management role grants unnecessary privileges and does not implement the intended publication boundary. Sources: Publish applications with RemoteApp — https://learn.microsoft.com/azure/virtual-desktop/publish-applications-stream-remoteapp; Preferred application group type behavior — https://learn.microsoft.com/azure/virtual-desktop/preferred-application-group-type

Read the source reference