Google Associate Cloud Engineer - Practice Test 1
You need to provision a new Compute Engine instance within a Google Cloud project that does not yet exist. Which sequence of steps should you follow?
Before any resources can be created, a project must first exist and have billing enabled. Once the project is established, the necessary APIs, such as the Compute Engine API, must be explicitly enabled within that project. Only after these foundational steps are completed can a Compute Engine instance be successfully provisioned.
Your organization manages diverse datasets, each with distinct storage needs. These datasets include: 1. Customer profiles that are structured and frequently queried with complex operations. 2. Extensive historical audit logs, rarely accessed but critical for compliance. 3. High-throughput IoT sensor readings, requiring real-time ingestion and analysis, with some tolerance for data loss during peak loads. You need to implement the most cost-effective Google Cloud storage solution that meets all these requirements. Which combination of services should you choose?
Cloud SQL is ideal for structured customer data requiring complex queries. Cloud Storage Coldline offers a cost-effective solution for infrequently accessed, large-volume historical logs. BigQuery is well-suited for high-velocity sensor data, providing real-time analytics capabilities and handling large datasets efficiently.
A managed instance group (MIG) in Google Cloud has failed to create new instances, leading to a reduced number of running instances below the desired target. This is impacting the application's ability to handle expected traffic. You suspect an issue with persistent disks preventing new instance creation. What is the most appropriate action to resolve this issue and ensure the MIG can scale correctly?
The primary cause of this issue is often persistent disks not being deleted when instances are terminated, leading to name conflicts when new instances try to provision. The solution involves deleting the conflicting persistent disks and then updating the instance template to set `disks.autoDelete` to `true` for boot disks, which ensures disks are automatically deleted with their instances in the future. While a rolling update might be needed to apply template changes, the core problem resolution involves the disk management and template update.
You need to deploy a stateless web application with a web interface and multiple API endpoints. This application requires internal IP address accessibility from your company's private Virtual Private Cloud (VPC) and on-premises network for security reasons. You also need to frequently update the application with minimal operational overhead and manage the least amount of cloud infrastructure. Which Google Cloud solution should you implement?
Cloud Run is ideal for stateless web applications requiring minimal infrastructure management and frequent updates. Private Service Connect enables access to Cloud Run services from internal IP addresses within your VPC and, through proper network configuration like VPN or Interconnect, from on-premises networks. Private Google Access, on the other hand, is for internal Google Cloud resources to reach Google APIs and services, not for on-premises networks to access Cloud Run services.
You are designing a data archiving solution on Google Cloud Platform to meet compliance requirements for data originating from a single geographical region. This data needs to be archived after 30 days and will be accessed approximately once per year. Which Google Cloud Storage configuration should you choose?
Since the data originates from a single geographical location and compliance objectives require it to remain there, Regional Storage is appropriate. For data accessed annually (less than once per quarter), Coldline Storage is the most cost-effective option, and a lifecycle rule automates the transition after 30 days.