Question: 1
Your solution is producing performance bugs in production that you did not see in staging and test
environments. You want to adjust your test and deployment procedures to avoid this problem in the
future. What should you do?
A. Deploy fewer changes to production.
B. Deploy smaller changes to production.
C. Increase the load on your test and staging environments.
D. Deploy changes to a small subset of users before rolling out to production.
Answer: D
Question: 2
Your company has decided to make a major revision of their API in order to create better experiences
for their developers. They need to keep the old version of the API available and deployable, while
allowing new customers and testers to try out the new API. They want to keep the same SSL and DNS
records in place to serve both APIs. What should they do?
A. Configure a new load balancer for the new version of the API.
B. Reconfigure old clients to use a new endpoint for the new API.
C. Have the old API forward traffic to the new API based on the path.
D. Use separate backend pools for each API path behind the load balancer.
Answer: D
https://cloud.google.com/endpoints/docs/openapi/lifecycle-management
Question: 3
A small number of API requests to your microservices-based application take a very long time. You know that each request to the API can traverse many services. You want to know which service takes the longest in those cases. What should you do?
A. Set timeouts on your application so that you can fail requests faster.
B. Send custom metrics for each of your requests to Stackdriver Monitoring.
C. Use Stackdriver Monitoring to look for insights that show when your API latencies are high.
D. Instrument your application with Stackdnver Trace in order to break down the request latencies at
each microservice.
Answer: D
https://cloud.google.com/trace/docs/overview
Question: 4
During a high traffic portion of the day, one of your relational databases crashes, but the replica is never
promoted to a master. You want to avoid this in the future. What should you do?
A. Use a different database.
B. Choose larger instances for your database.
C. Create snapshots of your database more regularly.
D. Implement routinely scheduled failovers of your databases.
Answer: C
Explanation:
Take regular snapshots of your database system.
If your database system lives on a Compute Engine persistent disk, you can take snapshots of your
system each time you upgrade. If your database system goes down or you need to roll back to a
previous version, you can simply create a new persistent disk from your desired snapshot and make that
disk the boot disk for a new Compute Engine instance. Note that, to avoid data corruption, this
approach requires you to freeze the database system's disk while taking a snapshot.
Reference: https://cloud.google.com/solutions/disaster-recovery-cookbook
Question: 5
Your organization requires that metrics from all applications be retained for 5 years for future analysis in
possible legal proceedings. Which approach should you use?
A. Grant the security team access to the logs in each Project.
B. Configure Stackdriver Monitoring for all Projects, and export to BigQuery.
C. Configure Stackdriver Monitoring for all Projects with the default retention policies.
D. Configure Stackdriver Monitoring for all Projects, and export to Google Cloud Storage.
Answer: B
https://cloud.google.com/monitoring/api/v3/metrics
Explanation:
Stackdriver Logging provides you with the ability to filter, search, and view logs from your cloud and
open source application services. Allows you to define metrics based on log contents that are
incorporated into dashboards and alerts. Enables you to export logs to BigQuery, Google Cloud Storage,and Pub/Sub.
References: https://cloud.google.com/stackdriver/
Related links:
https://www.dumpspass4sure.com/google/professional-cloud-architect-dumps.html
https://www.dumpspass4sure.com/google-cloud-cerified-test.html
https://cloud.google.com/certification/cloud-architect
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.