Google Associate Cloud Engineer Practice Test 5
Question 40
A budget notification must reach a non-billing stakeholder outside the default billing-admin distribution. Which supported integration helps?
- Add a Cloud Monitoring email notification channel for the stakeholder and link it to the budget.
- Add the stakeholder to the project’s SSH-keys metadata only.
- Create a VPC subnet named budget-alert-recipient.
- Turn on Cloud Trace for the budget’s project and expect it to email billing events.
Explanation
Correct Answer
A:The budget can use Cloud Monitoring email notification channels to reach authorized people outside default billing-role recipients. Recipients need additional financial permissions only if they must open the underlying budget data in the console.
Incorrect Answers
B:SSH metadata governs VM login, not notification routing.
C:A subnet name does not configure a budget alert destination.
D:Cloud Trace is for request tracing and does not automatically route billing notifications.
Question 41
A finance team wants an incident automation to receive the current state of a Cloud Billing budget without waiting for threshold alert emails. Which integration creates programmatic budget messages?
- Export Compute Engine serial console logs to the incident project; they include a billing-budget status envelope.
- Enable a Cloud Monitoring dashboard widget; dashboards automatically publish every billing budget update to Pub/Sub.
- Connect the billing budget to a Pub/Sub topic and have an authorized consumer process budget-status notifications.
- Create a Cloud Storage bucket retention policy so budget alerts become object finalize events.
Explanation
Correct Answer
C:Connect the billing budget to a Pub/Sub topic and have an authorized consumer process budget-status notifications. Google provides budget programmatic notifications through Pub/Sub, including current status updates sent multiple times per day. A consumer handles these messages.
Incorrect Answers
A:Export Compute Engine serial console logs to the incident project; they include a billing-budget status envelope. Serial-console output describes VM startup, not the billing budget record. It cannot supply periodic budget-status messages to the incident workflow.
B:Enable a Cloud Monitoring dashboard widget; dashboards automatically publish every billing budget update to Pub/Sub. A visualization does not itself configure the billing-budget Pub/Sub publisher. The team must connect the budget notification feed explicitly.
D:Create a Cloud Storage bucket retention policy so budget alerts become object finalize events. Object lifecycle events describe bucket data changes. They are not the Cloud Billing service publishing spend-status messages.
Question 42
A finance team wants daily itemized usage and pricing analysis across projects with SQL. What service should receive the export?
- Send billing rows to Cloud Logging only and query them as audit log entries.
- Export only the current list of Compute Engine instances as CSV.
- Use a billing budget email because it contains an itemized daily price ledger.
- Configure the appropriate Cloud Billing usage and, if needed, pricing exports into BigQuery datasets.
Explanation
Correct Answer
D:Cloud Billing exports to BigQuery make supported charges and price-list data available as queryable tables. Select the relevant export types and grant least-privilege dataset access to the analysts who need cross-project SQL reporting.
Incorrect Answers
A:Application and audit logs do not replace the structured, account-wide usage and price data required for financial queries.
B:An instance list omits charges for other services and lacks the billing SKU and price history columns.
C:Budget email notifications summarize thresholds rather than providing daily SQL-ready billing line items.
Question 43
A finance team activates Cloud Billing usage export today and asks for complete SKU-level cost history from three years ago. What limitation must it check before promising that report?
- Assume a new export always backfills every invoice line and usage charge ever generated for the billing account.
- Check the selected export type, dataset location and documented backfill window; retrieve older records through other available billing reports when needed.
- Assume that creating a BigQuery view retroactively recreates billing export records that were never written.
- Delete the export dataset and re-enable it until the full historical period appears automatically.
Explanation
Correct Answer
B:Check the selected export type, dataset location and documented backfill window; retrieve older records through other available billing reports when needed. Google documents separate cost-export types and history/backfill constraints. The analyst should establish what the selected export actually contains before claiming years of detailed records.
Incorrect Answers
A:Assume a new export always backfills every invoice line and usage charge ever generated for the billing account. Export history depends on the export product, the start date and the destination. Activation alone does not guarantee full retroactive SKU-level records.
C:Assume that creating a BigQuery view retroactively recreates billing export records that were never written. A BigQuery view can transform existing rows, but it cannot reconstruct usage records that the Cloud Billing export never populated.
D:Delete the export dataset and re-enable it until the full historical period appears automatically. Repeated deletion discards existing data and does not expand the documented backfill window. The problem is availability of historical source rows, not dataset corruption.
Question 44
A company enables Cloud Billing cost export, but its destination BigQuery dataset sits in a FinOps project linked to a different billing account than the account being exported. What must be corrected?
- Give the analyst extra BigQuery query access and leave the dataset project linked to the unrelated billing account.
- Create another View-only report in the existing dataset; this changes which billing account pays for the project.
- Disable BigQuery billing on the destination project because cost export never requires a billable project.
- Use an authorized export dataset in a project whose billing link matches the account containing the costs to export.
Explanation
Correct Answer
D:Use an authorized export dataset in a project whose billing link matches the account containing the costs to export. Google's export setup requires the project hosting the destination dataset to be linked to the relevant Cloud Billing account. Correcting that association resolves the mismatch.
Incorrect Answers
A:Give the analyst extra BigQuery query access and leave the dataset project linked to the unrelated billing account. BigQuery query privileges allow reading data but do not repair the billing linkage requirement for the export destination project.
B:Create another View-only report in the existing dataset; this changes which billing account pays for the project. A view rearranges stored data. It does not alter the Cloud Billing account associated with the project that hosts the export dataset.
C:Disable BigQuery billing on the destination project because cost export never requires a billable project. The destination BigQuery project must have billing enabled. Disabling billing would not satisfy the documented setup prerequisite.
Question 45
A Cloud Billing administrator has enabled the standard usage-cost export, but an analyst needs resource-level cost attributes provided by the detailed usage schema. What separate configuration is required?
- Create another view on the standard export; views automatically add detailed-cost-only fields to its source table.
- Enable the Compute Engine API again; API enablement changes the Cloud Billing export schema.
- Add an organization Viewer IAM role to the analyst so BigQuery generates the additional detailed fields.
- Enable the detailed usage-cost export and query its separately maintained detailed table and supported fields.
Explanation
Correct Answer
D:Enable the detailed usage-cost export and query its separately maintained detailed table and supported fields. Google lists standard and detailed usage-cost exports as separate export types. The detailed option must be enabled and its schema used to obtain the additional attributes.
Incorrect Answers
A:Create another view on the standard export; views automatically add detailed-cost-only fields to its source table. Views can expose or transform the columns already present in their underlying table; they cannot manufacture resource-level columns never exported by the standard feed.
B:Enable the Compute Engine API again; API enablement changes the Cloud Billing export schema. Service Usage controls Google API activation, not whether the detailed billing-export data product is enabled.
C:Add an organization Viewer IAM role to the analyst so BigQuery generates the additional detailed fields. IAM role grants control access to existing data. They do not switch the export from the standard schema to the detailed usage-cost format.
Question 46
A FinOps analyst wants to examine historical changes in the Cloud Billing price list independently of usage and estimated charges. Which export type is intended for this?
- Use only the standard usage-cost export and assume it is the full product price catalog.
- Create a spending budget because threshold notification history is the authoritative pricing database.
- Use only a Cloud Logging sink, because infrastructure audit events include the effective price of every SKU.
- Enable Cloud Billing pricing-data export to BigQuery alongside any required usage-cost exports.
Explanation
Correct Answer
D:Enable Cloud Billing pricing-data export to BigQuery alongside any required usage-cost exports. Google documents a distinct pricing export in addition to standard/detailed usage data. It is the relevant source when the question concerns list prices rather than consumed resources.
Incorrect Answers
A:Use only the standard usage-cost export and assume it is the full product price catalog. Usage exports describe consumption and estimated charges. The dedicated pricing-data export exposes price-related dimensions for separate analysis.
B:Create a spending budget because threshold notification history is the authoritative pricing database. Budget alerts compare charges with thresholds; they do not provide a SKU price history for systematic price-list analysis.
C:Use only a Cloud Logging sink, because infrastructure audit events include the effective price of every SKU. Audit logs describe administrative or resource events and are not a Cloud Billing pricing catalog for SKUs.
Question 47
A project is linked to a billing account but the finance team has no budget visibility because it selected a different account in the console. What should be checked first?
- Assume every account in the console shows all of the organization’s budgets, regardless of payer.
- Recreate the same budget under the account used by a different business unit.
- Open the actual paying Cloud Billing account, then verify the budget’s project and service filters.
- Change the project’s region to match the finance team’s location.
Explanation
Correct Answer
C:The project’s charges and corresponding billing-account budgets must be inspected in the correct payer context. Check account selection, authorized access and scope filters before concluding that the budget is missing.
Incorrect Answers
A:Budgets belong to a particular paying account or supported project scope, not every account in an organization.
B:Copying a budget to an unrelated billing account would not repair access to the existing budget.
D:Resource location does not determine which billing account’s budget appears in the console.
Question 48
A previously working Cloud Billing budget-to-Pub/Sub integration stops producing messages just after administrators remove the topic publisher grant. The budget and topic still exist. Which permission change should be reviewed?
- Restore the documented Cloud Billing publisher identity's Pub/Sub Publisher permission on the intended topic.
- Grant the finance analyst Cloud Run Invoker; that role authorizes the budget publisher to write to Pub/Sub.
- Move the Cloud Billing account into the VPC subnet because only local-subnet budgets can publish notifications.
- Increase the percentage threshold on the budget; topic IAM permission errors disappear when the limit is higher.
Explanation
Correct Answer
A:Restore the documented Cloud Billing publisher identity's Pub/Sub Publisher permission on the intended topic. Budget notifications require the billing service to publish to the configured Pub/Sub topic. Removing its publishing permission can stop delivery despite a valid budget.
Incorrect Answers
B:Grant the finance analyst Cloud Run Invoker; that role authorizes the budget publisher to write to Pub/Sub. Cloud Run Invoker authorizes requests to a Cloud Run service. It does not confer Pub/Sub topic publishing permission on Cloud Billing.
C:Move the Cloud Billing account into the VPC subnet because only local-subnet budgets can publish notifications. Billing accounts are not VPC endpoints and a subnet change cannot repair a Pub/Sub topic IAM policy that denies publication.
D:Increase the percentage threshold on the budget; topic IAM permission errors disappear when the limit is higher. A threshold controls when email alerts are generated, not whether the budget publisher has permission to send Pub/Sub notifications.
Question 49
A monthly bill rose unexpectedly. Finance needs to distinguish Compute Engine CPU charges from Cloud Storage charges by service and SKU across projects on one billing account. Which data source answers that question?
- Inspect project IAM audit logs, which list every invoice charge with its service and SKU price.
- Compare total project VM counts only; running VM inventory includes all storage, network, and database SKU charges.
- Read budget-alert email subjects, which contain a complete per-SKU ledger for the billing account.
- Query the billing account's Cloud Billing usage-cost export in BigQuery, grouped by service and SKU with relevant project filters.
Explanation
Correct Answer
D:Query the billing account's Cloud Billing usage-cost export in BigQuery, grouped by service and SKU with relevant project filters. The billing export provides charge records with service and SKU dimensions for the linked projects. Grouping those rows identifies the source of the increase.
Incorrect Answers
A:Inspect project IAM audit logs, which list every invoice charge with its service and SKU price. IAM audit logs record authorization or configuration events, not the complete accounting ledger. They cannot reconcile service/SKU charges.
B:Compare total project VM counts only; running VM inventory includes all storage, network, and database SKU charges. Compute Engine inventory excludes other billed services and cannot determine cost solely from counts. The invoice increase needs usage-cost data.
C:Read budget-alert email subjects, which contain a complete per-SKU ledger for the billing account. Budget notifications show budget status or thresholds, not a full itemized account-wide usage ledger suitable for SKU attribution.
Question 50
A cost anomaly appears in a billing export but a team uses the CSV result to claim the bill is already finalized. What interpretation is safer?
- Treat export values as usage/cost records that may still be adjusted, and reconcile against the finalized invoice.
- Treat any CSV row with a project ID as a legally finalized invoice line.
- Assume billing exports cannot be delayed because BigQuery queries are immediate.
- Delete the export table after detecting an anomaly so finance does not count it twice.
Explanation
Correct Answer
A:Billing export records can have ingestion latency and adjustments; finance should distinguish estimates and usage attribution from the formally issued invoice. Preserve the export as evidence while reconciling final billed amounts and credits.
Incorrect Answers
B:A project identifier is not an invoice finalization marker, even if the row includes a charge.
C:Fast SQL query execution says nothing about when upstream usage is reported or adjusted.
D:Deleting cost evidence makes reconciliation harder and does not correct a potentially provisional amount.