CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Google
  5. Google Cloud Architect Professional

Free Google Cloud Architect Professional Exam Braindumps (page: 14)

Page 13 of 68
PDF with 278 Questions
View Related Case Study

TerramEarth has a legacy web application that you cannot migrate to cloud. However, you still want to build a cloud-native way to monitor the application. If the application goes down, you want the URL to point to a "Site is unavailable" page as soon as possible. You also want your Ops team to receive a notification for the issue. You need to build a reliable solution for minimum cost What should you do?

  1. Create a scheduled job in Cloud Run to invoke a container every minute. The container will check the application URL If the application is down, switch the URL to the "Site is unavailable" page, and notify the Ops team.
  2. Create a cron job on a Compute Engine VM that runs every minute. The cron job invokes a Python program to check the application URL If the application is down, switch the URL to the "Site is unavailable" page, and notify the Ops team.
  3. Create a Cloud Monitoring uptime check to validate the application URL If it fails, put a message in a Pub/Sub queue that triggers a Cloud Function to switch the URL to the "Site is unavailable" page, and notify the Ops team.
  4. Use Cloud Error Reporting to check the application URL If the application is down, switch the URL to the "Site is unavailable" page, and notify the Ops team.

Answer(s): C

Explanation:

https://cloud.google.com/blog/products/management-tools/how-to-use-pubsub-as-a-cloud- monitoring-notification-channel



View Related Case Study

You are migrating a Linux-based application from your private data center to Google Cloud. The TerramEarth security team sent you several recent Linux vulnerabilities published by Common Vulnerabilities and Exposures (CVE). You need assistance in understanding how these vulnerabilities could impact your migration.
What should you do?

  1. Open a support case regarding the CVE and chat with the support engineer.
  2. Read the CVEs from the Google Cloud Status Dashboard to understand the impact.
  3. Read the CVEs from the Google Cloud Platform Security Bulletins to understand the impact
  4. Post a question regarding the CVE in Stack Overflow to get an explanation
  5. Post a question regarding the CVE in a Google Cloud discussion group to get an explanation

Answer(s): A,C

Explanation:

https://cloud.google.com/support/bulletins



View Related Case Study

You have broken down a legacy monolithic application into a few containerized RESTful microservices. You want to run those microservices on Cloud Run. You also want to make sure the services are highly available with low latency to your customers.
What should you do?

  1. Deploy Cloud Run services to multiple availability zones. Create Cloud Endpoints that point to the services. Create a global HTIP(S) Load Balancing instance and attach the Cloud Endpoints to its backend.
  2. Deploy Cloud Run services to multiple regions Create serverless network endpoint groups pointing to the services. Add the serverless NE Gs to a backend service that is used by a global HTIP(S) Load Balancing instance.
  3. Cloud Run services to multiple regions. In Cloud DNS, create a latency-based DNS name that points to the services.
  4. Deploy Cloud Run services to multiple availability zones. Create a TCP/IP global load balancer. Add the Cloud Run Endpoints to its backend service.

Answer(s): B

Explanation:

https://cloud.google.com/run/docs/multiple-regions



View Related Case Study

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?

  1. 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.
  2. 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.
  3. Make func _query 'Require authentication' and only accept internal traffic. Create those two functions in the same VP Create an ingress firewall rule for func_query to only allow traffic from func_display.
  4. 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.

Answer(s): B

Explanation:

https://cloud.google.com/functions/docs/securing/authenticating#authenticating_function_to_func tion_calls






Post your Comments and Discuss Google Google Cloud Architect Professional exam with other Community members:

Google Cloud Architect Professional Discussions & Posts