Google Cloud Professional Cloud Architect Managing Implementation and Reliability Operations Syllabus

Managing Implementation and Reliability Operations syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Managing Implementation and Reliability Operations in Google Cloud Professional Cloud Architect, not a summary of it.

1. 1

   Advising Development and Operations Teams

   4 topics

   • Application development best practices on Google Cloud
     • Twelve-factor and cloud-native principles
   • API design and management
     • Apigee and API Gateway
   • Using Google Cloud SDK, gcloud, and client libraries
   • Microservices and service mesh patterns
     • Cloud Service Mesh and Anthos
2. 2

   Interacting with Google Cloud Programmatically

   4 topics

   • Cloud APIs and authentication
   • Cloud Shell and Cloud SDK workflows
   • Automation with scripting and SDKs
   • Event-driven integration
     • Pub/Sub and Eventarc
     • Cloud Functions and workflows
3. 3

   Monitoring, Logging, and Observability

   4 topics

   • Cloud Monitoring metrics and dashboards
     • Uptime checks and alerting policies
   • Cloud Logging and log routing
     • Log sinks and log-based metrics
   • Cloud Trace, Profiler, and Error Reporting
   • Defining SLOs and error budget policies
4. 4

   Reliability and Scalability Engineering

   4 topics

   • Autoscaling and load balancing strategies
     • Global vs. regional load balancers
   • Managing quotas, limits, and throttling
   • Caching strategies
     • Memorystore and Cloud CDN
   • Handling failure modes and self-healing

Managing Implementation and Reliability Operations flashcards for Google Cloud Professional Cloud Architect

22 of 65 cards from the Managing Implementation and Reliability Operations deck — real questions with worked answers.

1. What is the recommended pattern for handling configuration and secrets in a 12-factor app deployed on Google Cloud?

   Store config in the environment (env vars), and keep secrets out of code by using Secret Manager, injecting them at runtime rather than hardcoding or committing them.

2. In Google Cloud application development, what is the difference between idempotent and non-idempotent operations, and why does it matter for retries?

   An idempotent operation produces the same result no matter how many times it is applied; a non-idempotent one does not. Idempotency lets clients safely retry failed requests without causing duplicate side effects.

3. What is the purpose of exponential backoff with jitter when calling Google Cloud APIs?

   It spaces out retries with progressively longer, randomized delays to avoid overwhelming a recovering service and to prevent many clients from retrying in synchronized 'thundering herd' bursts.

4. What are the four main HTTP methods in a RESTful API and their typical CRUD mappings?

   GET = Read, POST = Create, PUT/PATCH = Update (full/partial), DELETE = Delete.

5. In API design, what is the difference between PUT and PATCH?

   PUT replaces the entire resource with the provided representation (full update), while PATCH applies a partial update to only the specified fields.

6. What is API versioning and what are two common strategies for it?

   Versioning lets an API evolve without breaking existing clients. Common strategies: URI/path versioning (e.g., /v1/resource) and header-based versioning (e.g., Accept header or custom version header).

7. What is Apigee in the Google Cloud ecosystem?

   Apigee is Google Cloud's full-lifecycle API management platform for designing, securing, publishing, monitoring, and monetizing APIs, including features like rate limiting, quotas, and developer portals.

8. What is the difference between authentication and authorization in Cloud APIs?

   Authentication verifies WHO you are (identity); authorization verifies WHAT you are allowed to do (permissions/access). IAM handles authorization once identity is established.

9. Which gcloud command initializes the SDK and sets up the active configuration (account, project, region)?

   gcloud init

10. What is the difference between gcloud, gsutil, and bq command-line tools?

    gcloud manages most Google Cloud resources, gsutil manages Cloud Storage (buckets/objects), and bq runs BigQuery jobs and queries. (gsutil is now largely superseded by 'gcloud storage'.)

11. What are Google Cloud Client Libraries and how do they differ from raw REST/gRPC calls?

    Client Libraries are idiomatic, language-specific SDKs that wrap the underlying REST/gRPC APIs, handling authentication, retries, and serialization so developers write less boilerplate than calling the APIs directly.

12. What is Application Default Credentials (ADC) and how does it find credentials?

    ADC is a strategy client libraries use to automatically find credentials, checking in order: the GOOGLE_APPLICATION_CREDENTIALS env var, the gcloud user credentials, then the attached service account (metadata server) on Google Cloud resources.

13. What is a microservices architecture and one key advantage over a monolith?

    It structures an application as a collection of small, independently deployable services each owning a single business capability. Key advantage: each service can be developed, scaled, and deployed independently.

14. What is a service mesh and what problem does it solve?

    A service mesh is a dedicated infrastructure layer (e.g., Istio/Anthos Service Mesh) that handles service-to-service communication—load balancing, mTLS, traffic routing, retries, and observability—via sidecar proxies, offloading this from application code.

15. In a service mesh like Istio, what is a sidecar proxy?

    A proxy (e.g., Envoy) deployed alongside each service instance that intercepts all inbound/outbound network traffic, enforcing policies, security (mTLS), and collecting telemetry transparently to the app.

16. What is the Circuit Breaker pattern in microservices?

    A resilience pattern that stops sending requests to a failing downstream service after a failure threshold ('opens' the circuit), failing fast and allowing the service to recover before retrying.

17. What is mutual TLS (mTLS) and where is it commonly used in Google Cloud?

    mTLS is two-way TLS where both client and server present and verify certificates, ensuring both authentication and encryption. It is commonly enabled by service meshes (Anthos Service Mesh/Istio) for secure service-to-service traffic.

18. What is a service account in Google Cloud and what is it used for?

    A service account is a special non-human identity used by applications, VMs, or services to authenticate and call Google Cloud APIs, with IAM roles granting it permissions.

19. What is OAuth 2.0 access scope in the context of Cloud APIs?

    A scope defines the specific level of access an OAuth 2.0 token grants to an API (e.g., read-only vs. read-write), limiting what the authenticated identity can do.

20. What is Cloud Shell and what is one notable limitation of its default environment?

    Cloud Shell is a free, browser-based Linux shell with the Cloud SDK pre-installed and a 5 GB persistent home directory. Limitation: the VM and non-home filesystem are ephemeral and reset after about an hour of inactivity (only $HOME persists).

21. How much persistent storage does Cloud Shell provide and what is preserved?

    Cloud Shell provides 5 GB of free persistent disk mounted at your $HOME directory; only files in $HOME survive across sessions.

22. What is a gcloud configuration and why use multiple named configurations?

    A gcloud configuration is a named set of properties (account, project, region/zone). Multiple configurations let you quickly switch contexts between different projects or accounts using 'gcloud config configurations activate'.

See more Managing Implementation and Reliability Operations flashcards →

Planning Managing Implementation and Reliability Operations for Google Cloud Professional Cloud Architect

Managing Implementation and Reliability Operations (Google Cloud Professional Cloud Architect) FAQ