You are managing a few hundred Ubuntu and Red Hat Enterprise Linux virtual machines running on Google Compute Engine (GCE). You need to patch the operating systems for those VMs periodically in a secure and scalable way. What should you do?
Answer(s): D
D — Set up VM Manager, and install the OS Config agent on each VM. Schedule a patch job to apply patches on each VM.When managing hundreds of Ubuntu and RHEL VMs on Google Compute Engine, you need a solution that is:Secure (no SSH key sprawl or custom scripts)Scalable (works across many VMs)Automated & manageable (centralized patching, reporting, and scheduling)Google Cloud provides a native service that does exactly this: VM Manager (OS Config).
Your company uses Salesforce for customer relationship management (CRM). ServiceNow for IT service management, and a Cloud SQL database to store customer transaction data You need to seamlessly connect, map. and transform data between these systems to ensure data consistency and enable real-time reporting. You want to follow Google-recommended practices. What should you do?
Answer(s): B
B: Leverage Application Integration to connect the services and transform the data. Google Cloud's Application Integration is a fully managed, no-code/low-code Integration-Platform-as-a-Service (iPaaS) solution designed specifically for integrating various business systems, such as CRM, ITSM, and databases.
You are designing the architecture for a global social media site on Google Cloud. The site serves dynamic API content, static assets such as CSS. JS. images, and user-uploaded videos for streaming. You need to minimize latency for all content types for users worldwide. What should you do? (Choose two.)
Answer(s): A,B
A: External Application Load Balancer .It is globally distributed and uses Google’s premium global networkRoutes users to the nearest healthy backendIdeal for dynamic API trafficSupports HTTPS, TLS termination, and advanced routingThis is the recommended front end for global, latency-sensitive web applications.B: Cloud CDN .Caches static assets (CSS, JS, images) at Google’s edge locationsReduces latency and backend loadIntegrates natively with the external Application Load BalancerServes users from the closest edge point of presence
You are creating a migration plan to move your organization’s infrastructure from on-premises to Google Cloud. You want to understand and manage costs effectively after the migration is complete. Which strategies should you include in the migration plan? (Choose two.)
Answer(s): B,E
Why B and E are the optimal choicesB – Configure labels and tags for the resources provisioned in Google CloudLabels and tags provide a granular, cost-allocation mechanism that lets you attribute spend to specific business units, projects, environments, or workloads. They integrate natively with Cost Management → Reports and BigQuery export , enabling automated cost-allocation dashboards, budgeting alerts, and rights-izing recommendations. By enforcing a tagging policy early in the migration, you avoid “un-tagged” resources that would otherwise be invisible in cost reports, ensuring accurate forecasting and chargeback.E – Adopt infrastructure as code (IaC) for the cloud resourcesIaC (e.g., Terraform, Deployment Manager, or Pulumi) codifies the entire resource topology, making provisioning repeatable, version-controlled, and auditable. This approach supports cost-optimization by allowing you to:1. Apply consistent sizing standards (e.g., using predefined instance templates). 2. Automate de-provisioning or autoscaling policies. 3. Perform “what-if” cost simulations before deployment. IaC also reduces manual errors that can lead to over-provisioned or orphaned resources, directly contributing to lower operational spend.Why the other options are less suitableA – Enable Backup and DR Service – While essential for data protection, backup/DR does not directly influence ongoing cost-management after migration; it adds storage and compute overhead without providing cost-allocation insight.C – Create a Cloud Scheduler job to export billing data to Cloud SQL – Exporting billing data is a valid data-collection technique, but it is merely a mechanism for reporting, not a strategy for managing or optimizing costs. It does not enforce cost-control policies or visibility.D – Create service alerts using Cloud Monitoring – Alerts are useful for operational health and anomaly detection, yet they are not a primary tool for cost governance. They can surface spikes but do not provide the systematic allocation, budgeting, or optimization capabilities that labels/tags and IaC deliver.Conclusion In a post-migration cost-management plan, the two most effective strategies are labeling/tagging to achieve precise cost attribution and IaC to enforce disciplined, repeatable, and cost-optimized provisioning. These directly address visibility, accountability, and optimization—key pillars of sustainable cloud financial management.
A Cloud Run service running your serverless application is unable to connect to an AlloyDB database created with default configurations. You need to troubleshoot and resolve the issue as quickly as possible. What should you do?
B — Enable Direct VPC egress for the Cloud Run service, and send traffic directly to a VPCBy default, a Cloud Run service:Runs in a fully managed, serverless environmentDoes not have direct access to your VPC networkUses public egress unless configured otherwiseMeanwhile, an AlloyDB instance created with default settings:Uses a private IPIs accessible only from within a VPCThis network mismatch prevents Cloud Run from connecting to AlloyDB.
Post your Comments and Discuss Google Google Cloud Architect Professional exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Google Cloud Architect Professional content, but please register or login to continue.