You are implementing MSIX app attach for a pooled host pool. ContosoApp.msix is expanded into a VHDX stored on an Azure Files share that uses Active Directory authentication. Users sign in but do not see the app; the package shows Not registered. Which two actions are required to allow the package to be staged and registered? Choose two answers.

For MSIX app attach to function correctly, two critical steps are needed. First, the MSIX package signing certificate's public certificate must be installed into the Local Computer Trusted People certificate store on all session hosts. This allows the operating system to trust the application package and successfully stage it. Without this, the package will show as "Not registered" because its signature cannot be validated. Second, the session host computer accounts (or a group they belong to) require Read share and NTFS permissions on the Azure Files share where the VHDX is stored. This enables the session hosts to access and mount the VHDX containing the application. Incorrect options: Converting VHDX to VHD is unnecessary; VHDX is the standard format. Copying the VHDX to the C: drive defeats the purpose of centralized storage and MSIX app attach. The App-V client is unrelated to MSIX app attach.