Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A cloud financial analyst is investigating an unexpected spending spike that occurred over the past week in their organization's Google Cloud environment. Using Cloud Billing Reports, the analyst needs to pinpoint the cause of the anomaly based on the following requirements:
prod-analytics project and the BigQuery service.How should the analyst configure the Cloud Billing Report to meet these requirements?
In Cloud Billing Reports, the Spend-based CUDs filter isolates usage costs and commitment fee SKUs associated with spend-based committed use discounts. Grouping by Label keys organizes cost data according to custom key:value metadata pairs (such as environment:dev or cost_center:marketing) that administrators have attached to Google Cloud resources.
prod-analytics project and BigQuery service.This configuration would be appropriate if a billing administrator wanted to evaluate how current-month spend-based committed use discounts were distributed across resources tagged with a specific custom label key, such as environment or team.
While labels are a best practice for allocating costs to teams or environments, they only reflect tagged resources. When troubleshooting an unexpected service spike, filtering directly by Project and Service and grouping by Date > SKU guarantees visibility into all billable items regardless of whether resource labels were configured.
In Cloud Billing Reports, the Billing period (formerly Invoice month) time range returns usage costs and invoice-level charges—such as taxes, adjustments, and surcharges—for completed monthly invoices. The No grouping (show total cost only) option aggregates all matching charges into a single summarized total for the selected timeframe.
prod-analytics and BigQuery.This configuration would be appropriate if an accounting team needed to view the overall, ungrouped total cost across the entire Cloud Billing account for a completed invoice month, including invoice-level taxes and adjustments.
When investigating recent operational anomalies or sudden usage spikes, analysts should use a Charge period (usage date) time range with specific Filters and granular Group by dimensions (like SKU or Date > SKU) rather than ungrouped monthly invoice views.
Cloud Billing Reports allow users to analyze long-term historical spending trends across multiple months or years. Using the Locations filter restricts report data by geographic regions or multi-regions, while the Month > Project Hierarchy grouping summarizes monthly costs by organizational folders, organizations, and projects.
us-east1) or multi-region (such as us*) rather than isolating the prod-analytics project and BigQuery service.This configuration would be the right choice if an executive wanted to review multi-year, month-over-month spending trends across organizational folders and projects within a specific geographic region.
While Month > Project Hierarchy is valuable for high-level financial governance and chargeback across business units over long periods, pinpointing a recent 7-day cost spike requires a short time range, Project and Service filters, and SKU-level grouping.
Cloud Billing Reports provide interactive visual charts and customizable tables that allow organizations to monitor cloud spending, analyze usage patterns, and identify underlying cost drivers. Combining Time range settings, Filters, and multiple-dimension Group by options enables analysts to narrow down broad billing datasets into actionable, granular insights when investigating cost anomalies.
prod-analytics project and BigQuery service: Applying the Projects and Services filter tiles refines the dataset returned to the report so that only usage charges associated with prod-analytics and BigQuery are displayed.Unlike single-dimension project or service groupings that aggregate totals across the entire time range in the table, Date > SKU paired with Project and Service filters isolates the exact workload and lets the analyst expand the exact day of the anomaly to see which specific SKUs caused the cost spike.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated