[Aug-2026] Professional-Cloud-DevOps-Engineer Dumps PDF - Professional-Cloud-DevOps-Engineer Real Exam Questions Answers
Professional-Cloud-DevOps-Engineer Dumps 100% Pass Guarantee With Latest Demo
Google Professional-Cloud-DevOps-Engineer certification is a highly esteemed certification program for professionals seeking to validate their expertise in cloud-based DevOps engineering. It is designed to test the knowledge and skills required to deploy, manage, and monitor secure, scalable, and highly available cloud-based infrastructure and applications.
The Professional-Cloud-DevOps-Engineer exam covers various topics, including cloud architecture and infrastructure, continuous delivery and release management, site reliability engineering, security, compliance, and troubleshooting. Candidates who pass the exam demonstrate their ability to design, implement, and manage scalable and secure solutions using Google Cloud technologies. Google Cloud Certified - Professional Cloud DevOps Engineer Exam certification is suitable for professionals who work in DevOps roles, cloud architects, and those who are responsible for developing and maintaining cloud-based applications and services.
NEW QUESTION # 98
You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?
- A. Reroute the user traffic from the affected region to other regions that don't report issues.
- B. Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
- C. Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.
- D. Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
Answer: A
Explanation:
Google always aims to first stop the impact of an incident, and then find the root cause (unless the root cause just happens to be identified early on).
NEW QUESTION # 99
You are designing a new Google Cloud organization for a client. Your client is concerned with the risks associated with long-lived credentials created in Google Cloud. You need to design a solution to completely eliminate the risks associated with the use of JSON service account keys while minimizing operational overhead. What should you do?
- A. Grant the roles/ iam.serviceAccountKeyAdmin IAM role to organization administrators only.
- B. Use custom versions of predefined roles to exclude all iam.serviceAccountKeys. * service account role permissions.
- C. Apply the constraints/iam. disableServiceAccountKeyUp10ad constraint to the organization.
- D. Apply the constraints/iam.disableserviceAccountKeycreation constraint to the organization.
Answer: D
NEW QUESTION # 100
You are managing the production deployment to a set of Google Kubernetes Engine (GKE) clusters. You want to make sure only images which are successfully built by your trusted CI/CD pipeline are deployed to production. What should you do?
- A. Enable Vulnerability Analysis on the Container Registry.
- B. Set up the Kubernetes Engine clusters with Binary Authorization.
- C. Set up the Kubernetes Engine clusters as private clusters.
- D. Enable Cloud Security Scanner on the clusters.
Answer: B
Explanation:
Explanation
https://cloud.google.com/binary-authorization/docs/overview
NEW QUESTION # 101
You are running a web application that connects to an AlloyDB cluster by using a private IP address in your default VPC. You need to run a database schema migration in your CI/CD pipeline by using Cloud Build before deploying a new version of your application. You want to follow Google-recommended security practices. What should you do?
- A. Add the database username and password to Secret Manager. When running the schema migration script, retrieve the username and password from Secret Manager.
- B. Set up a Cloud Build private pool to access the database through a static external IP address. Configure the database to only allow connections from this IP address. Execute the schema migration script in the private pool.
- C. Add the database username and encrypted password to the application configuration file. Use these credentials in Cloud Build to execute the schema migration script.
- D. Create a service account that has permission to access the database. Configure Cloud Build to use this service account and execute the schema migration script in a private pool.
Answer: D
Explanation:
To securely connect Cloud Build to an AlloyDB cluster using a private IP address and adhere to Google- recommended security practices, you need to address two main aspects:
Network Connectivity:Ensuring Cloud Build can reach the private IP of the AlloyDB cluster.
Authentication/Credential Management:Securely authenticating Cloud Build to the AlloyDB cluster.
Let's break down why Option B is the most suitable:
Cloud Build Private Pool:AlloyDB is accessed via a private IP in your VPC. Cloud Build's default build environment runs on Google-managed infrastructure outside your VPC and cannot directly access private IP addresses. To enable this, you must use aCloud Build private pool. A private pool can be configured with VPC peering to your default VPC, allowing build steps running within that pool to access resources like your AlloyDB cluster via their private IPs. Option B correctly includes "execute the schema migration script in a private pool." Service Account with Permissions (IAM Database Authentication):AlloyDB supports IAM database authentication. This is a Google-recommended security practice because it allows you to manage database access using Google Cloud's Identity and Access Management (IAM) rather than relying on traditional database passwords.
You would create a dedicated service account for Cloud Build (or use the private pool's service account).
This service account would be granted the necessary IAM roles to connect to the AlloyDB instance (e.g., roles
/alloydb.client) and a database-level IAM role for login (e.g., roles/alloydb.user or roles/alloydb.admin depending on the permissions needed for schema migration).
Cloud Build would then be configured to use this service account. The "permission to access the database" in Option B refers to these IAM permissions. This method avoids managing and distributing database passwords.
Analyzing the options:
A: Set up a Cloud Build private pool to access the database through a static external IP address...
While using a private pool is correct for network access, routing this through a staticexternalIP for a resource that has aprivateIP is generally not the first-choice secure pattern if direct private access is feasible. It adds complexity and a potential external exposure point, even if firewalled. The aim is to keep traffic within the private network as much as possible.
B: Create a service account that has permission to access the database. Configure Cloud Build to use this service account and execute the schema migration script in a private pool.
This option correctly combines the use of aprivate pool(for private IP network access) with aservice account having permissions(strongly implying IAM database authentication for AlloyDB, which is a best practice).
This is a secure and robust approach.
C: Add the database username and encrypted password to the application configuration file...
Storing credentials, even if "encrypted" (the method and key management for encryption are unspecified and problematic), in application configuration files checked into source control or packaged with the application is a significant security risk and not a recommended practice.
D: Add the database username and password to Secret Manager. When running the schema migration script, retrieve the username and password from Secret Manager.
UsingSecret Managerto store database usernames and passwords is a Google-recommended practiceifyou are using password-based authentication. However, this optionalonedoes not solve the network connectivity issue for Cloud Build to reach the private IP of AlloyDB. You would still need a private pool. While D is good for secret management, B offers a more comprehensive solution that includes both the network aspect and implies a more modern authentication method (IAM database auth). If the question forced a choice between only doing secure credential storage (D) or doing IAM auth + private networking (B), B is more complete for the overall task.
Conclusion:Option B is the most aligned with Google-recommended security practices as it addresses both the necessary private network connectivity via a Cloud Build private pool and promotes the use of IAM-based database authentication for AlloyDB, which is generally preferred over managing passwords.
References (General Concepts):
Cloud Build Private Pools for VPC Access:Google Cloud documentation for Cloud Build explicitly details using private pools to connect to resources in a VPC network.
See:https://www.google.com/search?q=https://cloud.google.com/build/docs/private-pools/accessing-private- resources-with-private-pools AlloyDB IAM Database Authentication:Google Cloud documentation for AlloyDB highlights IAM database authentication as a secure method.
See:https://www.google.com/search?q=https://cloud.google.com/alloydb/docs/iam-authentication Secret Manager:If password authentication were the only option, Secret Manager would be the recommended way to store those credentials.
See:https://cloud.google.com/secret-manager
Option B synergizes the benefits of private networking and modern IAM-based authentication for a comprehensive secure solution.
NEW QUESTION # 102
You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?
- A. Reroute the user traffic from the affected region to other regions that don't report issues.
- B. Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
- C. Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.
- D. Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
Answer: A
NEW QUESTION # 103
You are deploying a Cloud Build job that deploys Terraform code when a Git branch is updated. While testing, you noticed that the job fails. You see the following error in the build logs:
Initializing the backend. ..
Error: Failed to get existing workspaces : querying Cloud Storage failed: googleapi : Error
403
You need to resolve the issue by following Google-recommended practices. What should you do?
- A. Grant the roles/ owner Identity and Access Management (IAM) role to the Cloud Build service account on the project.
- B. Grant the roles/ storage. objectAdmin Identity and Access Management (IAM) role to the Cloud Build service account on the state file bucket.
- C. Create a storage bucket with the name specified in the Terraform configuration.
- D. Change the Terraform code to use local state.
Answer: B
Explanation:
Explanation
The correct answer is D. Grant the roles/storage.objectAdmin Identity and Access Management (IAM) role to the Cloud Build service account on the state file bucket.
According to the Google Cloud documentation, Cloud Build is a service that executes your builds on Google Cloud Platform infrastructure1. Cloud Build uses a service account to execute your build steps and access resources, such as Cloud Storage buckets2. Terraform is an open-source tool that allows you to define and provision infrastructure as code3. Terraform uses a state file to store and track the state of your infrastructure4.
You can configure Terraform to use a Cloud Storage bucket as a backend to store and share the state file across multiple users or environments5.
The error message indicates that Cloud Build failed to access the Cloud Storage bucket that contains the Terraform state file. This is likely because the Cloud Build service account does not have the necessary permissions to read and write objects in the bucket. To resolve this issue, you need to grant the roles/storage.objectAdmin IAM role to the Cloud Build service account on the state file bucket. This role allows the service account to create, delete, and manage objects in the bucket6. You can use the gcloud command-line tool or the Google Cloud Console to grant this role.
The other options are incorrect because they do not follow Google-recommended practices. Option A is incorrect because it changes the Terraform code to use local state, which is not recommended for production or collaborative environments, as it can cause conflicts, data loss, or inconsistency. Option B is incorrect because it creates a new storage bucket with the name specified in the Terraform configuration, but it does not grant any permissions to the Cloud Build service account on the new bucket. Option C is incorrect because it grants the roles/owner IAM role to the Cloud Build service account on the project, which is too broad and violates the principle of least privilege. The roles/owner role grants full access to all resources in the project, which can pose a security risk if misused or compromised.
NEW QUESTION # 104
Your company runs services by using multiple globally distributed Google Kubernetes Engine (GKE) clusters Your operations team has set up workload monitoring that uses Prometheus-based tooling for metrics alerts:
and generating dashboards This setup does not provide a method to view metrics globally across all clusters You need to implement a scalable solution to support global Prometheus querying and minimize management overhead What should you do?
- A. Configure workload metrics within Cloud Operations for GKE
- B. Configure Prometheus hierarchical federation for centralized data access
- C. Configure Google Cloud Managed Service for Prometheus
- D. Configure Prometheus cross-service federation for centralized data access
Answer: C
Explanation:
The best option for implementing a scalable solution to support global Prometheus querying and minimize management overhead is to use Google Cloud Managed Service for Prometheus. Google Cloud Managed Service for Prometheus is a fully managed service that allows you to collect, query, and visualize metrics from your GKE clusters using Prometheus-based tooling. You can use Google Cloud Managed Service for Prometheus to query metrics across multiple clusters and regions using a global view. You can also use Google Cloud Managed Service for Prometheus to integrate with other Google Cloud services, such as Cloud Monitoring, Cloud Logging, and BigQuery. By using Google Cloud ManagedService for Prometheus, you can avoid managing and scaling your own Prometheus servers and focus on your application performance.
NEW QUESTION # 105
You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve dat a. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?
- A. Determine whether there is an increased number of connections to the Cloud SQL instance.
- B. Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.
- C. Check the serial port logs of the Compute Engine instance.
- D. Use Stackdriver Profiler to visualize the resources utilization throughout the application.
Answer: A
Explanation:
The most probable cause of the database timeout is an increased number of connections to the Cloud SQL instance. This could happen if the application does not close connections properly or if it creates too many connections at once. You can check the number of connections to the Cloud SQL instance using Cloud Monitoring or Cloud SQL Admin API .
NEW QUESTION # 106
You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?
- A. SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd
- B. Verify the VM service account access scope includes the monitoring.write scope.
- C. Install the most recent version of the Stackdriver agent.
- D. Look for the agent's test log entry in the Logs Viewer.
Answer: A
NEW QUESTION # 107
You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?
- A. Monitor results of Stackdriver Trace to determine the required amount of resources.
- B. Use the n1-highcpu-96 machine type in the configuration of the MIG.
- C. Validate that the resource requirements are within the available quota limits of each region.
- D. Deploy the service in one region and use a global load balancer to route traffic to this region.
Answer: C
Explanation:
Explanation
https://cloud.google.com/compute/quotas#understanding_quotas
https://cloud.google.com/compute/quotas
NEW QUESTION # 108
You are creating and assigning action items in a postmodern for an outage. The outage is over, but you need to address the root causes. You want to ensure that your team handles the action items quickly and efficiently.
How should you assign owners and collaborators to action items?
- A. Assign the team lead as the owner for all action items because they are in charge of the SRE team.
- B. Assign collaborators but no individual owners to the items to keep the postmortem blameless.
- C. Assign one owner for each action item and any necessary collaborators.
- D. Assign multiple owners for each item to guarantee that the team addresses items quickly
Answer: C
Explanation:
Explanation
https://devops.com/when-it-disaster-strikes-part-3-conducting-a-blameless-post-mortem/
NEW QUESTION # 109
You support a user-facing web application When analyzing the application's error budget over the previous six months you notice that the application never consumed more than 5% of its error budget You hold a SLO review with business stakeholders and confirm that the SLO is set appropriately You want your application's reliability to more closely reflect its SLO What steps can you take to further that goal while balancing velocity, reliability, and business needs?
Choose 2 answers
- A. Add more serving capacity to all of your application's zones
- B. Announce planned downtime to consume more error budget and ensure that users are not depending on a tighter SLO
- C. Tighten the SLO to match the application's observed reliability
- D. Have more frequent or potentially risky application releases
- E. Implement and measure all other available SLIs for the application
Answer: C,D
NEW QUESTION # 110
You recently noticed that one Of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Site Reliability Engineering (SRE) practices.
What should you do?
- A. Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.
- B. Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.
- C. Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.
- D. Escalate the situation and request additional error budget.
Answer: B
NEW QUESTION # 111
You use Spinnaker to deploy your application and have created a canary deployment stage in the pipeline.
Your application has an in-memory cache that loads objects at start time. You want to automate the comparison of the canary version against the production version. How should you configure the canary analysis?
- A. Compare the canary with the existing deployment of the current production version.
- B. Compare the canary with a new deployment of the current production version.
- C. Compare the canary with a new deployment of the previous production version.
- D. Compare the canary with the average performance of a sliding window of previous production versions.
Answer: B
Explanation:
https://cloud.google.com/architecture/automated-canary-analysis-kubernetes-engine-spinnaker
https://spinnaker.io/guides/user/canary/best-practices/#compare-canary-against-baseline-not-against- production
NEW QUESTION # 112
You are the Site Reliability Engineer responsible for managing your company's data services and products.
You regularly navigate operational challenges, such as unpredictable data volume and high cost, with your company's data ingestion processes. You recently learned that a new data ingestion product will be developed in Google Cloud. You need to collaborate with the product development team to provide operational input on the new product. What should you do?
- A. When the new product is used by at least one internal customer in production, share error logs and monitoring metrics with the product development team.
- B. Deploy the prototype product in a test environment, run a load test, and share the results with the product development team.
- C. Review the design of the product with the product development team to provide feedback early in the design phase.
- D. When the initial product version passes the quality assurance phase and compliance assessments, deploy the product to a staging environment. Share error logs and performancemetrics with the product development team.
Answer: C
Explanation:
The correct answer is D. Review the design of the product with the product development team to provide feedback early in the design phase.
According to the Google Cloud DevOps best practices, a Site Reliability Engineer (SRE) should collaborate with the product development team from the beginning of the product lifecycle, not just after the product is deployed or tested. This way, the SRE can provide operational input on the product design, such as scalability, reliability, security, and cost efficiency. The SRE can also help define service level objectives (SLOs) and service level indicators (SLIs) for the product, as well as monitoring and alerting strategies. By collaborating early and often, the SRE and the product development team can ensure that the product meets the operational requirements and expectations of the customers.
Reference:
Preparing for Google Cloud Certification: Cloud DevOps Engineer Professional Certificate, Course 1: Site Reliability Engineering and DevOps, Week 1: Introduction to SRE and DevOps.
NEW QUESTION # 113
You support a user-facing web application When analyzing the application's error budget over the previous six months you notice that the application never consumed more than 5% of its error budget You hold a SLO review with business stakeholders and confirm that the SLO is set appropriately You want your application's reliability to more closely reflect its SLO What steps can you take to further that goal while balancing velocity, reliability, and business needs?
Choose 2 answers
- A. Add more serving capacity to all of your application's zones
- B. Announce planned downtime to consume more error budget and ensure that users are not depending on a tighter SLO
- C. Tighten the SLO to match the application's observed reliability
- D. Have more frequent or potentially risky application releases
- E. Implement and measure all other available SLIs for the application
Answer: C,D
Explanation:
The best options for furthering your application's reliability goal while balancing velocity, reliability, and business needs are to have more frequent or potentially risky application releases and to tighten the SLO to match the application's observed reliability. Having more frequent or potentially risky application releases can help you increase the change velocity and deliver new features faster. However, this also increases the likelihood of consuming more error budget and reducing the reliability of your service. Therefore, you should monitor your error budget consumption and adjust your release policies accordingly. For example, you can freeze or slow down releases when the error budget is low, or accelerate releases when the error budget is high. Tightening the SLO to match the application's observed reliability can help you align your service quality with your users' expectations and business needs. However, this also means that you have less room for error and need to maintain a higher level of reliability. Therefore, you should ensure that your SLO is realistic and achievable, and that you have sufficient engineering resources and processes to meet it.
NEW QUESTION # 114
You are designing a system with three different environments: development, quality assurance (QA), and production. Each environment will be deployed with Terraform and has a Google Kubernetes Engine Enterprise (GKE Enterprise) cluster created so that application teams can deploy their applications. Config Sync will be used and templated to deploy infrastructure-level resources in each GKE Enterprise cluster. All users (for example, infrastructure operators and application owners) will use GitOps. How should you structure your source control repositories for both infrastructure as code (IaC) and application code?
- A. Cloud Infrastructure (Terraform) repository is shared: different directories are different environmentsGKE Enterprise Infrastructure (Config Sync Kustomize manifests) repository is shared: different overlay directories are different environmentsApplication (app source code) repositories are separated: different branches are different features
- B. Cloud Infrastructure (Terraform) repository is shared: different branches are different environmentsGKE Enterprise Infrastructure (Config Sync Kustomize manifests) repository is shared: different overlay directories are different environmentsApplication (app source code) repository is shared: different directories are different features
- C. Cloud Infrastructure (Terraform) repositories are separated: different branches are different environmentsGKE Enterprise Infrastructure (Config Sync Kustomize manifests) repositories are separated: different overlay directories are different environmentsApplication (app source code) repositories are separated: different branches are different features
- D. Cloud Infrastructure (Terraform) repository is shared: different directories are different environmentsGKE Enterprise Infrastructure (Config Sync Kustomize manifests) repositories are separated: different branches are different environmentsApplication (app source code) repositories are separated: different branches are different features
Answer: A
NEW QUESTION # 115
You are developing the deployment and testing strategies for your CI/CD pipeline in Google Cloud You must be able to
* Reduce the complexity of release deployments and minimize the duration of deployment rollbacks
* Test real production traffic with a gradual increase in the number of affected users You want to select a deployment and testing strategy that meets your requirements What should you do?
- A. Recreate deployment and canary testing
- B. Blue/green deployment and canary testing
- C. Rolling update deployment and shadow testing
- D. Rolling update deployment and A/B testing
Answer: B
NEW QUESTION # 116
You recently noticed that one Of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Site Reliability Engineering (SRE) practices.
What should you do?
- A. Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.
- B. Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget.
- C. Escalate the situation and request additional error budget.
- D. Look through other metrics related to the product and find SLOs with remaining error budget.
Reallocate the error budgets and allow the feature launch.
Answer: A
Explanation:
The correct answer is A. Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.
According to the Site Reliability Engineering (SRE) practices, an error budget is the amount of unreliability that a service can tolerate without harming user satisfaction1.An error budget is derived from the service-level objectives (SLOs), which are the measurable goals for the service quality2. When a service exceeds its error budget, it means that it has violated its SLOs and may have negatively impacted the users.In this case, the SRE team should notify the product team that their error budget is used up and negotiate with them for a launch freeze or a lower SLO3. A launch freeze means that no new features are deployed until the service reliability is restored. A lower SLO means that the product team accepts a slightly worse user experience in exchange for launching new features. Both options require a trade-off between reliability and innovation, and should be agreed upon by both teams.
The other options are incorrect because they do not follow the SRE practices.Option B is incorrect because it violates the principle of error budget autonomy, which means that each service should have its own error budget and SLOs, and should not borrow or reallocate them from other services4. Option C is incorrect because it does not address the root cause of the error budget overspend, and may create unrealistic expectations for the service reliability. Option D is incorrect because it does not prevent the possibility of introducing new errors or bugs with the feature launch, which may further degrade the service quality and user satisfaction.
NEW QUESTION # 117
You currently store the virtual machine (VM) utilization logs in Stackdriver. You need to provide an easy-to-share interactive VM utilization dashboard that is updated in real time and contains information aggregated on a quarterly basis. You want to use Google Cloud Platform solutions. What should you do?
- A. 1. Export VM utilization logs from Stackdriver to BigOuery.
2. Create a dashboard in Data Studio.
3. Share the dashboard with your stakeholders. - B. 1. Export VM utilization logs from Stackdriver to a Cloud Storage bucket.
2. Enable the Cloud Storage API to pull the logs programmatically.
3. Build a custom data visualization application.
4. Display the pulled logs in a custom dashboard. - C. 1. Export VM utilization logs (rom Stackdriver to BigQuery.
2. From BigQuery. export the logs to a CSV file.
3. Import the CSV file into Google Sheets.
4. Build a dashboard in Google Sheets and share it with your stakeholders. - D. 1. Export VM utilization logs from Stackdriver to Cloud Pub/Sub.
2. From Cloud Pub/Sub, send the logs to a Security Information and Event Management (SIEM) system.
3. Build the dashboards in the SIEM system and share with your stakeholders.
Answer: C
NEW QUESTION # 118
......
Dumps Real Google Professional-Cloud-DevOps-Engineer Exam Questions [Updated 2026]: https://www.ipassleader.com/Google/Professional-Cloud-DevOps-Engineer-practice-exam-dumps.html
Prepare Professional-Cloud-DevOps-Engineer Question Answers Free Update With 100% Exam Passing Guarantee [2026]: https://drive.google.com/open?id=1gTyyNSHz8RB81w3k_ys8YRJ988pktE9H