Free Google Professional-Cloud-Architect Exam Dumps Questions & Answers

For this question, refer to the Mountkirk Games case study.
Mountkirk Games wants to set up a continuous delivery pipeline. Their architecture includes many small services that they want to be able to update and roll back quickly. Mountkirk Games has the following requirements:
* Services are deployed redundantly across multiple regions in the US and Europe.
* Only frontend services are exposed on the public internet.
* They can provide a single frontend IP for their fleet of services.
* Deployment artifacts are immutable.
Which set of products should they use?

• A.  Google Kubernetes Registry, Google Container Engine, Google HTTP(S) Load Balancer
• B.  Google Cloud Functions, Google Cloud Pub/Sub, Google Cloud Deployment Manager
• C.  Google Cloud Storage, Google App Engine, Google Network Load Balancer
• D.  Google Cloud Storage, Google Cloud Dataflow, Google Compute Engine

You need to implement a network ingress for a new game that meets the defined business and technical requirements. Mountkirk Games wants each regional game instance to be located in multiple Google Cloud regions. What should you do?

• A.  Configure a global load balancer with Google Kubernetes Engine.
• B.  Configure kubemci with a global load balancer and Google Kubernetes Engine.
• C.  Configure a global load balancer connected to a managed instance group running Compute Engine instances.
• D.  Configure Ingress for Anthos with a global load balancer and Google Kubernetes Engine.

For this question, refer to the EHR Healthcare case study. You need to define the technical architecture for hybrid connectivity between EHR ' s on-premises systems and Google Cloud. You want to follow Google ' s recommended practices for production-level applications. Considering the EHR Healthcare business and technical requirements, what should you do?

• A.  Configure two Partner Interconnect connections in one metro (City), and make sure the Interconnect connections are placed in different metro zones.
• B.  Configure two VPN connections from on-premises to Google Cloud, and make sure the VPN devices on-premises are in separate racks.
• C.  Configure Direct Peering between EHR Healthcare and Google Cloud, and make sure you are peering at least two Google locations.
• D.  Configure two Dedicated Interconnect connections in one metro (City) and two connections in another metro, and make sure the Interconnect connections are placed in different metro zones.

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?

• A.  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.
• B.  Work with your ISP to diagnose the problem.
• C.  Open a support ticket to ask for network capture and flow data to diagnose the problem, then roll back your application.
• D.  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.

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?

• A.  In the Cloud Platform Console download the list of the uptime servers ' IP addresses and create an inbound firewall rule
• B.  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)
• C.  Configure their load balancer to pass through the User-Agent HTTP header when the value matches GoogleStackdriverMonitoring-UptimeChecks (https://cloud.google.com/monitoring)
• D.  Install the Stackdriver agent on all of the legacy web servers.