Clustering in BigQuery sorts the data based on the values of one or more columns, called clustering columns. This helps to: Improve query performance by organizing related data together, making it faster to locate specific rows. Reduce query costs by reducing the amount of data scanned. For example, clustering a table on `user_id` and `timestamp` can speed up queries filtering on these columns.

SELECT product,sales, ROUND(sales * 100.0 / SUM(sales) OVER (), 2) AS sales_percentage FROM sales_table ORDER BY sales_percentage DESC; SUM() OVER() without PARTITION BY gives the grand total for percentage calculation.

- Secure Remote Access: Secure remote access to resources like virtual machines and databases can be achieved with Google Cloud Platform (GCP) via secure shell (SSH) tunneling. - Proxying Traffic: It is frequently employed for secure proxy traffic between a local computer and google cloud-deployed resources, such as Kubernetes clusters. - Database Connection: Secure connections to databases such as Cloud SQL can be created from local development environments via SSH tunneling. - Bypassing Firewalls: It can be utilized for securely access internal GCP resources from external networks without avoiding firewalls. - Secure File Transfer: Using SCP or SFTP, SSH tunneling allows safe file transfers between local machines and the Google Cloud Platform instances.

C. Assign event time timestamps and configure watermarks with allowed lateness and triggers. The correct option is Assign event time timestamps and configure watermarks with allowed lateness and triggers. This approach uses event time to place each record in the correct logical window which preserves the true time semantics of the data. Watermarks provide a best effort signal of how far event time has progressed so the pipeline knows when it likely has seen all on time data for a window. Allowed lateness lets the window remain open for a bounded period so late records can still update results. Triggers control when to emit early on time and late results so you can produce timely outputs and then refine them as more data arrives. With appropriate accumulation mode the pipeline can update aggregates when late events show up which keeps results correct and predictable for both batch and streaming runs. Configure sliding windows wide enough to cover lagging records is not sufficient because widening windows only trades latency for some tolerance of delay and it still cannot guarantee correctness for arbitrarily late or out of order events. Without event time semantics watermarks allowed lateness and triggers the pipeline will either drop late data or place it in the wrong window. Use a single global window to simplify aggregation across all events removes natural boundaries which leads to unbounded state and makes it difficult to reason about completeness. Even with triggers you lose predictable finality for aggregates and you still need event time watermarks and allowed lateness to handle out of order and late arrivals in a controlled way. Enable Pub/Sub message ordering and rely on processing time windows for consistency does not address the core problem because ordering is not guaranteed end to end and processing time windows reflect when Dataflow sees messages rather than when events actually occurred. This leads to misattributed counts and incorrect aggregates whenever events are delayed or arrive out of order. When a question mentions late or out of order events choose event time windowing with watermarks plus allowed lateness and triggers rather than processing time or message ordering. Then think about how results should accumulate as late data arrives.

To monitor Google Cloud Dataflow pipelines effectively, you can use the following tools: - Stackdriver Logging: Monitor job execution and view logs for debugging purposes. - Stackdriver Monitoring: Track pipeline performance metrics such as CPU utilization, throughput, and processing latency. - Dataflow UI: The Dataflow UI provides real-time insights into the pipeline's progress and performance.

C. Create a materialized view that aggregates retail_ops.sales_events and restricts it to the last 12 months of partitions. The correct option is Create a materialized view that aggregates retail_ops.sales_events and restricts it to the last 12 months of partitions. A materialized view precomputes AVG, MAX, and SUM and incrementally refreshes only the portions of data that change. This gives very low latency and cost for dashboards and services that run frequent aggregate queries. Restricting the materialized view to the most recent 12 months means queries scan far less data while the base table continues to hold all historical rows for auditing. BigQuery can also rewrite compatible queries to use the materialized view which reduces operational upkeep because clients do not need to change their SQL. Enable BigQuery BI Engine and query retail_ops.sales_events with a filter for the last 12 months of partitions is not the best fit because BI Engine is an in memory acceleration layer that does not precompute or incrementally maintain aggregates. You still pay for repeated scans or a large reservation and you do not get the same cost savings and simplicity that a preaggregated result provides. Create a scheduled query that rebuilds a 12 month aggregate summary table every 30 minutes is inefficient and increases maintenance. It introduces staleness between runs and repeatedly recomputes the entire window which drives cost and fails the requirement for near real time results. Create a materialized view on retail_ops.sales_events and configure a partition expiration policy on the base table so only the last 12 months are kept violates the requirement to preserve all historical rows for auditing because an expiration policy would delete older partitions from the base table. When you see frequent aggregate queries that must stay fresh with low latency and cost, think materialized views. If the problem mentions an auditing need, avoid any option that expires or deletes base data.