πŸ‡ΊπŸ‡Έ Google Cloud Professional Cloud Architect Β· subject

Google Cloud Professional Cloud Architect Designing for Security and Compliance Syllabus

The Designing for Security and Compliance syllabus for Google Cloud Professional Cloud Architect in full: 5 chapters, 20 topics and 9 sub-topics, every one listed below, plus 61 Designing for Security and Compliance flashcards with answers.

5Chapters
20Topics
9Sub-topics
61Flashcards

Designing for Security and Compliance syllabus: all 5 chapters

Expand any chapter to see its topics and sub-topics.

  1. Identity and Access Management

    4 topics
    • IAM roles and policy structure
      • Primitive, predefined, and custom roles
      • Principle of least privilege
    • Service accounts and workload identity
      • Workload Identity Federation
      • Service account impersonation
    • Cloud Identity and directory federation
    • IAM Conditions and deny policies
  2. Resource Hierarchy and Organization Controls

    4 topics
    • Organization, folders, and projects
      • Policy inheritance model
    • Organization policy constraints
    • Resource Manager and tagging
    • VPC Service Controls and perimeters
  3. Data Protection and Encryption

    4 topics
    • Encryption at rest and in transit
    • Cloud KMS and key management
      • Customer-managed (CMEK) and customer-supplied (CSEK) keys
      • Cloud HSM and External Key Manager
    • Secret Manager
    • Sensitive Data Protection (DLP)
  4. Network and Application Security

    4 topics
    • Cloud Armor and WAF policies
      • DDoS protection and rate limiting
    • Identity-Aware Proxy and BeyondCorp
    • Private Google Access and Private Service Connect
    • Certificate Manager and TLS
  5. Compliance, Governance, and Threat Detection

    4 topics
    • Security Command Center
      • Threat and vulnerability findings
    • Compliance frameworks and Assured Workloads
    • Audit logging and Access Transparency
    • Penetration testing and shared responsibility

Google Cloud Professional Cloud Architect Designing for Security and Compliance flashcards β€” 61 questions with answers

  1. In Google Cloud IAM, what are the three components of an IAM policy (role binding)?

    A principal (member: user, group, service account, or domain), a role (a collection of permissions), and the resource to which the binding is attached. Optionally an IAM Condition.

  2. What are the three categories of IAM roles in Google Cloud, and how do they differ?

    Basic roles (Owner, Editor, Viewer) β€” broad, legacy, project-wide; Predefined roles β€” granular, Google-managed for specific services; Custom roles β€” user-defined sets of permissions tailored to least privilege.

  3. What is the format of a Google Cloud IAM permission?

    service.resource.verb (e.g., compute.instances.delete or storage.objects.get).

  4. How does IAM policy inheritance work in the Google Cloud resource hierarchy?

    Policies are inherited downward: a policy set at the organization applies to folders, projects, and resources beneath it. The effective policy on a resource is the union of its own policy plus all inherited ancestor policies.

  5. What is the difference between a basic 'Editor' role and the principle of least privilege?

    Editor grants broad write access across most services, violating least privilege. Least privilege favors predefined or custom roles granting only the specific permissions a principal needs.

  6. What is a Google Cloud service account and what two purposes does it serve?

    A special non-human identity used by applications/workloads. It serves as both an identity (a principal that can be granted IAM roles) and a resource (an object others can be granted access to impersonate).

  7. What is the recommended alternative to downloading service account keys for workloads running on Google Cloud?

    Attach a service account directly to the resource (e.g., a VM or GKE workload) and use the metadata server / Application Default Credentials, avoiding long-lived key files.

  8. What is Workload Identity Federation in Google Cloud?

    A mechanism that lets external identities (from AWS, Azure, or any OIDC/SAML provider) impersonate a Google service account using short-lived tokens, eliminating the need for exported service account keys.

  9. What is GKE Workload Identity and why is it preferred?

    It binds a Kubernetes service account to a Google service account, letting pods authenticate to Google APIs without node-level keys. It is the recommended, most secure way for GKE workloads to access Google Cloud services.

  10. What permission/role allows a principal to impersonate a service account by generating short-lived tokens?

    Service Account Token Creator (roles/iam.serviceAccountTokenCreator), which grants the iam.serviceAccounts.getAccessToken permission.

  11. What is Cloud Identity and how does it relate to Google Workspace?

    Cloud Identity is a standalone Identity-as-a-Service (IDaaS) product providing managed user accounts, groups, and device/policy management β€” essentially Google Workspace identity features without the productivity apps.

  12. What tool synchronizes users and groups from an on-premises Active Directory or LDAP to Cloud Identity?

    Google Cloud Directory Sync (GCDS), a one-way sync that provisions identities from the on-prem directory into Cloud Identity/Workspace.

  13. In a federated SSO setup with Cloud Identity, which system acts as the IdP and which as the SP?

    With external federation, the third-party (e.g., Active Directory Federation Services / Okta) is typically the SAML Identity Provider (IdP) and Google acts as the Service Provider (SP), so authentication occurs against the external IdP.

  14. What is an IAM Condition and what is it written in?

    An optional logic expression on a role binding that grants access only when the condition is true. It is written in Common Expression Language (CEL) and can test attributes like resource name, request time, or IP.

  15. What is an IAM deny policy and how does it interact with allow policies?

    A deny policy lists denied permissions for principals; deny rules are evaluated before allow grants. If a request matches a deny rule, access is blocked regardless of any allow binding (deny takes precedence).

  16. Give an example use case for an IAM Condition based on time.

    Granting temporary 'just-in-time' access: a binding with a condition like request.time < timestamp('2026-07-01T00:00:00Z') automatically expires access after that date.

  17. What are the three levels of the Google Cloud resource hierarchy, from top to bottom?

    Organization (root node) β†’ Folders (optional grouping, can nest) β†’ Projects β†’ Resources. The Organization is tied to a Cloud Identity/Workspace domain.

  18. What is the purpose of a Google Cloud project?

    A project is the base-level organizing entity that groups resources, owns billing, enables APIs, and serves as a trust/quota boundary. Every resource belongs to exactly one project.

  19. Why use folders in the resource hierarchy?

    Folders group projects by department, team, or environment, allowing IAM policies and Organization Policy constraints to be applied at the folder level and inherited by all projects within it.

  20. What is an Organization Policy and how does it differ from IAM?

    IAM controls WHO can do WHAT (identity-based permissions). Organization Policy sets centralized constraints on WHAT can be configured on resources (e.g., restrict VM external IPs), applied across the hierarchy regardless of who acts.

Show the other 41 Designing for Security and Compliance flashcards
  1. What are the two main types of Organization Policy constraints?

    List constraints (allow or deny specific values, e.g., allowed locations or service accounts) and Boolean constraints (enforce a true/false rule, e.g., disable serial port access).

  2. Name a commonly used Organization Policy constraint for restricting where resources can be created.

    constraints/gcp.resourceLocations β€” a list constraint that limits resource creation to specified regions/locations, useful for data residency/compliance.

  3. What is Google Cloud Resource Manager?

    The service that programmatically manages the resource hierarchy β€” creating and managing organizations, folders, and projects, and the IAM policies and metadata attached to them.

  4. What are Resource Manager tags and how do they differ from labels?

    Tags are key-value pairs (defined org-wide) that can be referenced in IAM Conditions and Organization Policies for conditional enforcement. Labels are simpler key-value metadata used mainly for organization, billing, and filtering β€” not for policy decisions.

  5. What is VPC Service Controls and what problem does it solve?

    A security feature that defines a service perimeter around Google-managed resources (like Cloud Storage, BigQuery) to mitigate data exfiltration, preventing data from moving outside the perimeter even by authorized identities with valid credentials.

  6. In VPC Service Controls, what is the difference between a perimeter bridge and an access level?

    A perimeter bridge allows controlled communication of projects across two separate perimeters. An access level (from Access Context Manager) defines conditions (IP range, device, identity) under which requests from outside the perimeter are permitted in via ingress rules.

  7. What are ingress and egress rules in a VPC Service Controls perimeter?

    Ingress rules define which external sources/identities may access resources inside the perimeter; egress rules define which outside resources/services principals inside the perimeter may reach. They provide fine-grained boundary control.

  8. By default, is data at rest in Google Cloud encrypted, and with what?

    Yes. All data at rest is automatically encrypted by default using Google-managed encryption keys (AES-256), with no action required by the customer.

  9. Compare GMEK, CMEK, and CSEK for encryption at rest in Google Cloud.

    GMEK (Google-Managed Encryption Keys): default, Google handles keys. CMEK (Customer-Managed): you create/manage keys in Cloud KMS, controlling rotation and access. CSEK (Customer-Supplied): you provide your own raw key material with each API call; Google does not store it.

  10. How is data encrypted in transit within Google Cloud and across the internet?

    In transit, data is protected with TLS. Traffic between Google data centers is encrypted, and traffic to Google APIs uses TLS. Application-layer and ALTS (Application Layer Transport Security) protect internal service-to-service communication.

  11. What is Cloud KMS and what key types can it manage?

    Cloud Key Management Service is a centralized cloud service to create, use, rotate, and destroy cryptographic keys. It supports symmetric keys, asymmetric keys (encryption and signing), and integration with HSM and external key managers.

  12. What is the difference between Cloud KMS software, Cloud HSM, and Cloud EKM protection levels?

    SOFTWARE: keys protected in software. HSM: keys generated and used in FIPS 140-2 Level 3 certified hardware security modules. EKM (External Key Manager): key material stays in a third-party external key manager outside Google.

  13. What is key rotation in Cloud KMS and why does it matter?

    Rotation creates a new key version that becomes primary for new encryption while old versions remain to decrypt existing data. Automatic rotation on a schedule limits the amount of data protected by a single key version, improving security.

  14. What is the hierarchy of objects in Cloud KMS?

    Project β†’ Key Ring (regional grouping of keys) β†’ CryptoKey β†’ CryptoKey Versions. The key ring's location is fixed at creation and determines where keys reside.

  15. What is Secret Manager and what does it store?

    A managed service for storing, versioning, and accessing sensitive data such as API keys, passwords, certificates, and database credentials, with IAM-controlled access and audit logging. Secrets are encrypted at rest.

  16. How does versioning work in Secret Manager?

    Each secret has immutable versions; you reference a specific version number or 'latest'. Versions can be enabled, disabled, or destroyed, allowing controlled rotation and rollback of secret values.

  17. What is Sensitive Data Protection (formerly Cloud DLP) used for?

    To discover, classify, and protect sensitive data (PII like credit card numbers, SSNs, emails). It supports inspection, and de-identification techniques such as masking, tokenization, and redaction.

  18. What are infoTypes in Sensitive Data Protection (DLP)?

    Predefined or custom detectors that identify specific categories of sensitive data (e.g., CREDIT_CARD_NUMBER, US_SOCIAL_SECURITY_NUMBER, EMAIL_ADDRESS) during inspection scans.

  19. What de-identification technique in DLP replaces sensitive values with reversible surrogate tokens?

    Format-preserving tokenization / pseudonymization (cryptographic tokenization, e.g., FPE or deterministic encryption), which can be reversed with the proper key, unlike irreversible redaction or masking.

  20. What is Google Cloud Armor and at which layer does it primarily operate?

    A network security service providing DDoS protection and a Web Application Firewall (WAF) at the edge, integrated with external HTTP(S) load balancers (Layer 7), filtering traffic before it reaches backends.

  21. What pre-configured WAF rules does Cloud Armor offer to address common web attacks?

    Pre-configured rules based on the OWASP ModSecurity Core Rule Set, protecting against SQL injection (SQLi), cross-site scripting (XSS), local/remote file inclusion, and other OWASP Top 10 threats.

  22. In a Cloud Armor security policy, how are rules evaluated?

    Rules are evaluated in ascending priority order (lower number = higher priority). The first matching rule's action (allow/deny/rate-limit) is applied, and evaluation stops.

  23. What is Identity-Aware Proxy (IAP) and what does it secure?

    IAP enforces identity-based access control to applications and VMs without a VPN. It verifies user identity and context at the application layer, granting access only to authorized principals via the IAP-secured Web App User role.

  24. How does IAP embody Google's BeyondCorp / zero-trust model?

    BeyondCorp shifts access controls from the network perimeter to individual users and devices. IAP enforces this by authenticating and authorizing each request based on identity and context, so trust is never granted merely by network location.

  25. What is Private Google Access and what does it enable?

    It allows VM instances that have only internal IP addresses (no external IP) to reach Google APIs and services (like Cloud Storage) through Google's network, rather than over the public internet.

  26. What is Private Service Connect (PSC)?

    A capability that lets you privately consume Google APIs or services published by other VPCs/producers using internal IP endpoints within your VPC, keeping traffic on Google's backbone and avoiding external IPs.

  27. What is Certificate Manager used for in Google Cloud?

    To acquire, store, and deploy TLS/SSL certificates (Google-managed or self-managed) for load balancers and services, supporting large numbers of certificates and wildcard/SAN certs for HTTPS termination.

  28. What is Security Command Center (SCC) and what is its purpose?

    Google Cloud's centralized security and risk management platform that provides asset inventory, vulnerability and misconfiguration detection, threat detection, and compliance monitoring across the organization.

  29. What are the two main service tiers of Security Command Center and how do they differ?

    Standard tier: free, basic findings (Security Health Analytics, asset discovery). Premium/Enterprise tier: paid, adds Event Threat Detection, Container Threat Detection, compliance reporting, attack path simulation, and advanced threat detection.

  30. What is Assured Workloads in Google Cloud?

    A service that lets you create and manage workloads meeting specific compliance and sovereignty requirements (e.g., FedRAMP, CJIS, IL4, data residency) by enforcing controls like personnel/data location and approved products automatically.

  31. What are the four types of Cloud Audit Logs in Google Cloud?

    Admin Activity logs (config changes, always on), Data Access logs (reads/writes of data, mostly off by default), System Event logs (Google system actions), and Policy Denied logs (access blocked by security policy).

  32. Which Cloud Audit Log type is enabled by default and cannot be disabled?

    Admin Activity audit logs β€” they record administrative/config-changing actions, are always written, and incur no charge. Data Access logs, by contrast, must be explicitly enabled (except for BigQuery).

  33. What is Access Transparency and how does it differ from audit logs?

    Access Transparency provides logs of actions taken by Google personnel (e.g., support staff) when they access your content, with justification. It logs Google-side access, whereas Cloud Audit Logs record actions by your own users and services.

  34. What is Access Approval in Google Cloud?

    A control that requires your explicit approval before Google support or engineering personnel can access your data for support purposes, giving customers a gate over administrative access by Google.

  35. Under the shared responsibility model, who is responsible for 'security OF the cloud' vs 'security IN the cloud'?

    Google (the provider) is responsible for security OF the cloud β€” physical infrastructure, hardware, and managed services. The customer is responsible for security IN the cloud β€” data, IAM configuration, access controls, and OS/application patching (varies by service type).

  36. How does the shared responsibility split change between IaaS, PaaS, and SaaS?

    Moving from IaaS to SaaS, the customer's responsibility decreases and Google's increases. In IaaS the customer manages OS/patching; in PaaS Google manages the OS/runtime; in SaaS Google manages nearly everything except data and access.

  37. Does Google require advance notification before you conduct penetration testing on your own Google Cloud resources?

    No. Google does not require you to notify or request permission to pentest your own projects, but you must comply with the Acceptable Use Policy and Terms of Service and only test resources you own.

  38. What is the difference between authentication and authorization in the context of GCP IAM?

    Authentication verifies WHO a principal is (proving identity, e.g., via Cloud Identity or a service account key/token). Authorization determines WHAT that authenticated principal is allowed to do (governed by IAM policies and roles).

  39. What is Access Context Manager and how does it support security perimeters?

    A service that defines and manages access levels based on attributes like IP ranges, device policy, and geolocation. These access levels are consumed by VPC Service Controls and IAP Conditions to enforce context-aware access.

  40. What is the recommended approach to centrally enforce that no Compute Engine VM can have an external/public IP address?

    Apply the Organization Policy constraint constraints/compute.vmExternalIpAccess (a list constraint set to deny all) at the org or folder level, blocking external IP assignment across all projects beneath it.

  41. What is envelope encryption as used by Cloud KMS?

    Data is encrypted with a Data Encryption Key (DEK), and the DEK is itself encrypted (wrapped) by a Key Encryption Key (KEK) stored in Cloud KMS. Only the wrapped DEK is stored alongside the data; the KEK never leaves KMS.

Google Cloud Professional Cloud Architect Designing for Security and Compliance FAQ

What is in the Google Cloud Professional Cloud Architect Designing for Security and Compliance syllabus?

Google Cloud Professional Cloud Architect Designing for Security and Compliance is split into 5 chapters: Identity and Access Management, Resource Hierarchy and Organization Controls, Data Protection and Encryption, Network and Application Security and Compliance, Governance, and Threat Detection. Together they contain 20 topics and 9 sub-topics.

How many chapters are in Google Cloud Professional Cloud Architect Designing for Security and Compliance?

5 chapters, containing 20 topics and 9 sub-topics. The largest chapter is Identity and Access Management, with 4 topics.

Are there flashcards for Google Cloud Professional Cloud Architect Designing for Security and Compliance?

Yes β€” a 61-card Designing for Security and Compliance deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.