Free Google Associate Cloud Engineer Exam Dumps and Associate Cloud Engineer Exam Questions

Question No: 1

MultipleChoice

You're attempting to set up a File based Billing Export. Which of the following components are required?

Options

AA Cloud Storage bucket.

BA BigQuery dataset.

CA report prefix.

DA Budget and at least one alert.

Question No: 2

MultipleChoice

You've been asked to add Martha Jones as a member of the "Production Storefront App" project; Using the email address martha.jones@tardis.com with the App Engine Admin role. You browse to the IAM page in the console and attempt to add her, however, you get the following error.

"Email addresses and domains must be associated with an active Google Account or Google Apps account."

What's the most likely cause for this error?

Options

AMartha has already been added as a to this project as a different member.

BMartha has been denied access due to a policy on the Organization.

CMartha hasn't been added as a user inside the Company's G Suite account.

DMartha has an outstanding bill with Google and can't be added until the bill is paid.

Question No: 3

MultipleChoice

You're attempting to remove the zone property from the Compute Engine service, that was set with the incorrect value. Which command would accomplish your task?

Options

Agcloud config unset compute/zone

Bgcloud config unset zone

Cgcloud config configurations unset compute/zone

Dgcloud unset compute/zone

Question No: 4

MultipleChoice

Your boss has asked you to set up the CFO as a user inside Google Cloud. Before walking away, she said, "And obviously you know which role to assign him."

Which role was she likely talking about, and why is it obvious? (Select one role and one reason)

Options

AReason: This role will ensure the CFO has full access to the project.

BRole: Billing Account Viewer

CReason: This role will ensure the CFO has access to view the spending data.

DRole: Project Owner

ERole: Billing Account Admin

FReason:: This role will ensure the CFO can perform any billing task that they may need.

Question No: 5

MultipleChoice

You and your team have been working on a new application over the past couple weeks. While it's still in development, it's becoming a bit costly for your limited budget. The entire team had a meeting on Friday to talk about how to save money until you're able to launch. One of your team members suggested shutting down some services overnight and during the weekend. Though no official decision was made before leaving for the weekend, a junior team member sent out an email saying he found a solution to the problem.

When arriving at the office on Monday, you find that your project is no longer in the drop-down inside the Console. What's the most likely reason for the missing project?

Options

AThe project was moved to another account.

BYour trial credits expired, and the project was removed.

CThe engineer removed the project and attached all of the resources directly to the Organization.

DThe engineer clicked the 'shut down' link thinking it was like a light switch that he could toggle on and off.

Question No: 6

MultipleChoice

You're deploying an application to a Compute Engine instance, and it's going to need to make calls to read from Cloud Storage and Bigtable. You want to make sure you're following the principle of least privilege. What's the easiest way to ensure the code can authenticate to the required Google Cloud APIs?

Options

ACreate a new user account with the required roles. Store the credentials in Cloud Key Management Service and download them to the instance in code.

BUse the default Compute Engine service account and set its scopes. Let the code find the default service account using 'Application Default Credentials'.

CCreate a new service account and key with the required limited permissions. Set the instance to use the new service account. Edit the code to use the service account key.

DRegister the application with the Binary Registration Service and apply the required roles.

Question No: 7

MultipleChoice

2. Your auditor wants to view your organization's use of data in Google Cloud. The auditor is most interested in auditing who accessed data in Cloud Storage buckets. You need to help the auditor access the data they need. What should you do?

Options

AAssign the appropriate permissions, and then use Cloud Monitoring to review metrics

BUse the export logs API to provide the Admin Activity Audit Logs in the format they want

CTurn on Data Access Logs for the buckets they want to audit, and Then build a query in the log viewer that filters on Cloud Storage

DAssign the appropriate permissions, and then create a Data Studio report on Admin Activity Audit Logs

Question No: 8

MultipleChoice

Your application stores files on Cloud Storage by using the Standard Storage class. The application only requires access to files created in the last 30 days. You want to automatically save costs on files that are no longer accessed by the application. What should you do?

Options

AEnable object versioning on the storage bucket and add lifecycle rules to expire non-current versions after 30 days.

BCreate an object lifecycle on the storage bucket to change the storage class to Archive Storage for objects with an age over 30 days.

CCreate a retention policy on the storage bucket of 30 days, and lock the bucket by using a retention policy lock.

DCreate a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files older than 30 days.

Answer
BExplanation

Object lifecycle management is a feature of Cloud Storage that allows you to automatically manage the storage class and retention of your objects. You can use object lifecycle management to reduce the cost of storing your data by transitioning objects to lower-cost storage classes, such as Archive Storage, which is designed for long-term storage of data that is rarely accessed. You can also use object lifecycle management to delete objects that are no longer needed after a certain period of time. To use object lifecycle management, you need to create a lifecycle configuration, which is a set of rules that specify the actions to take on objects that match certain conditions. You can apply a lifecycle configuration to a storage bucket, and it will affect all objects in that bucket.

In this scenario, you want to automatically save costs on files that are no longer accessed by the application after 30 days. Therefore, you should create an object lifecycle on the storage bucket to change the storage class to Archive Storage for objects with an age over 30 days. This way, you can keep the files in the bucket, but pay less for storing them. Archive Storage has the lowest cost per GB among all storage classes, but also has the highest retrieval and early deletion fees. Therefore, it is suitable for data that is rarely accessed and has a long retention period.

The other options are not correct because they either do not reduce the cost of storage, or they delete the files that you may still need. Option A is not correct because enabling object versioning on the storage bucket and adding lifecycle rules to expire non-current versions after 30 days will only affect the old versions of the files, not the current ones. Therefore, you will still pay the same amount for storing the current files in the Standard Storage class. Option C is not correct because creating a retention policy on the storage bucket of 30 days, and locking the bucket by using a retention policy lock will prevent you from deleting or modifying any object in the bucket for 30 days. This will not reduce the cost of storage, and it will also limit your flexibility to manage your data. Option D is not correct because creating a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files older than 30 days will permanently remove the files from the bucket. This may not be what you want, as you may still need to access the files for backup, audit, or compliance purposes.

Object Lifecycle Management

Storage Classes

Archive Storage

Question No: 9

MultipleChoice

You are planning to migrate the following on-premises data management solutions to Google Cloud:

* One MySQL cluster for your main database

* Apache Kafka for your event streaming platform

* One Cloud SQL for PostgreSQL database for your analytical and reporting needs

You want to implement Google-recommended solutions for the migration. You need to ensure that the new solutions provide global scalability and require minimal operational and infrastructure management. What should you do?

Options

AMigrate from MySQL to Cloud SQL, from Kafka to Pub/Sub, and from Cloud SQL for PostgreSQL to BigQuery.

BMigrate from MySQL to Cloud Spanner, from Kafka to Pub/Sub, and from Cloud SQL for PostgreSQL to BigQuery.

CMigrate from MySQL to Cloud Spanner, from Kafka to Memorystore, and from Cloud SQL for PostgreSQL to Cloud SQL.

DMigrate from MySQL to Cloud SQL, from Kafka to Memorystore, and from Cloud SQL for PostgreSQL to Cloud SQL.

Answer
BExplanation

Cloud Spanner, Pub/Sub, and BigQuery are Google-recommended solutions for migrating your on-premises data management solutions to Google Cloud. They provide global scalability and require minimal operational and infrastructure management. Here is why:

Cloud Spanner is a fully managed, relational database service that offers strong consistency, high availability, and horizontal scalability across regions and continents. It is compatible with MySQL and can handle high-throughput OLTP workloads. It is a good choice for migrating your main database from MySQL to Google Cloud, as it can support your application's performance, availability, and growth requirements.

Pub/Sub is a fully managed, real-time messaging service that allows you to send and receive messages between independent applications. It is compatible with Apache Kafka and can handle high-volume event streaming and data ingestion. It is a good choice for migrating your event streaming platform from Kafka to Google Cloud, as it can support your application's reliability, scalability, and flexibility requirements.

BigQuery is a fully managed, serverless data warehouse that offers fast SQL queries, high scalability, and low cost. It is compatible with Cloud SQL for PostgreSQL and can handle complex analytical and reporting needs. It is a good choice for migrating your analytical and reporting database from Cloud SQL for PostgreSQL to Google Cloud, as it can support your application's speed, efficiency, and innovation requirements.

The other options are not correct because they either do not provide the required scalability, performance, or functionality. Option A is not correct because Cloud SQL is a regional, managed database service that does not offer the same level of scalability, availability, and consistency as Cloud Spanner. Option C is not correct because Memorystore is a regional, managed in-memory data store that does not offer the same level of functionality, durability, and integration as Pub/Sub. Option D is not correct because Cloud SQL is a regional, managed database service that does not offer the same level of scalability, performance, and cost-effectiveness as BigQuery.

Migrating from MySQL to Cloud Spanner

Migrating from Apache Kafka to Cloud Pub/Sub

Migrating from Cloud SQL for PostgreSQL to BigQuery

Question No: 10

MultipleChoice

You want to enable your development team to deploy new features to an existing Cloud Run service in production. To minimize the risk associated with a new revision, you want to reduce the number of customers who might be affected by an outage without introducing any development or operational costs to your customers. You want to follow Google-recommended practices for managing revisions to a service. What should you do?

Options

AGradually roll out the new revision and split customer traffic between the revisions to allow rollback in case a problem occurs.

BDeploy your application to a second Cloud Run service, and ask your customers to use the second Cloud Run service.

CAsk your customers to retry access to your service with exponential backoff to mitigate any potential problems after the new revision is deployed.

DSend all customer traffic to the new revision, and roll back to a previous revision if you witness any problems in production.

Answer
AExplanation

Cloud Run is a fully managed platform that allows you to deploy and run containerized applications without worrying about the underlying infrastructure. Cloud Run automatically scales your application based on the incoming requests, and you only pay for the resources you use. Cloud Run also supports deploying multiple revisions of your service, and splitting the customer traffic between them. This allows you to gradually roll out new features, test them in production, and monitor their performance and reliability. If you encounter any problems with the new revision, you can easily roll back to a previous revision by adjusting the traffic split. This is a Google-recommended practice for managing revisions to a service, as it minimizes the risk associated with a new revision, reduces the number of customers who might be affected by an outage, and does not introduce any development or operational costs to your customers.

The other options are not correct because they either do not follow the Google-recommended practice, or they do not reduce the risk or cost associated with a new revision. Option B is not correct because deploying your application to a second Cloud Run service, and asking your customers to use the second Cloud Run service, is not a gradual roll out, but a complete switch. This may cause confusion and inconvenience for your customers, and it does not allow you to monitor the performance and reliability of the new revision in comparison with the old one. Option C is not correct because asking your customers to retry access to your service with exponential backoff to mitigate any potential problems after the new revision is deployed, is not a good user experience, and it does not address the root cause of the problems. Option D is not correct because sending all customer traffic to the new revision, and rolling back to a previous revision if you witness any problems in production, is a risky and costly strategy, as it exposes all your customers to the potential problems, and it does not allow you to test the new revision before deploying it to all customers.

Cloud Run documentation

Managing revisions

Splitting traffic