nerdexam
Google

CLOUD-DIGITAL-LEADER · Question #32

There are internal compliance requirements that demand that we do not use any APIs or services that are not backed by SLAs. Which of these are acceptable for us? (Choose two answer)

The correct answer is C. General Availability D. Deprecated, but ensure that the SLA support period is still valid. Google Cloud defines a clear product launch lifecycle. General Availability (GA) is the only stage that comes with a full, formal SLA - services are production-ready, supported, and covered by uptime guarantees. Deprecated services are being phased out, but Google typically…

Governance, Risk, and Compliance

Question

There are internal compliance requirements that demand that we do not use any APIs or services that are not backed by SLAs. Which of these are acceptable for us? (Choose two answer)

Options

  • AAlpha, Beta
  • BEarly Access, Preview
  • CGeneral Availability
  • DDeprecated, but ensure that the SLA support period is still valid.

How the community answered

(27 responses)
  • A
    7% (2)
  • B
    4% (1)
  • C
    89% (24)

Explanation

Google Cloud defines a clear product launch lifecycle. General Availability (GA) is the only stage that comes with a full, formal SLA - services are production-ready, supported, and covered by uptime guarantees. Deprecated services are being phased out, but Google typically provides a defined support and SLA coverage window during the deprecation period, so they remain acceptable as long as you verify that SLA coverage is still active. Alpha and Beta (A) are pre-release stages explicitly excluded from SLAs - they are for testing and feedback only. Early Access and Preview (B) are similarly pre-GA stages that carry no SLA commitments. Using any pre-GA service in a compliance-sensitive environment would violate the stated requirement.

Topics

#SLAs#Product Lifecycle#Service Maturity#Compliance

Community Discussion

No community discussion yet for this question.

Full CLOUD-DIGITAL-LEADER Practice