The city must stop password authentication on the finance Hub app but still allow password on the cafeteria menu app. What is the correct Access change?
Select an answer to reveal the explanation.
Short Explanation
Authentication methods are like keys on a ring: you keep the key, you just do not hang it on the finance door. Leave password enabled, drop it from the finance policy, and keep it on the cafeteria policy—do not melt the key for the whole city.
Full Explanation
Workspace ONE Access authentication methods are enabled at the tenant, then associated per access policy and application. Removing password from the finance policy while leaving the method enabled lets other apps, such as the cafeteria menu, still use it. Globally disabling password or deleting the built-in identity provider is too blunt and breaks every password path. An NSX deny of HTTPS is not how Access method association is done.