1. Why would a developer choose to store source code in Cloud Source Repositories? (Select 2)
- To reduce work
- To have total control over the hosting infrastructure
- To keep code private to a Google Cloud project
- It is the only way to access your source code in a repository.
2. Why might a Google Cloud customer choose to use Cloud Functions?
- Cloud Functions is the primary way to run Node.js applications in Google Cloud.
- Their application has a legacy monolithic structure that they want to separate into microservices.
- Cloud Functions is a free service for hosting compute operations.
- Their application contains event-driven code that they don’t want to provision compute resources for.
3. Select the advantage of putting the event-driven components of your application into Cloud Functions.
- Cloud Functions handles scaling these components seamlessly.
- In Cloud Functions, processing is always free of charge.
- In Cloud Functions, code can be written in C# or C++.
- Cloud Functions eliminates the need to use a separate service to trigger application events.
Explanation: There is a multitude of advantages that come along with storing source code in Cloud Source Repositories (CSR). In the first place, it offers a centralized location that is simple to reach for your codebase. When it comes to collaborative projects, this has the potential to be a game-changer since it enables numerous developers to work fluidly together. Additionally, CSR connects with other Google Cloud services, which makes the experience more seamless if you are currently using services from their ecosystem.
An additional advantage is safety. Version control is provided by CSR, which enables you to keep a clear history of your codebase, monitor changes, and rollback to prior versions if necessary by allowing you to do so. Additionally, it offers fine-grained access control, which assists you in managing who may modify your code and in what ways.
Regarding customer service, automation is the name of the game. It simplifies the process of building, testing, and deploying your apps by providing support for continuous integration and delivery technology. In addition, it has a number of useful capabilities, such as code search, which makes it an efficient toolkit intended for developers.
4. Why might a Google Cloud customer choose to use Terraform?
- Terraform can be used as an infrastructure management system for Google Cloud resources.
- Terraform can be used as a version-control system for your Google Cloud infrastructure layout.
- Terraform can be used to enforce maximum resource utilization and spending limits on your Google Cloud resources.
- Terraform can be used as an infrastructure management system for Kubernetes pods.
Explanation: When it comes to managing infrastructure on Google Cloud, Terraform is a choice that comes with a number of convincing reasons. Terraform is a strong and versatile infrastructure as code (IaC) tool, which is one of the most significant advantages of their product. By enabling you to create and provide infrastructure via the use of a declarative configuration language, it simplifies the process of managing and controlling the version of your respective infrastructure code.
The vast array of services offered by Google Cloud may at times be prohibitively difficult to manage manually. Through the provision of a single workflow for the deployment and management of resources, Terraform contributes to the streamlining of this process. Because Terraform allows you to develop, alter, and version your infrastructure in a manner that is consistent and repeatable, you may use it.
The capacity to work together effectively is yet another significant advantage. Additionally, Terraform configurations may be versioned and shared in the same manner as any other code, which makes it easier for members of a team to work together. This contributes to the maintenance of consistency across all settings, including product development, testing, and production.
Once again, automation is the key operative term. Terraform's scripting features allow it to enable automation, which makes it simple to connect with continuous integration and continuous delivery pipelines. In this approach, you will be able to guarantee that the modifications you make to your infrastructure are tested and implemented in a controlled manner.
5. There are “Four Golden Signals” that measure a system’s performance and reliability. What are they?
- Availability, durability, scalability, resiliency
- Latency, traffic, saturation, errors
- Get, post, put, delete
- KPIs, SLIs, SLOs, SLAs
6. Which definition best describes a service level indicator (SLI)?
- A key performance indicator; for example, clicks per session or customer signups
- A percentage goal of a measure you intend your service to achieve
- A contract with your customers regarding service performance
- A time-bound measurable attribute of a service
Explanation: A quantitative indicator that describes a particular component of the performance or dependability of a service is referred to as a Service Level Indicator, or SLI for short. It is an expression that is often represented as a percentage or ratio, and it expresses the features of a service that can be measured. Serving as a component of a more comprehensive framework for the management of service level objectives (SLOs) and service level agreements (SLAs), service level indicators (SLIs) are used to conduct an objective evaluation of the degree to which a service is reaching its aims.
Putting it another way, service level indicators (SLIs) are the metrics or criteria that you choose in order to evaluate the performance or dependability of a service. Some examples of service-level indicators (SLIs) are the latency (response time) of a service, error rates, and availability respectively. When it comes to evaluating and monitoring the performance of a service, they provide a method that is both clear and quantitative.
7. Which option describes a commitment made to your customers that your systems and applications will have only a certain amount of “downtime”?
- Service level agreement
- Service level indicator
- Key performance indicator
- Service level objective
Explanation: A Service Level Agreement (SLA) is the kind of agreement that is commonly used to refer to this promise. An SLA, or service level agreement, is a legal agreement that specifies the level of service that a client might anticipate receiving from a service provider. Quite frequently, it contains particular guarantees for uptime, performance, and several other measures of importance. In a service level agreement (SLA), the downtime commitment outlines the maximum amount of time that a system or service is permitted to be offline or to be experiencing problems within a specifically specified time frame. Accomplishing these pledges is absolutely necessary in order to preserve the confidence and happiness of the consumer.
8. You want to create alerts on your Google Cloud resources, such as when health checks fail. Which is the best Google Cloud product to use?
- Cloud Trace
- Cloud Monitoring
- Cloud Functions
- Cloud Debugger
Explanation: It is common practice to make use of Google Cloud Monitoring in order to generate alerts on Google Cloud resources, including problems encountered during health checks. Google Cloud Monitoring is a sophisticated tool that gives you the ability to gather data associated with your Google Cloud Platform (GCP) resources, examine those metrics, and get alerts about them.
You have the ability to establish alerting rules inside Google Cloud Monitoring that are based on certain criteria. One example would be the creation of an alert policy that is activated in the event that a health check is unsuccessful. In the event that there are problems with the state of your resources, you will be contacted as soon as possible under this arrangement.
Additionally, you can use Google Cloud Logging to gather and analyze logs, and you can link it with Cloud Monitoring for a full monitoring and alerting solution.
9. Select the two correct statements about Cloud Logging.
- Cloud Logging lets you define uptime checks.
- Cloud Logging lets you view logs from your applications and filter and search on them.
- Cloud Logging requires the use of a third-party monitoring agent.
- Cloud Logging requires you to store your logs in BigQuery or Cloud Storage.
- Cloud Logging lets you define metrics based on your logs.
10. Which of the following does not allow you to interact with Google Cloud?
- Google Cloud Console
- REST-based API
- Cloud Explorer
- Cloud Shell
11. What is the difference between the Google Cloud Console and Cloud Shell?
- Cloud Shell is a command-line tool, while the Cloud Console is a graphical user interface
- The Cloud Console is a command-line tool, while Cloud Shell is a graphical user interface
- Cloud Shell is a locally installed tool, while the Cloud Console is a temporary virtual machine.
- There is no difference as these tools are 100% identical.
12. In Google Cloud, what is the minimum number of IP addresses that a VM instance needs?
- One: Only an internal IP address
- Two: One internal and one external IP address
- Three: One internal, one external and one alias IP address
Explanation: Within the Google Cloud Virtual Private Cloud (VPC) network, a virtual machine (VM) instance normally requires at least one internal IP address in order to connect with other instances located within the VPC. Nevertheless, if you want the virtual machine to be accessible via the internet, you might alternatively provide an IP address that is external to the machine.
Therefore, the very minimum is one IP address that is internal; but, if you want access from the outside, you will also need to assign an IP address that is external. Keep in mind that you have the ability to set several IP addresses, both internal and external, depending on the unique needs of your networking environment.
13. What are the three types of networks offered the Google Cloud?
- Zonal, regional, and global
- Gigabit network, 10 gigabit network, and 100 gigabit network
- Default network, auto network, and custom network.
- IPv4 unicast network, IPv4 multicast network, IPv6 network
14. What is one benefit of applying firewall rules by tag rather than by address?
- Tags help organizations track firewall billing.
- Tags in network traffic help with network sniffing.
- Tags on firewall rules control which ephemeral IP addresses VMs will receive.
- When a VM is created with a matching tag, the firewall rules apply irrespective of the IP address it is assigned.
Explanation: When it comes to controlling the security of your network, applying firewall rules based on tags rather than addresses has the potential to give more flexibility and simplicity. When you utilize tags, you have the ability to link one or more tags with the instances or resources of your virtual machine, and then you may apply firewall rules depending on these tags.
Dynamic scalability is one of the crucial advantages. If you have a dynamic environment in which instances are often produced or destroyed, tagging gives you the ability to apply firewall rules to groups of instances based on the attributes of those instances rather than the IP addresses of those instances individually. Because of this, scaling your infrastructure is made much simpler, and you won't have to deal with the hassle of continuously upgrading individual IP addresses in your firewall rules.
Making use of tags also improves the management of the system. Through the use of tags, you are able to classify instances according to their roles, functions, or any other criteria, and then apply firewall rules to the categories that you have created. Especially in big and complicated network setups, this abstraction makes the rule management process more clear and simplifies it, making it much easier to operate.
Therefore, implementing firewall rules by tag offers a more dynamic and manageable method, which enables you to respond to changes in your environment and expedite the administration of your network security policies. In conclusion, this technique is more controllable and dynamic.