Google Google Certifications CLOUD-DIGITAL-LEADER Questions & Answers

• Question 251:

  What according to you are NOT the key capabilities of In-App Messaging?

  A. Target messages accordingly to the change in the behavior pattern of the target audience.

  B. Creating customized and flexible alerts

  C. Increasing conversion for user-to-user sharing

  D. Sending relevant messages to the target audience

  Correct Answer: C

  In-App Messaging

  Engage active app users with contextual messages.

  Firebase In-App Messaging helps you engage users who are actively using your app by sending them targeted and contextual messages that nudge them to complete key in-app actions-like beating a game level, buying an item, or

  subscribing to content.

• Question 252:

  "With cloud messaging you can Customize and deliver messages accordingly to the predetermined time in the user's local time zone." Comment on the above statement.

  A. This statement is undefined.

  B. The above statement is partially true.

  C. The above statement is completely false.

  D. The above statement is completely true.

  Correct Answer: D

  Firebase Cloud Messaging:

  Firebase Cloud Messaging (FCM) is a cross-platform messaging solution that lets you reliably send messages at no cost.

  Using FCM, you can notify a client app that new email or other data is available to sync. You can send notification messages to drive user re-engagement and retention. For use cases such as instant messaging, a message can transfer a payload of up to 4000 bytes to a client app.

  Key capabilities of Firebase Cloud Messaging:

  Send notification messages or data messages: Send notification messages that are displayed to your user. Or send data messages and determine completely what happens in your application code.

  Versatile message targeting: Distribute messages to your client app in any of 3 ways--to single devices, to groups of devices, or to devices subscribed to topics. Send messages from client apps: Send acknowledgments, chats, and other messages from devices back to your server over FCM's reliable and battery-efficient connection channel.

• Question 253:

  A customer is migrating there on-promises data analytics solution to Google Cloud. The current solution has a lot of data being read form and written to disk. The performance of this approach has occasionally been a bottleneck for a scale of operations that your cus-tomer has. The application is fault tolerant and can with stand machine going down fre-quently. In moving to Google Cloud they are asking your advice on any way to improve performance?

  A. Use Big Query Which has very fast data access and analysis

  B. Use Cloud Storage which can be central, scalable storage

  C. Use local SSDs with the VMs

  D. Use Persistent Disk with the VMs

  Correct Answer: C

  Local SSDs are attached to the VM and have very high throughput. However, when the VM shuts down, The local SSD is also shut down, Since our Workload here is foult tolerant, than is not an issue.

• Question 254:

  You are a cloud architect in a software solution provider company, one of the client that is a Na-tional Bank who wants to build an application that deals with transactions processing, and it needs a relational database with petabyte of scale data. Which of the following Google Cloud Services will you use?

  A. Cloud SQL

  B. Cloud Bigtable

  C. Cloud Spanner

  D. Google Cloud BigQuery

  Correct Answer: C

  -Cloud Spanner is the online transaction processing solution that is relational and offers petabyte scalability. Cloud SQL is not designed for petabyte-scale data.

• Question 255:

  Cloud SQL is a fully-managed relational database service for MySQL, PostgreSQL and SQL serv-ers, keeping Cloud SQL Google Cloud Service in mind, which of the following statements is/are correct?

  A. Data inside cloud SQL is automatically Encrypted.

  B. Cloud SQL automatically ensures your databases are reliable, secure, and scala-ble so that your business continues to run without disruption.

  C. With DMS (Database Migration Service) it becomes very easy to Migration of Pro-duction Database.

  D. All of the above

  Correct Answer: D

  Cloud SQL

  Fully managed relational database service for MySQL, PostgreSQL, and SQL Server. Run the exact same relational databases you know with their rich extension collections, configuration flags and developer ecosystem, but without the

  hassle of self management.

  -Reduce maintenance cost with fully managed MySQL, PostgreSQL and SQL Server databases.

  -Ensure business continuity with reliable and secure services backed by 24/7 SRE team.

  -Automate database provisioning, storage capacity management, and other time-consuming tasks.

  -Database observability made easy for developers with Cloud SQL Insights.

  -Easy integration with existing apps and Google Cloud services like GKE and BigQuery.

  Key features:

  Fully managed

  Cloud SQL automatically ensures your databases are reliable, secure, and scalable so that your business continues to run without disruption. Cloud SQL automates all your backups, replication, encryption patches, and capacity increases-

  while ensuring greater than 99.95% availability, anywhere in the world. Integrated Access Cloud SQL instances from just about any application. Easily connect from App Engine, Compute Engine, Google Kubernetes Engine, and your workstation. Open up analytics possibilities by using BigQuery to directly query your Cloud SQL databases. Reliable Easily configure replication and backups to protect your data. Go further by enabling automatic failover to make your database highly available. Your data is automatically encrypted, and Cloud SQL is SSAE 16, ISO 27001, and PCI DSS compliant and supports HIPAA compliance. Easy migrations to Cloud SQL Database Migration Service (DMS) makes it easy to migrate your production databases to Cloud SQL with minimal downtime. This serverless offering eliminates the manual hassle of provisioning, managing, and monitoring migration-specific resources. DMS leverages the native replication capabilities of MySQL and PostgreSQL to maximize the fidelity and reliability of your migration. And it's available at no additional charge for native like-to-like migrations to Cloud SQL.

• Question 256:

  Cloud Data Loss Prevention (DLP) is a fully managed service designed to help discover, classify, and protect the most sensitive data. DLP provides three key features (Select Three Answers)

  A. Classification

  B. De-identification

  C. De-classification

  D. Inspection

  E. Reinspection

  Correct Answer: ABD

  Classification. De-classification and Inspection Classification is the process to inspect the data and know what data we have, how sensitive it is, and the likelihood. Inspection and classification happen here. De-identification is the process of removing, masking, replacing information from data.

  Reference link-https://cloud.google.com/dlp/docs

• Question 257:

  What cloud deployment model is generally deployed between organizations such as non-profits, hospitals or even enterprises that share similar requirements or interests?

  A. Hybrid

  B. Community

  C. Private

  D. Public

  Correct Answer: B

  Community Cloud ?The cloud infrastructure is planned for selective use by a particular community of consumers from organizations that have mutual interests like security needs, policy, and compliance considerations.

  Reference link-https://csrc.nist.gov/glossary/term/community_cloud

• Question 258:

  A customer has an application running in virtual machines. They are migrating this application to Google Cloud. They have previously had scaling issues when on-premises as VMs had to be pre-allocated. Capacity planning was repeatedly off mark-it's either too many VMs or too less. They want to match the capacity to demand while keeping the application running always. They don't have the time or budget to re-architect the systems using containers and Kubernetes at the mo- ment. What would be your recommendation?

  A. Run a load test on Compute Engine VMs. Get an estimate of usage. Then plan for a VM capacity of 25% above the load test value.

  B. Use the Managed Instance Group with Compute Engine

  C. Inform them that new-age companies are using microservices, containers, and Kubernetes for this and they can plan to rewrite the app quickly.

  D. Inform them that using a serverless option will take care of the scaling and they can move to Cloud Run or App Engine.

  Correct Answer: B

  Scalability. When your apps require additional compute resources, autoscaled MIGs can automatically grow the number of instances in the group to meet demand. If demand drops, autoscaled MIGs can automatically shrink to reduce your costs

  https://cloud.google.com/compute/docs/instance-groups

• Question 259:

  Your customer's IT team is in the process of modernizing their customer-facing applications. They've witnessed others getting good results from employing microservices, and they're keen to adopt it themselves. The first application that they are modernizing has about 5 different sub-parts, which they have identified will be the services. They also identify that each of them has different scale requirements-some services like user login are less frequently used while others like transac-tions are heavily used. What technical strategy would you recommend for them?

  A. Containerize the services and orchestrate them with Google Kubernetes Engine.

  B. Retain the original application in Compute Engine and scale it as needed using Managed Instance Groups.

  C. Retain the original application as a backup and also for separately scaling the ser-vices, create new application binaries.

  D. Retain the original application in Compute Engine and scale it as needed using Unmanaged Instance Groups.

  Correct Answer: A

  Containers and Kubernetes are ideal for the kind of requirement mentioned here-separate microservices that need to scale independently. Google Kubernetes Engine (GKE) provides a managed environment for deploying, managing, and scaling your containerized applications using Google infrastructure. The GKE environment consists of multiple machines (specifically, Compute Engine instances) grouped together to form a cluster.

  Reference link-https://cloud.google.com/kubernetes-engine/docs/concepts/kubernetes-engine-overview

• Question 260:

  With respect to the Core Feature of Standby Instances of Cloud SQL which one of the options is correct.?

  A. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance appears in the Google Cloud Console but does not get billed. When failover occurs, connections to the primary instance need to be manually transferred to the standby instance.

  B. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance appears in the Google Cloud Console but does not get billed. When failover occurs, connections to the primary instance are automatically transferred to the standby instance.

  C. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console. When failover occurs, connections to the primary instance are automati-cally transferred to the standby instance.

  D. None of the Above.

  Correct Answer: C

  The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console. When failover occurs, connections to the primary instance are automatically transferred to the standby instance.

  Cloud SQL Key Terms:

  Cloud SQL instance A Cloud SQL instance corresponds to one virtual machine (VM). The VM includes the database instance and accompanying software containers to keep the database instance up and running. Database instance A database instance is the set of software and files that operate the databases: MySQL, PostgreSQL or SQL Server. High availability Cloud SQL instances using high availability (HA) provide greater reliability than non-HA instances. HA in Cloud SQL works by having two synchronized instances: a primary instance and a standby instance. Each instance has exactly one VM. Each instance is in a different zone in the same region. Failover A failover is when Cloud SQL switches serving from the original primary instance to the standby instance. Autofailover is a mechanism that automatically triggers failover when a Cloud SQL instance didn't issue a heartbeat in the previous interval. Standby instances The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console. When failover occurs, connections to the primary instance are automatically transferred to the standby instance. Clone When you clone a Cloud SQL instance, you create a new instance that is a copy of the source instance, but is completely independent. After cloning is complete, changes to the source instance are not reflected in the clone, and changes in the clone are not reflected in the source instance. Replication Replication is the ability to create copies of a Cloud SQL instance or an on-premises database, and offload work to the copies. The main reason for using replication is to scale the use of data in a database without degrading performance on the primary instance. Read replica The read replica is an exact copy of the primary instance. Data and other changes on the primary instance are updated in almost real time on the read replica. Send your write transactions to the primary instance, and your read requests to the read replica. The read replica processes queries, read requests, and analytics traffic, thus reducing the load on the primary instance. Source server Replication copies transactions from a primary instance to one or more read replicas. The primary instance is also called the source server. The source server can be a Cloud SQL primary instance, or a server outside of Google Cloud, such as an on-premises server or a server running in a different cloud. If the source server is outside of Google Cloud, we call it Replication from an external server. Cloud SQL Auth proxy client The Cloud SQL Auth proxy client is open source software maintained by Cloud SQL. It connects to a companion process, the Cloud SQL Auth proxy server, running on your Cloud SQL instance. You run the Cloud SQL Auth proxy client on your own servers. The Cloud SQL Auth proxy client can be used to establish a secure SSL/TLS connection to the database instance, and/or to avoid having to open the firewall. Authentication is done through Identity and Access Management (IAM).