Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Gauge your current knowledge
Gauge your current knowledge
Understanding where data lives is essential for following the law. Data residency refers to the physical geographic location where data is stored, while data locality focuses on keeping data close to its users or processing site. Data sovereignty means that data is subject to the legal jurisdiction of the country where it physically resides. Architects must distinguish between these concepts to ensure sensitive information remains compliant with international government mandates.
Google Cloud Assured Workloads helps organizations manage these requirements automatically by creating secure boundaries that follow specific rules like GDPR in Europe or FedRAMP in the United States. This tool applies predefined security packages to specific folders or projects, including regional data boundaries that restrict data to specific geographic areas, personnel access controls that limit which Google employees can see the data, and violation monitoring that alerts administrators when a setting breaks a compliance rule.
The Organization Policy Service enforces these boundaries through the gcp.resourceLocations constraint, which restricts the creation of new resources to approved regions only. By locking down these settings, companies prevent data from accidentally moving across borders into unauthorized jurisdictions. This technical control is essential for meeting strict requirements of local legislation and data ownership rules.
Compliance is a shared responsibility where Google protects the physical hardware while the customer secures the data itself. Cloud Data Loss Prevention (DLP) helps identify and classify sensitive information such as health records or data involving children's privacy. Using encryption through Cloud Key Management Service (KMS) ensures that data remains private and owned by the organization, even when stored in a provider's data center.
Google Cloud helps organizations meet global privacy regulations by aligning its infrastructure with international standards. Google undergoes regular third-party audits for certifications like ISO/IEC 27018, which specifically focuses on cloud privacy. These frameworks help businesses manage data residency and sovereignty requirements effectively.
For industries like healthcare and finance, Google provides tools to support regulations such as HIPAA and FFIEC. Using Sensitive Data Protection services helps automatically discover and classify sensitive information. Implementing these technical controls is essential for safeguarding personal health records and children's privacy.
De-identification and tokenization protect sensitive data while keeping it useful for analysis. De-identification removes or masks identifying information from a dataset, while tokenization replaces sensitive data with non-sensitive substitutes called tokens. Data Clean Rooms allow multiple parties to analyze data without revealing underlying raw details, which is useful for collaborative analytics while maintaining privacy.
Google uses a Zero Trust security model where access is granted based on the user's identity and the context of their request. Binary Authorization for Borg ensures that only reviewed and approved software can access sensitive customer data. This multi-layered approach prevents unauthorized access and reduces the risk of insider threats.
A dedicated Privacy Team operates independently to review product designs and code for privacy risks. All employees must follow a Code of Conduct and complete regular training on handling customer data safely. This internal culture ensures that privacy is built into every product from the beginning.
Data ownership requires an organization to identify who is responsible for specific data assets. In Google Cloud, tools like Data Catalog and Tag Engine automatically assign business metadata such as the owner's name and the data's sensitivity level. Automated tagging ensures that all sensitive information is labeled correctly, which helps the organization maintain authority over its data and meet legal requirements.
Data sovereignty and data residency refer to legal requirements that dictate where data can be stored and processed. Organizations use the Organization Policy Service to define allowed storage regions and the Access Context Manager to limit access based on a user's physical location. The Report Engine detects if data is stored or accessed outside of approved regions, comparing policies against actual data locations to find discrepancies that could lead to compliance violations.
The shared responsibility model defines the division of security tasks between the cloud provider and the customer. While Google Cloud maintains high-level certifications like PCI DSS and ISO/IEC 27701, the customer is responsible for configuring their specific environment securely. The level of customer responsibility often depends on the service type used, such as whether they are managing their own virtual machines or using fully managed databases.
Data classification organizes data into categories based on sensitivity levels, such as Personally Identifiable Information (PII). Using Sensitive Data Protection, organizations can automatically scan for credit card numbers or social security numbers to apply correct security tags. These tags then trigger specific access controls, such as column-level security in a database, to ensure only authorized personnel can view sensitive details.
Managing the data lifecycle involves planning how long data is kept and how it is destroyed when no longer needed. Organizations set retention periods and expiration actions to automatically archive or purge data after a certain number of days. Automating these tasks reduces the risk of keeping sensitive data longer than legally allowed. Common lifecycle actions include purging (permanently deleting data after its retention period ends), archiving (moving older data to low-cost storage for long-term keeping), and soft-deletion (holding data for a short period before final removal to allow recovery).
StudyCerts
StudyCerts