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: 22)

Page 21 of 68
PDF with 278 Questions

One of the developers on your team deployed their application in Google Container Engine with the Dockerfile below. They report that their application deployments are taking too long.



You want to optimize this Dockerfile for faster deployment times without adversely affecting the app's functionality.

Which two actions should you take? Choose 2 answers.

  1. Remove Python after running pip.
  2. Remove dependencies from requirements.txt.
  3. Use a slimmed-down base image like Alpine linux.
  4. Use larger machine types for your Google Container Engine node pools.
  5. Copy the source after the package dependencies (Python and pip) are installed.

Answer(s): C,E

Explanation:

The speed of deployment can be changed by limiting the size of the uploaded app, limiting the complexity of the build necessary in the Dockerfile, if present, and by ensuring a fast and reliable internet connection.

Note: Alpine Linux is built around musl libc and busybox. This makes it smaller and more resource efficient than traditional GNU/Linux distributions. A container requires no more than 8 MB and a minimal installation to disk requires around 130 MB of storage. Not only do you get a fully-fledged Linux environment but a large selection of packages from the repository.


Reference:

https://groups.google.com/forum/#!topic/google-appengine/hZMEkmmObDU https://www.alpinelinux.org/about/



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?

  1. Deploy fewer changes to production.
  2. Deploy smaller changes to production.
  3. Increase the load on your test and staging environments.
  4. Deploy changes to a small subset of users before rolling out to production.

Answer(s): C



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?

  1. Configure a new load balancer for the new version of the API.
  2. Reconfigure old clients to use a new endpoint for the new API.
  3. Have the old API forward traffic to the new API based on the path.
  4. Use separate backend pools for each API path behind the load balancer.

Answer(s): D

Explanation:

https://cloud.google.com/endpoints/docs/openapi/lifecycle-management



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?

  1. Set timeouts on your application so that you can fail requests faster.
  2. Send custom metrics for each of your requests to Stackdriver Monitoring.
  3. Use Stackdriver Monitoring to look for insights that show when your API latencies are high.
  4. Instrument your application with Stackdnver Trace in order to break down the request latencies at each microservice.

Answer(s): D

Explanation:

https://cloud.google.com/trace/docs/overview






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

Google Cloud Architect Professional Discussions & Posts