Free CLOUD-DIGITAL-LEADER Exam Braindumps (page: 31)

Page 30 of 104

You are a database manager working for a new product that will need millions of reading and writ- ing from the database, with zero downtime, key-value i.e. NoSQL features, no manual steps should be required to ensure consistency, repair data, synchronize writes and deletes, Which of the follow- ing database you choose?

  1. Cloud SQL
  2. Cloud BigTable
  3. Cloud Spanner
  4. Cloud Firestore

Answer(s): B

Explanation:

Cloud BigTable
Key features
High throughput at low latency
Bigtable is ideal for storing very large amounts of data in a key-value store and supports high read and write throughput at low latency for fast access to large amounts of data. Throughput scales linearly--you can increase QPS (queries per second) by adding Bigtable nodes. Bigtable is built with proven infrastructure that powers Google products used by billions such as Search and Maps.
Cluster resizing without downtime
Scale seamlessly from thousands to millions of reads/writes per second. Bigtable throughput can be dynamically adjusted by adding or removing cluster nodes without restarting, meaning you can increase the size of a Bigtable cluster for a few hours to handle a large load, then reduce the cluster's size again--all without any downtime.
Flexible, automated replication to optimize any workload Write data once and automatically replicate where needed with eventual consistency--giving you control for high availability and isolation of reading and write workloads. No manual steps are needed to ensure consistency, repair data, or synchronize writes and deletes. Benefit from a high availability SLA of 99.999% for instances with multi-cluster routing across 3 or more regions (99.9%

for single-cluster instances).



In terms of Cloud SQL for MySQL Features offered by Google Cloud Platform which of the statements is/are correct?

  1. Do not support Private IP (private service access).
  2. Customer data is encrypted on Google's internal networks and in database tables, temporary files, and backups.
  3. Do not Provide automated and on-demand backups and point-in-time recovery.
  4. None of the above

Answer(s): B

Explanation:

Cloud SQL for MySQL:
Features
- Fully managed MySQL Community Edition databases in the cloud.
- Cloud SQL instances support MySQL 8.0, 5.7 (default), and 5.6, and provide up to 624 GB of RAM and 64 TB of data storage, with the option to automatically increase the storage size, as needed.
- Create and manage instances in the Google Cloud Console.
- Instances are available in the Americas, EU, Asia, and Australia.
- Customer data is encrypted on Google's internal networks and in database tables, temporary files, and backups.
- Support for secure external connections with the Cloud SQL Auth proxy or with the SSL/TLS protocol.
- Support for private IP (private services access).
- Data replication between multiple zones with automatic failover.
- Import and export databases using mysqldump, or import and export CSV files.
- Support for MySQL wire protocol and standard MySQL connectors.
- Automated and on-demand backups and point-in-time recovery.
- Instance cloning.
- Integration with Google Cloud's operations suite logging and monitoring.



What issues can arise when organizations integrate third-party systems into their cloud infrastruc- ture?

  1. Third-party systems may not be powerful enough to run many critical business applications.
  2. Without sufficient security measures and regular checks, unsecured third-party systems can pose a threat to data security.
  3. Over-reliance on third-party systems limits an organization's potential for innova-tion.
  4. Third-party systems are less capable of addressing an organization's security re-quirements.

Answer(s): B

Explanation:

Because unsecured third-party systems are a cybersecurity threat.



A customer of yours has an SLA with their client that a particular service will respond within 4 sec-

onds. The end client has reported that it feels slower. Your engineers do a trial at the client site and notice that there seems to be a delay for many of the requests. It's your team's responsibility to iden- tify the issue quickly within the strict timeline for fixes according to the contract, and then fix it.
What should you do?

  1. Recommend a move to serverless technologies which will scale automatically on demand.
  2. Add logging statements at multiple points in the application, build it, and deploy it. Now new requests will give us information on latency in the logs.
  3. Check if the browsers used by the client are different from yours. If they are, that's most likely the issue. Ensure that everybody uses the latest version of the browser that you are also using.
  4. Use Cloud Trace to collect latency data and track how requests propagate and why there is a delay.

Answer(s): D

Explanation:

Cloud Trace is a built-in tool in the Operations suite to identify issues like latency. -> Such fixes are unlikely to change core issues like the service itself being architected or written sub- optimally. Though changes like browser, networking, etc. are helpful, it would be the wrong approach to first recommend that the customer upgrade all their hardware and software. -> Rewriting code and logging information is going to be time consuming. In general though, logging should always be included in code and it can give good insights. But tracing is way more specific and comprehensive for this requirement.
-> In certain cases, we might identify scaling as the issue. But we should first identify the core problem. So, start with tracing. We can also achieve scale in server-ful technologies.

Reference link- https://cloud.google.com/trace






Post your Comments and Discuss Google CLOUD-DIGITAL-LEADER exam with other Community members:

CLOUD-DIGITAL-LEADER Discussions & Posts