Google Certified Professional Cloud Architect (GCP) Exam (PROFESSIONAL-CLOUD-ARCHITECT) - Google Cloud Actual Exam Questions
Last updated on May 11, 2026
Your company recently acquired a company that has infrastructure in Google Cloud. Each company has its own Google Cloud organization Each company is using a Shared Virtual Private Cloud (VPC) to provide network connectivity tor its applications Some of the subnets used by both companies overlap In order for both businesses to integrate, the applications need to have private network connectivity. These applications are not on overlapping subnets. You want to provide connectivity with minimal re-engineering. What should you do?
Set up VPC peering and peer each Shared VPC together
Configure SSH port forwarding on each application to provide connectivity between applications i the different Shared VPCs
Migrate the protects from the acquired company into your company's Google Cloud organization Re launch the instances in your companies Shared VPC
Set up a Cloud VPN gateway in each Shared VPC and peer Cloud VPNs
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
For this question, refer to the TerramEarth case study. You start to build a new application that uses a few Cloud Functions for the backend. One use case requires a Cloud Function func_display to invoke another Cloud Function func_query. You want func_query only to accept invocations from func_display. You also want to follow Google's recommended best practices. What should you do?
Create a token and pass it in as an environment variable to func_display. When invoking func_query, include the token in the request Pass the same token to func _query and reject the invocation if the tokens are different.
Make func_query 'Require authentication.' Create a unique service account and associate it to func_display. Grant the service account invoker role for func_query. Create an id token in func_display and include the token to the request when invoking func_query.
Make func _query 'Require authentication' and only accept internal traffic. Create those two functions in the same VPC. Create an ingress firewall rule for func_query to only allow traffic from func_display.
Create those two functions in the same project and VPC. Make func_query only accept internal traffic. Create an ingress firewall for func_query to only allow traffic from func_display. Also, make sure both functions use the same service account.
downtime is loss of players. Increase efficiency of the cloud resources we use. Reduce latency to all customers. Technical Requirements Requirements for Game Backend Platform Dynamically scale up or down based on game activity. Connect to a transactional database service to manage user profiles and game state. Store game activity in a timeseries database service for future analysis. As the system scales, ensure that data is not lost due to processing backlogs. Run hardened Linux distro. Requirements for Game Analytics Platform Dynamically scale up or down based on game activity Process incoming data on the fly directly from the game servers Process data that arrives late because of slow mobile networks Allow queries to access at least 10 TB of historical data Process files that are regularly uploaded by users’ mobile devices Executive Statement Our last successful game did not scale well with our previous cloud provider, resulting in lower user adoption and affecting the game’s reputation. Our investors want more key performance indicators (KPIs) to evaluate the speed and stability of the game, as well as other metrics that provide deeper insight into usage patterns so we can adapt the game to target users. Additionally, our current technology stack cannot provide the scale we need, so we want to replace MySQL and move to an environment that provides autoscaling, low latency load balancing, and frees us up from managing physical servers.
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Your company has multiple on-premises systems that serve as sources for reporting. The data has not been maintained well and has become degraded over time. You want to use Google-recommended practices to detect anomalies in your company dat a. What should you do?
Upload your files into Cloud Storage. Use Cloud Datalab to explore and clean your data.
Upload your files into Cloud Storage. Use Cloud Dataprep to explore and clean your data.
Connect Cloud Datalab to your on-premises systems. Use Cloud Datalab to explore and clean your data.
Connect Cloud Dataprep to your on-premises systems. Use Cloud Dataprep to explore and clean your data.
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
For this question, refer to the Dress4Win case study. Dress4Win has configured a new uptime check with Google Stackdriver for several of their legacy services. The Stackdriver dashboard is not reporting the services as healthy. What should they do?
Install the Stackdriver agent on all of the legacy web servers.
In the Cloud Platform Console download the list of the uptime servers' IP addresses and create an inbound firewall rule
Configure their load balancer to pass through the User-Agent HTTP header when the value matches GoogleStackdriverMonitoring-UptimeChecks (https://cloud.google.com/monitoring)
Configure their legacy web servers to allow requests that contain user-Agent HTTP header when the value matches GoogleStackdriverMonitoring— UptimeChecks (https://cloud.google.com/monitoring)
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Your customer is receiving reports that their recently updated Google App Engine application is taking approximately 30 seconds to load for some of their users. This behavior was not reported before the update. What strategy should you take?
Work with your ISP to diagnose the problem.
Open a support ticket to ask for network capture and flow data to diagnose the problem, then roll back your application.
Roll back to an earlier known good release initially, then use Stackdriver Trace and logging to diagnose the problem in a development/test/staging environment.
Roll back to an earlier known good release, then push the release again at a quieter period to investigate. Then use Stackdriver Trace and logging to diagnose the problem.
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Finish Practice?
Are you sure you want to finish? This will end your practice session.