PCD-4

You made a typo in a low-level Linux configuration file that prevents your Compute Engine instance from booting to a normal run level. You just created the Compute Engine instance today and have done no other maintenance on it, other than tweaking files. How should you correct this error?

• Download the file using scp, change the file, and then upload the modified version

• Configure and log in to the Compute Engine instance through SSH, and change the file

• Configure and log in to the Compute Engine instance through the serial port, and change the file

• Configure and log in to the Compute Engine instance using a remote desktop client, and change the file

You are developing an application that needs to store files belonging to users in Cloud Storage. You want each user to have their own subdirectory in Cloud Storage. When a new user is created, the corresponding empty subdirectory should also be created. What should you do?

• Create an object with the name of the subdirectory ending with a trailing slash ('/') that is zero bytes in length.

• Create an object with the name of the subdirectory, and then immediately delete the object within that subdirectory.

• Create an object with the name of the subdirectory that is zero bytes in length and has WRITER access control list permission.

• Create an object with the name of the subdirectory that is zero bytes in length. Set the Content-Type metadata to CLOUDSTORAGE_FOLDER.

Your company’s corporate policy states that there must be a copyright comment at the very beginning of all source files. You want to write a custom step in Cloud Build that is triggered by each source commit. You need the trigger to validate that the source contains a copyright and add one for subsequent steps if not there. What should you do?

• Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.

• Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files do not need to be committed back to the source repository.

• Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are written back to the Cloud Storage bucket.

• Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.

One of your deployed applications in Google Kubernetes Engine (GKE) is having intermittent performance issues. Your team uses a third-party logging solution. You want to install this solution on each node in your GKE cluster so you can view the logs. What should you do?

• Deploy the third-party solution as a DaemonSet

• Modify your container image to include the monitoring software

• Use SSH to connect to the GKE node, and install the software manually

• Deploy the third-party solution using Terraform and deploy the logging Pod as a Kubernetes Deployment

You are developing an application that consists of several microservices running in a Google Kubernetes Engine cluster. One microservice needs to connect to a third-party database running on-premises. You need to store credentials to the database and ensure that these credentials can be rotated while following security best practices. What should you do?

• Store the credentials in a sidecar container proxy, and use it to connect to the third-party database.

• Configure a service mesh to allow or restrict traffic from the Pods in your microservice to the database.

• Store the credentials in an encrypted volume mount, and associate a Persistent Volume Claim with the client Pod.

• Store the credentials as a Kubernetes Secret, and use the Cloud Key Management Service plugin to handle encryption and decryption.

You manage your company's ecommerce platform's payment system, which runs on Google Cloud. Your company must retain user logs for 1 year for internal auditing purposes and for 3 years to meet compliance requirements. You need to store new user logs on Google Cloud to minimize onpremises storage usage and ensure that they are easily searchable. You want to minimize effort while ensuring that the logs are stored correctly. What should you do?

• Store the logs in a Cloud Storage bucket with bucket lock turned on.

• Store the logs in a Cloud Storage bucket with a 3-year retention period.

• Store the logs in Cloud Logging as custom logs with a custom retention period.

• Store the logs in a Cloud Storage bucket with a 1-year retention period. After 1 year, move the logs to another bucket with a 2-year retention period.

Your company has a new security initiative that requires all data stored in Google Cloud to be encrypted by customer-managed encryption keys. You plan to use Cloud Key Management Service (KMS) to configure access to the keys. You need to follow the "separation of duties" principle and Google-recommended best practices. What should you do? (Choose two.)

• Provision Cloud KMS in its own project.

• Do not assign an owner to the Cloud KMS project.

• Provision Cloud KMS in the project where the keys are being used.

• Grant the roles/cloudkms.admin role to the owner of the project where the keys from Cloud KMS are being used.

• Grant an owner role for the Cloud KMS project to a different user than the owner of the project where the keys from Cloud KMS are being used.

You need to migrate a standalone Java application running in an on-premises Linux virtual machine (VM) to Google Cloud in a cost-effective manner. You decide not to take the lift-and-shift approach, and instead you plan to modernize the application by converting it to a container. How should you accomplish this task?

• Use Migrate for Anthos to migrate the VM to your Google Kubernetes Engine (GKE) cluster as a container.

• Export the VM as a raw disk and import it as an image. Create a Compute Engine instance from the Imported image.

• Use Migrate for Compute Engine to migrate the VM to a Compute Engine instance, and use Cloud Build to convert it to a container.

• Use Jib to build a Docker image from your source code, and upload it to Artifact Registry. Deploy the application in a GKE cluster, and test the application.

Your organization has recently begun an initiative to replatform their legacy applications onto Google Kubernetes Engine. You need to decompose a monolithic application into microservices. Multiple instances have read and write access to a configuration file, which is stored on a shared file system. You want to minimize the effort required to manage this transition, and you want to avoid rewriting the application code. What should you do?

• Create a new Cloud Storage bucket, and mount it via FUSE in the container.

• Create a new persistent disk, and mount the volume as a shared PersistentVolume.

• Create a new Filestore instance, and mount the volume as an NFS PersistentVolume.

• Create a new ConfigMap and volumeMount to store the contents of the configuration file.

Your development team has built several Cloud Functions using Java along with corresponding integration and service tests. You are building and deploying the functions and launching the tests using Cloud Build. Your Cloud Build job is reporting deployment failures immediately after successfully validating the code. What should you do?

• Check the maximum number of Cloud Function instances.

• Verify that your Cloud Build trigger has the correct build parameters.

• Retry the tests using the truncated exponential backoff polling strategy.

• Verify that the Cloud Build service account is assigned the Cloud Functions Developer role.