Cloud Engineer: Google Associate Flashcards

You need to move a group of media files totaling more than 50 GB each to Google Cloud Storage. The documents are located in your on-site data center. What kind of relocation strategy might you employ to hasten the transfer process?

Answer: Use parallel uploads to break the file into smaller chunks then transfer it simultaneously

For very large files like 50 GB media files, using parallel uploads significantly speeds up the transfer process to Google Cloud Storage. This strategy breaks the large file into smaller chunks, which are then uploaded simultaneously. By leveraging multiple connections and concurrent transfers, it maximizes available bandwidth and drastically reduces the overall time required compared to a single, sequential upload.

Your team uses Splunk for centralized logging, and Splunk logs are the basis for many of your reports and dashboards. Splunk Forwarder must be installed on each node of your new Kubernetes Engine autoscaled cluster. The logs are forwarded to a central Splunk server by the Splunk forwarder. You want to reduce administrative costs. What is the most effective strategy to install Splunk Forwarder throughout the cluster's nodes?

Answer: Include the forwarder agent in a DaemonSet deployment

A DaemonSet in Kubernetes is designed to ensure that a copy of a pod runs on every node in a cluster. This is the most effective strategy for deploying a logging agent like Splunk Forwarder across all nodes in an autoscaled Kubernetes Engine cluster. It automatically handles the installation on new nodes as they scale up, reducing administrative overhead and ensuring consistent logging coverage without manual intervention.

Your team strives to deploy your application to the GKE cluster in the desired state configuration. YAML files represent the Kubernetes deployment and service objects. The replicas parameter in app deployment.yaml specifies that your application is intended to run on two pods. The GKE load balancer is described in the app service. Your service uses YAML. You created the Kubernetes resources by running kubectl apply -f app-deployment.yaml kubectl apply -f app-service.yaml Although your deployment is now handling live traffic, it has performance problems. You would like to make five more replicas. What should you do to update the replicas in the deployed Kubernetes objects currently in use?

Answer: Edit the number of replicas in the YAML file and rerun the kubectl apply. kubectl apply -f app-deployment.yaml

The `kubectl apply -f` command is declarative, meaning it applies the desired state defined in the YAML file to your Kubernetes cluster. To update the number of replicas, you should modify the `replicas` parameter directly in your `app-deployment.yaml` file. Rerunning `kubectl apply -f app-deployment.yaml` will then reconcile the cluster's state with the updated YAML, ensuring your infrastructure-as-code remains the single source of truth for your deployment configuration.

Every year, auditors visit your teams and request a review of all the prior year's Google Cloud Identity and Access Management (Cloud IAM) policy updates. The analysis and auditing processes have to be streamlined and accelerated. What ought you to do?

Answer: Enable Logging export to Google BigQuery and use ACLs and views to scope the data shared with the auditor

Exporting Cloud IAM audit logs to Google BigQuery provides a centralized, highly scalable, and queryable repository for historical data. BigQuery's powerful SQL capabilities allow auditors to easily analyze and filter specific IAM policy updates. Furthermore, BigQuery's Access Control Lists (ACLs) and views enable precise control over which data subsets are shared with auditors, streamlining the review process while maintaining data security and compliance.

A business plans to move its online application to Google App Engine. They would nonetheless keep using their on-site database. How do they configure the application?

Answer: Setup the application using App Engine Flexible environment with Cloud VPN to connect to database

The App Engine Flexible environment allows applications to run in custom runtimes within a Google Cloud Virtual Private Cloud (VPC), providing more network configuration options than the Standard environment. To connect to an on-site database securely, a Cloud VPN tunnel can be established between the Google Cloud VPC and the on-site data center. This setup enables the App Engine Flexible application to access the private on-site database over a secure, private connection.

The corporate apps of your client are being moved to the Google Cloud Platform. The security team requests complete visibility into every project within the company. You create your account as the organization administrator and provide the Google Cloud Resource Manager. Which Cloud IAM (Google Cloud Identity and Access Management) roles ought the security team be assigned?

Answer: Org viewer, project viewer

The security team requires complete visibility into all projects and the organization structure without the ability to make changes. The `Org viewer` role grants read-only access to organization-level resources, while the `Project viewer` role provides read-only access to all resources within projects. Assigning both roles ensures the security team has comprehensive visibility for auditing purposes across the entire GCP organization without granting any modification permissions.

Your virtual machines are operating on a network with the subnet mask 255.255.255.240. There are no more available IP addresses on the present subnet, and you need an additional 10 IP addresses for new virtual machines. All current and recent VMs should be able to connect without needing different routes. What ought you to do?

Answer: Use gcloud to expand the IP range of the current subnet

To add more IP addresses to an existing subnet without disrupting current virtual machines or requiring new routing configurations, the most efficient method is to expand the subnet's IP range. Google Cloud allows you to expand the primary IP range of a subnet using the `gcloud` command-line tool. This operation seamlessly adds more available IP addresses to the subnet while preserving existing configurations and connectivity for all VMs.