You are migrating a telehealth care company's on-premises data center to Google Cloud. The migration plan specifies: PostgreSQL databases must be migrated to a multi-region backup configuration with…

Question

Options

• ASet up Cloud Logging and Cloud Monitoring with Cloud Functions to send an alert every time a
• BSet up different organizations for each database type, and apply policy constraints at the
• CSet up Pub/Sub to ingest data from Cloud Logging, send an alert every time a new database
• DSet up different projects for PostgreSQL and MySQL databases, and apply organizational policy

• B
  13% (2)
• C
  6% (1)
• D
  81% (13)

Explanation

Setting up separate projects for PostgreSQL and MySQL databases and applying organizational policy constraints at the project level is the correct approach. Google Cloud's Organization Policy Service allows you to enforce constraints (such as restricting resource locations) at different levels of the resource hierarchy - organization, folder, or project. By placing PostgreSQL databases in a project with a policy that allows multi-region configurations and cross-region replicas, and placing MySQL databases in a separate project with a policy that restricts resources to a single approved region for data residency compliance, you achieve both requirements with minimal ongoing administrative effort. Options A and C are monitoring/alerting approaches that detect violations after they occur but do not proactively prevent non-compliant configurations. Option B (separate organizations) is technically possible but is unnecessarily complex, expensive to manage, and far exceeds the administrative overhead needed - separate projects under one organization are sufficient and are the Google-recommended approach.

No community discussion yet for this question.