Q: 11
Your organization is currently updating an existing corporate application that is running in another
public cloud to access managed database services in Google Cloud. The application will remain in the
other public cloud while the database is migrated to Google Cloud. You want to follow Google-
recommended practices for authentication. You need to minimize user disruption during the
migration. What should you do?
Options
Discussion
Its A, workload identity federation lets you securely connect the app from another cloud without messing with user passwords. B and D would force password changes or syncs, which Google doesn't recommend. C isn't needed if the app isn't moving yet.
A not D. D is a trap because Google Workspace Password Sync is for syncing user passwords, which isn't what managed service access from another cloud needs. A fits Google's own advice if you're keeping the app external.
Its A, really clear scenario. Workload identity federation matches Google best practices for minimal disruption.
Be respectful. No spam.
