Your application images are built wing Cloud Build and pushed to Google Container Registry (GCR). You want to be able to specify a particular version of your application for deployment based on the release version tagged in source control. What would you do when you push the image?

• A.Use Cloud Build to include the release version tag in the application image.
• B.Use GCR digest versioning to match the image to the tag in source control.
• C.Reference the image digest in the source control tag.
• D.Supply the source control tag as a parameter within the image name.

Comment: *

Name: *

Email: *

Verification: *

You manage an application that is writing logs to Stackdriver Logging. You need to give some team members the ability to export logs. What should you do?

• A.Create an Organizational Policy in Cloud IAM to allow only these members to create log exports.
• B.Create and grant a custom IAM role with the permissions logging.sinks.list and logging.sink.get.
• C.Configure Access Context Manager to allow only these members to export logs.
• D.Grant the team members the IAM role of logging.configWriter on Cloud IAM.

Comment: *

Name: *

Email: *

Verification: *

The new version of your containerized application has been tested and is ready to be deployed to production on Google Kubernetes Engine (GKE) You could not fully load-test the new version in your pre-production environment and you need to ensure that the application does not have performance problems after deployment Your deployment must be automated What should you do?

• A.Deploy the application through a continuous delivery pipeline by using canary deployments Use Cloud Monitoring to look for performance issues, and ramp up traffic as supported by the metrics
• B.Deploy the application through a continuous delivery pipeline by using blue/green deployments Migrate traffic to the new version of the application and use Cloud Monitoring to look for performance issues
• C.Deploy the application by using kubectl and use Config Connector to slowly ramp up traffic between versions. Use Cloud Monitoring to look for performance issues
• D.Deploy the application by using kubectl and set the spec. updatestrategy. type field to RollingUpdate Use Cloud Monitoring to look for performance issues, and run the kubectl rollback command if there are any issues.

Comment: *

Name: *

Email: *

Verification: *

You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?

• A.Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application
• B.Inject the secret at the time of instance creation via an encrypted configuration management system.
• C.Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently
• D.Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.

Comment: *

Name: *

Email: *

Verification: *

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 A/B testing
• D.Rolling update deployment and shadow testing

Comment: *

Name: *

Email: *

Verification: *