Home Microsoft Exams Google Cloud Exams

Loading page

Curious about new developments and updates? Follow our social media.

Get a free certification question every week.

Microsoft Exams

AZ-104 Administrator
AZ-204 Developer
AZ-900 Fundamentals
All Microsoft Exams

Google Cloud Exams

Associate Data Practitioner
All Google Cloud Exams

Terms Privacy Cookies About Pricing

© 2026 StudyCerts. All rights reserved.

StudyCerts is an independent service and is not affiliated with, endorsed by, or sponsored by any certification body or cloud provider.

Loading page

Home
Google Cloud Exams
Professional Cloud Data Engineer
Mapping current and future business requirements to the architecture
An enterprise is modernizing its enterprise data warehouse b…

Professional Cloud Data Engineer

professional-cloud-data-engineer

Advanced

Prepare and test your skills

Description
Sample Question
Free Trial
Practice Test

Advanced

Prepare and test your skills

Description
Sample Question
Free Trial
Practice Test

Bigquery Schema Evolution Facade Views Compatibility

Section: Mapping current and future business requirements to the architecture

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

...

...

...

...

...

Explanations

...

View source documentation

Related questions

Keep the momentum going with these hand-picked practice scenarios

AdvancedProfessional Cloud Data Engineer

A SaaS organization is redesigning its analytics platform on Google Cloud to handle a projected tenfold increase in tenant onboarding and raw data volume. Currently, ingestion workloads, storage, and customer-facing analytical queries share resources in a monolithic project, leading to severe compute contention, complex schema maintenance, and quota bottlenecks. You need to design a scalable, modular architecture that leverages BigQuery's separation of storage and compute to isolate compute resource allocation across tenant tiers while allowing storage and analytical pipelines to scale independently. Which architectural approach should you recommend?

Mapping current and future business requirements to the architecture

AdvancedProfessional Cloud Data Engineer

A financial services organization is building a decentralized data mesh architecture on Google Cloud. Multiple domain teams need to expose curated analytical data products to downstream business analysts across the enterprise. The enterprise architecture board has defined the following technical and regulatory constraints: Downstream business analysts must query aggregated business metrics and sanitized virtual tables without having direct read permissions to the underlying sensitive base datasets. The security and compliance teams require minimal administrative overhead and must avoid managing individual view authorizations as dozens of new analytical views are published. Data domain infrastructure deployments must prevent configuration drift using infrastructure as code (IaC) templates. Which technical requirement and access pattern should the data engineering team implement to satisfy these business objectives?

Mapping current and future business requirements to the architecture

AdvancedProfessional Cloud Data Engineer

Your organization stores customer transaction data in a centralized BigQuery table named sales.transactions. You need to securely share this table with three distinct user groups while enforcing the principle of least privilege: Finance Auditors: Must be able to query all rows and view sensitive payment identifiers (such as credit card numbers) in cleartext. Business Analysts: Must be able to query all rows, but sensitive payment identifiers must be dynamically masked (e.g., using a masking rule or hash) so that existing queries continue to run without exposing cleartext data. Regional Sales Managers: Must be restricted to querying only rows where region = 'EMEA', and payment identifiers must be masked. How should you configure access controls and data policies in Google Cloud to achieve these requirements?

Defining rules to share data

AdvancedProfessional Cloud Data Engineer

Your data engineering team manages cloud data infrastructure—including BigQuery datasets, Cloud Storage buckets, and Dataflow pipelines—across dev and prod environments on Google Cloud. You need to implement a continuous integration and continuous deployment (CI/CD) GitOps workflow using Terraform and Cloud Build that meets the following requirements: Provide a central, collaborative, and version-controlled mechanism for Terraform state management that prevents concurrency conflicts and state corruption. Automatically validate configurations and generate plan previews on proposed code changes before merging into environment branches. Enforce a strict multi-environment promotion sequence where changes are automatically applied only upon merging into the target environment branch. How should you structure your Terraform configuration, state storage, and Cloud Build triggers?

CI/CD (Continuous Integration and Continuous Deployment)

AdvancedProfessional Cloud Data Engineer

A financial services institution is architecting a centralized enterprise data platform on Google Cloud to support mission-critical risk analytics and regulatory reporting. The data platform must satisfy the following technical and governance requirements: Provide a 99.99% availability Service Level Agreement (SLA) for core query processing. Enforce advanced security and compliance controls, including Cloud External Key Manager (Cloud EKM) integration and multi-region disaster recovery with automated data replication failover. Support autoscaling compute capacity with baseline workload predictability by leveraging 3-year Committed Use Discounts (CUDs). Provide cross-project reservation sharing and centralized workload management across multiple business units. Which BigQuery Edition and capacity configuration should you select to meet these requirements?

Capacity management (e.g., BigQuery Editions and reservations)

AdvancedProfessional Cloud Security Engineer

A security engineer is preparing to remove several broad IAM roles, including roles/editor, from a production project to enforce least privilege across automated workloads. Before applying the updated allow policy, the engineer must validate that the change will not disrupt production services by evaluating the impact against recent historical API access attempts across the project and its child resources. During an initial command-line test replay, several permissions evaluated to an access state of UNKNOWN_INFO_DENIED with an error indicating missing permissions to retrieve IAM policies. Which tool should the engineer use, and how should they resolve the evaluation errors?

Applying Policy Intelligence.

Want more questions like this?

Get a free certification question every week.

Last updated August 27, 2026

Are you ready for the Professional Cloud Data Engineer?

50 questions in the full practice test

More Mapping current and future business requirements to the architecture practice questions

Get a free certification question with a full explanation every week.

Professional Cloud Data Engineer

Provider: Google Cloud
Passing score: 70%
Questions: 50
Duration: 90 minutes

Other sections in this exam

Designing data processing systems
Ingesting and processing the data
Storing the data
Preparing and using data for analysis
Maintaining and automating data workloads

Ask Scout

Still curious? Scout, our AI tutor, can explain this concept further and answer your follow-up questions.

An enterprise is modernizing its enterprise data warehouse by migrating workloads to Google Cloud BigQuery. During the migration lifecycle, the data engineering team needs to evolve several core dataset schemas, implement table optimizations such as partitioning and clustering, and restructure underlying tables to support emerging analytics use cases.

However, numerous downstream business intelligence (BI) dashboards, reporting applications, and automated query jobs are already actively reading from the existing table structures. The business requires that underlying schema refactoring and performance optimizations occur without causing operational disruption or requiring immediate query rewrites across downstream consumers.

Which architectural pattern should the data engineering team implement to satisfy these requirements?

Re-architect the data pipelines into an Extract-Transform-Load (ETL) pattern outside of BigQuery to transform data prior to ingestion.

Migrate all downstream BI consumers back to querying the legacy on-premises warehouse until physical BigQuery table refactoring is complete.

Execute procedural DDL scripts during off-peak maintenance windows to alter base table columns and force schema updates directly.

Create facade views in BigQuery on top of the underlying physical tables to abstract structural changes from downstream consumers.

Re-architect the data pipelines into an Extract-Transform-Load (ETL) pattern outside of BigQuery to transform data prior to ingestion.

Migrate all downstream BI consumers back to querying the legacy on-premises warehouse until physical BigQuery table refactoring is complete.

Execute procedural DDL scripts during off-peak maintenance windows to alter base table columns and force schema updates directly.

Create facade views in BigQuery on top of the underlying physical tables to abstract structural changes from downstream consumers.

What BigQuery Facade Views Are

Facade views are logical SQL views created on top of base storage tables in BigQuery that implement the classic facade design pattern. They present a stable, decoupled logical schema to downstream analytical tools while abstracting the underlying physical tables and storage complexity.

How It Meets the Requirements

Ensures backward compatibility: Downstream reporting tools and SQL queries reference the logical facade view schema rather than the physical table. If underlying columns are renamed, split, or restructured, the view definition can project and alias fields to maintain the exact legacy contract.
Minimizes operational disruption: Physical base tables can be refactored, split, merged, partitioned, or clustered in the background without modifying existing client queries or interrupting active business intelligence dashboards.
Enables continuous architectural evolution: Data engineering teams can iteratively evolve data models and introduce new optimization techniques while maintaining an undisturbed abstraction layer for downstream users.

Key Advantages and Capabilities

Zero-downtime schema evolution: Modifies underlying table structures without forcing simultaneous updates to client-side code.
Decoupled data modeling: Separates physical storage optimization (like partitioning and clustering) from logical presentation.
Granular security and governance: Provides an additional security boundary where column-level filtering or masking can be applied before exposing data to specific consumer groups.
Simplified migration path: Allows upstream ingestion pipelines and downstream consumption tools to migrate and evolve at independent cadences.

Why This Is Optimal

Implementing facade views establishes an abstraction boundary between physical storage and downstream consumption interfaces. This directly solves the challenge of evolving warehouse schemas in place while ensuring business continuity for analytics consumers.