Governance and Administration practice questions

Worked examples for Governance and Administration

1. Question 1

   A project team must not be surprised by cloud spend. They want to be notified by email when spending in a particular compartment approaches a threshold they define, and they also want the notification to fire based on where spending is projected to land by the end of the month. Which OCI Cost Management capability should they configure?

   1. A. A budget with alert rules, which tracks spend against a defined monthly amount and can trigger email alerts on actual or forecast spendCorrect answer

      Correct. A budget is set on a compartment (or cost-tracking tag) with a monthly amount, and its alert rules send email when actual or forecast spend crosses the threshold the customer defines.

   2. B. The cost estimator, which monitors live spending and emails the team when the estimate is exceeded

      Misconception that the cost estimator is a monitoring tool. The estimator is a pre-purchase planning tool for modelling the cost of a proposed configuration; it has no visibility into an active tenancy's spend and sends no alerts.

   3. C. A usage report, which automatically halts resource provisioning once the configured spending limit is reached

      Two errors: usage reports are CSV files of consumption detail for analysis, and no OCI budget or report automatically stops resources — alerts notify, they do not enforce a hard stop.

   4. D. Cost analysis, which is the only place a spending threshold can be defined and is evaluated continuously against forecasts

      Confuses analysis with control. Cost analysis provides interactive charts and filtering of accumulated cost data for investigation; thresholds and alerting are the job of budgets, not of the analysis views.

   Explanation

   Budgets in OCI Cost Management are set against a compartment or cost-tracking tag with a specified amount, and each budget can carry alert rules that email recipients when actual or forecast spend crosses a threshold. The cost estimator is a planning tool used before resources exist and cannot observe live spend, usage reports are detail files for analysis rather than an enforcement mechanism, and cost analysis visualizes accrued costs without defining thresholds — and notably, none of these mechanisms stops resources automatically.

2. Question 2

   A developer quickly labels a handful of test block volumes with the key/value pair `owner = jsmith` without involving a tenancy administrator, and no tag namespace is involved. Which characteristic of this kind of tag should the team understand?

   1. A. It is a free-form tag: any user with permission to manage the resource can apply it, and there is no schema or IAM control over its key or valueCorrect answer

      Correct. Free-form tags are simple key/value pairs attached directly to a resource with no namespace, no predefined value list, and no separate policy governing the tag itself — permission to update the resource is enough.

   2. B. It is a defined tag, because every tag applied in OCI is automatically registered into a default tag namespace

      Misconception that defined tags need no explicit namespace. A defined tag exists only because an administrator created a tag namespace and tag key first; tags applied without one remain free-form.

   3. C. It becomes a compartment quota key, so the tenancy can cap how many volumes carry that owner value

      Confuses metadata with enforcement. Tags describe resources; quota policies cap resource consumption in a compartment and are written independently of any tag the developer applies.

   4. D. Tags of this kind cannot be attached to resources at all, because OCI only permits tags that belong to a namespace

      Overstates governance. OCI deliberately supports both models: free-form tags for ad-hoc labelling and defined tags for governed, namespace-backed metadata.

   Explanation

   A tag applied as a plain key/value pair with no tag namespace behind it is a free-form tag: OCI accepts it from anyone who can manage the resource, and it carries no schema, no predefined value list, and no separate IAM control over the key. That convenience is also its weakness — spelling and casing drift, which is why governed reporting relies on defined tags instead. Defined tags require an administrator to create a namespace and key first, tags never act as quota keys, and OCI does support ungoverned free-form tagging alongside the defined model.

3. Question 3

   A cloud administrator opens Cost Analysis in the Console to investigate why last month's bill rose sharply. Which statement best describes what Cost Analysis is for?

   1. A. It enforces spending limits by blocking new resource creation in compartments that exceeded their allocation

      Confuses analysis with enforcement, and misattributes enforcement to Cost Management at all. Spending controls in OCI are advisory alerts on budgets; cost analysis is purely a visualization and investigation tool.

   2. B. It is the mechanism for setting monthly spending thresholds and configuring who receives email when they are crossed

      Describes budgets and their alert rules. Thresholds and notification recipients are configured on a budget; cost analysis defines no thresholds and sends no notifications.

   3. C. It predicts the cost of a workload that has not yet been deployed, based on the shapes the administrator selects

      Describes the cost estimator, a pre-purchase planning tool. Cost Analysis works from costs the tenancy has already accrued, not hypothetical configurations.

   4. D. It provides interactive charts and filtering of accrued costs — for example by compartment, service, or tag — so spending trends and drivers can be identifiedCorrect answer

      Correct. Cost Analysis visualizes the tenancy's accrued costs with grouping and filtering (by service, compartment, tag, and time), which is exactly how an administrator isolates what drove an increase.

   Explanation

   Cost Analysis is the investigative view within OCI Cost Management: it renders accrued costs as interactive charts that can be grouped and filtered by dimensions such as service, compartment, and cost-tracking tag over a chosen period, letting an administrator pinpoint what drove a change. It neither blocks resource creation, models undeployed workloads (that is the cost estimator), nor defines spending thresholds and alert recipients (that is a budget).

4. Question 4

   Which statement best describes the purpose of the Oracle Support Rewards program for a customer who is both an Oracle technology support customer and an OCI consumer?

   1. A. It reduces the published per-hour rate of OCI compute services once the customer opens a support ticket

      Confuses Support Rewards with a service rate discount. Rewards do not change OCI service rates, and they have nothing to do with filing support requests.

   2. B. It converts unused Universal Credits at the end of a term into cash refunded to the customer

      Misconception that Support Rewards is a refund mechanism for expiring credits. Rewards accrue from OCI consumption and are applied to support bills; they are not a cash-back scheme for unspent commitments.

   3. C. It earns the customer rewards based on their OCI consumption, which can then be applied to reduce their Oracle technology software support billCorrect answer

      Correct. Support Rewards accrue as the customer spends on OCI and are redeemed against the customer's Oracle technology (on-premises software) support invoice — the program's defining purpose.

   4. D. It grants free Oracle Database licenses for OCI, removing the need to bring existing licenses

      Confuses Support Rewards with licensing. Licensing options are BYOL versus license-included; Support Rewards affects the support bill and grants no licenses.

   Explanation

   Oracle Support Rewards ties two spends together: as a customer consumes OCI, they accrue rewards that can be redeemed to lower their Oracle technology software support bill, giving an incentive to migrate on-premises workloads to OCI. It does not alter OCI service rates, is not a cash refund for unspent Universal Credits, and confers no software licenses — licensing is handled separately through BYOL or license-included pricing.

5. Question 5

   An organization is confident it will spend a predictable, substantial amount on OCI over the next year and wants lower unit rates than list price, while still keeping the freedom to consume whichever OCI services it needs as its projects evolve. Which OCI pricing model best fits this requirement?

   1. A. Pay-as-you-go, because per-use billing automatically reduces unit rates once monthly consumption grows

      Misconception that pay-as-you-go rates fall automatically with volume. Pay-as-you-go bills at list rates for what is consumed with no commitment and no committed-spend discount; discounted rates come from a spend commitment, not from usage growth.

   2. B. Annual Universal Credits, because a committed annual spend earns discounted rates and the credits can be drawn down against any eligible OCI serviceCorrect answer

      Correct. Annual Universal Credits are a committed-spend model: the customer commits to an amount for the term in exchange for rates below pay-as-you-go, and the credits are 'universal' — consumable across eligible OCI services and regions rather than earmarked per service.

   3. C. Bring Your Own License, because reusing existing licenses is the only way to obtain a rate below list price

      Misconception that BYOL is a general-purpose discount mechanism. BYOL applies only where the customer already owns eligible on-premises Oracle licenses and reduces the license component of specific services; it does not provide a cross-service committed-spend discount.

   4. D. Annual Universal Credits, but the committed amount must be allocated to a single service family chosen at the start of the term

      Misconception that committed credits lock the customer to one service. The word 'universal' signals the opposite: the credits are not earmarked to a single service family and may be spent across eligible services.

   Explanation

   OCI offers pay-as-you-go (no commitment, billed for what is used at list rates) and committed-spend models. Annual Universal Credits trade an up-front spend commitment for discounted rates while leaving consumption flexible across eligible OCI services, which is exactly the stated need. Pay-as-you-go does not grant a commitment discount, BYOL only reduces license costs for services where the customer already owns eligible Oracle licenses, and the credits are deliberately not restricted to one service family.

6. Question 6

   A startup is beginning a proof of concept on OCI. It cannot predict how much capacity it will need, may abandon the project after a month, and is unwilling to sign any spending commitment. Which characteristics accurately describe the pay-as-you-go pricing model for this situation? (Select TWO.)

   1. A. Resources are billed for what is actually consumed, with no minimum spend commitment required up frontCorrect answer

      Correct. Pay-as-you-go is defined by consumption-based billing with no commitment, which is why it suits unpredictable or short-lived workloads.

   2. B. The startup can start and stop services at will, paying only for the period the resources were provisioned and usedCorrect answer

      Correct. Because billing follows consumption rather than a term commitment, the customer is free to provision and deprovision as needs change without owing for unused capacity.

   3. C. An annual spending commitment must be signed before any pay-as-you-go resource can be provisioned

      Directly inverts the model. A commitment is the defining feature of Annual Universal Credits, not of pay-as-you-go, whose entire premise is the absence of a commitment.

   4. D. Pay-as-you-go rates are lower than committed-spend rates because no contract administration is involved

      Reverses the discount direction. Committing to spend is what earns rates below pay-as-you-go; the flexibility of pay-as-you-go is paid for with list-price rates.

   5. E. Unused capacity from one month is banked and automatically carried forward as credit into the next month

      Imports a credit-drawdown notion that does not apply. Pay-as-you-go bills for actual usage each period; there is no pool of prepaid capacity to carry forward.

   Explanation

   Pay-as-you-go is the commitment-free OCI pricing model: customers are billed for the resources they actually consume and can provision or release capacity freely, which matches an unpredictable proof of concept. Claims that it requires an annual commitment invert the model, claims that its rates undercut committed spend reverse the discount direction (commitment is what buys the lower rate), and the idea of banking unused capacity belongs to prepaid credit models rather than to per-use billing.

7. Question 7

   A tenancy administrator wants to stop a development team from consuming more than a small share of the tenancy's available compute capacity, while leaving the production compartment unrestricted. Which statement correctly describes the relationship between compartment quotas and service limits in OCI?

   1. A. Setting a compartment quota above the service limit for a resource raises the effective ceiling for that compartment

      Assumes a quota can override an Oracle-set limit. A quota only restricts consumption within the tenancy's existing allowance; it can never grant capacity beyond the service limit, which remains the hard ceiling.

   2. B. Compartment quotas are set by Oracle per compartment, and the administrator raises or lowers service limits directly in the tenancy to control the development team

      Inverts ownership of both controls. Oracle sets service limits, not compartment quotas; quotas are written by the tenant, and service limits cannot simply be edited by the administrator — an increase must be requested from Oracle.

   3. C. Service limits are set by Oracle for the tenancy in a region, and the administrator writes compartment quota policies to cap consumption inside a compartment at or below those limitsCorrect answer

      Correct. Service limits are Oracle-set ceilings applied per tenancy and region; compartment quotas are tenant-authored policy statements that restrict how much of that allowance a given compartment may consume, which is exactly the control needed here.

   4. D. Compartment quotas and service limits are the same mechanism under two names, so configuring either one produces an identical tenancy-wide effect

      Conflates the two controls. They differ in who sets them and in scope: service limits are Oracle-set and apply to the tenancy in a region, while quotas are tenant-set and apply to an individual compartment, so a quota on the dev compartment leaves production untouched.

   Explanation

   Service limits are the ceilings Oracle applies to a tenancy for a given resource in a region, and raising one requires a request to Oracle rather than a self-service edit. Compartment quotas are policy statements the tenant writes to restrict how much of that Oracle-granted allowance a particular compartment may consume, which is why a quota can target the development compartment alone. Because a quota only subdivides an existing allowance, it can never lift a compartment above its service limit, and the two are not interchangeable names for one tenancy-wide control.

8. Question 8

   A new OCI customer signs up for paid cloud services and asks what technical support they are entitled to and how they will engage it. Which statement best describes Oracle's support model for OCI?

   1. A. Technical support must be purchased separately for each paid cloud service before any service request can be filed

      Misconception that OCI support is an à-la-carte add-on per service. Oracle includes technical support with paid OCI subscriptions rather than selling it per service as a prerequisite to filing a request.

   2. B. Support entitlement is derived from compartment quotas, so raising a quota also raises the customer's support level

      Confuses two unrelated controls. Quotas cap resource consumption within a compartment and have no bearing on support entitlement or service request handling.

   3. C. Technical support is included with paid OCI subscriptions, and customers open service requests — including requests to raise a service limit — through the support channelCorrect answer

      Correct. Paid OCI subscriptions include Oracle technical support, and the service request mechanism is the documented route for both technical issues and Oracle-side actions such as service limit increases.

   4. D. Always Free resources carry the same production support commitments as paid subscriptions, since both run on the same infrastructure

      Misconception that shared infrastructure implies identical entitlement. Always Free resources are intended for learning and light workloads and do not carry the same support and service commitments as paid subscriptions.

   Explanation

   Oracle includes technical support with paid OCI subscriptions, and the service request is the customer's channel into it — used both for technical problems and for Oracle-side administrative actions such as requesting a service limit increase. Support is therefore not a separately purchased prerequisite per service, and it is unrelated to compartment quotas, which only govern how much of a resource may be consumed in a compartment. Always Free resources, despite running on the same platform, are positioned for learning and light use and do not carry the commitments that come with a paid subscription.