Google Cloud Professional Cloud Architect Analyzing and Optimizing Technical and Business Processes Flashcards

24 sample cards from the Analyzing and Optimizing Technical and Business Processes deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. Differentiate standard, normal, and emergency changes in ITIL change management.

   Standard change: pre-approved, low-risk, routine (no CAB review needed). Normal change: requires assessment and approval (often via a Change Advisory Board). Emergency change: urgent fix for a critical issue, expedited approval, documented retroactively.

2. What is a Change Advisory Board (CAB)?

   A group of stakeholders that reviews, assesses risk for, and approves or rejects proposed normal/significant changes, advising on prioritization and scheduling to protect production stability.

3. What is capacity management and what is its goal?

   The process of ensuring IT resources (compute, storage, network) are sufficient to meet current and future demand at acceptable cost and performance — balancing under-provisioning (outages) against over-provisioning (wasted spend).

4. Distinguish demand management from capacity management.

   Capacity management ensures supply of resources meets demand. Demand management influences or shapes the demand itself — e.g., via rate limiting, scheduling batch jobs off-peak, pricing/quotas, or smoothing usage spikes to fit available capacity.

5. What is the difference between vertical and horizontal scaling?

   Vertical scaling (scale up) adds more power (CPU/RAM) to a single machine. Horizontal scaling (scale out) adds more machines/instances and distributes load across them. Horizontal scaling is generally more elastic and fault-tolerant.

6. What is a RACI matrix and what do its letters mean?

   A responsibility-assignment chart mapping roles to tasks. R = Responsible (does the work), A = Accountable (ultimately answerable, one per task), C = Consulted (provides input), I = Informed (kept updated).

7. What is skill mapping (skills matrix) and why is it used?

   A grid mapping team members against required skills/competency levels. It is used to identify capability gaps, plan training and hiring, assign work appropriately, and reduce single points of knowledge (bus factor).

8. What is stakeholder management, and what tool helps prioritize stakeholders?

   The process of identifying, analyzing, and engaging people affected by or influencing a project. A power/interest grid (interest vs. influence matrix) helps prioritize: manage closely (high power/high interest), keep satisfied, keep informed, or monitor.

9. What is a communication plan and what key questions does it answer?

   A document defining how project/operational information is shared. It answers: who needs information, what information, how often (frequency), through which channel/format, and who is responsible for delivering it.

10. What is the difference between governance and management in IT decision-making?

    Governance sets direction, policies, and accountability — deciding what should be done and who decides (evaluate, direct, monitor). Management executes within that framework — planning, building, running, and monitoring day-to-day operations.

11. Name common organizational decision-making models, including consensus and consent.

    Autocratic (single decider), consultative (decider seeks input), consensus (all must agree), consent (proceed unless someone has a reasoned objection), democratic/majority vote, and delegated (a designated owner decides). Consent is faster than consensus because it requires no objections rather than full agreement.

12. What is DevOps, in cultural terms?

    A culture and set of practices that break down silos between development and operations, emphasizing shared ownership, automation, continuous delivery, fast feedback, and collaboration to deliver software reliably and quickly.

13. What is SRE (Site Reliability Engineering) and how does it relate to DevOps?

    SRE is Google's prescriptive implementation of DevOps principles, applying software engineering to operations. It is often summarized as 'SRE implements DevOps' (class implements interface), adding concrete practices like SLOs, error budgets, and toil reduction.

14. Define SLI, SLO, and SLA.

    SLI (Service Level Indicator): a measured metric of service behavior (e.g., latency, availability %). SLO (Service Level Objective): an internal target value/range for an SLI (e.g., 99.9% availability). SLA (Service Level Agreement): an external contract with customers including consequences/penalties for missing targets.

15. What is an error budget in SRE and how is it used?

    The allowed amount of unreliability = 100% minus the SLO (e.g., a 99.9% SLO gives a 0.1% error budget). It is 'spent' by outages; while budget remains, teams can ship features freely, but if it is exhausted, releases freeze to focus on reliability.

16. What is 'toil' in SRE, and why reduce it?

    Toil is manual, repetitive, automatable, tactical operational work that scales linearly with service size and provides no enduring value. SRE caps and reduces toil through automation so engineers can focus on engineering improvements.

17. In Google Cloud, what is a billing account and how does it relate to projects?

    A billing account is a cloud-level resource that defines who pays and is linked to a Google payments profile. One billing account can be linked to many projects; every project that uses paid resources must be associated with exactly one active billing account.

18. What are budgets and budget alerts in Google Cloud Billing?

    A budget sets a monetary spending threshold (for a billing account or scoped to projects/services). Budget alerts send notifications (e.g., email or Pub/Sub) when actual or forecasted spend crosses configured percentage thresholds (e.g., 50%, 90%, 100%). Note: alerts notify but do not automatically cap spending.

19. How can budget alerts be used to automatically cap or stop spending in Google Cloud?

    By configuring the budget to publish alerts to a Pub/Sub topic, then triggering a Cloud Function that takes action — for example, disabling the billing account on the project — since budgets alone only notify and never auto-stop charges.

20. What are labels in Google Cloud and how do they support cost allocation?

    Labels are key-value pairs attached to resources (e.g., env=prod, team=payments, cost-center=123). Exported to billing data (e.g., BigQuery), they let you break down and allocate costs by team, environment, application, or cost center.

21. What is the difference between labels and the project/folder hierarchy for cost allocation?

    The resource hierarchy (Organization → Folders → Projects) groups resources structurally and is a natural cost-allocation boundary (per-project billing). Labels add flexible, cross-cutting cross-project dimensions (team, app, env) for finer-grained reporting that the hierarchy alone cannot express.

22. What is FinOps?

    A cultural and operational practice (Cloud Financial Operations) that brings financial accountability to variable cloud spend, uniting finance, engineering, and business teams to make data-driven trade-offs between cost, speed, and quality. Its phases are Inform, Optimize, and Operate.

23. What is the difference between showback and chargeback in cloud cost management?

    Showback reports each team/department its cloud usage and cost for visibility and awareness, without billing them. Chargeback actually allocates and bills those costs back to the consuming team's budget, creating direct financial accountability.

24. What is continuous process optimization, and what improvement cycle underpins it?

    The ongoing practice of measuring, analyzing, and incrementally improving processes rather than one-time fixes. It is commonly driven by the PDCA (Plan-Do-Check-Act / Deming) cycle and Kaizen — using metrics and feedback loops to drive iterative improvement.

What this deck covers

Analyzing and Optimizing Technical and Business Processes flashcards FAQ