In Oracle NoSQL Database Cloud Service, performance and cost are managed by provisioning capacity for each table. This capacity is defined by three main limits: Read Units, Write Units, and Storage capacity. The question specifically asks for rate limits, which govern the throughput of operations. These are directly controlled by setting the number of Read Units and Write Units. A Read Unit corresponds to one eventually consistent read per second for a row up to 1 KB, while a Write Unit corresponds to one write per second for a row up to 1 KB. These two dimensions, read and write throughput, are the primary rate limits users configure.

A. Storage capacity is a limit based on size (GB), not a rate or throughput limit. Network bandwidth is managed by the service, not a user-configured table limit.

C. CPU and memory are underlying infrastructure resources managed by the Oracle Cloud service, not dimensions directly provisioned by the user on a per-table basis.

D. The number of indexes is a structural limit, not a rate limit. Query complexity influences the consumption of Read Units but is not a provisioned limit itself.

1. Oracle Cloud Infrastructure Documentation, "Estimating Capacity for Oracle NoSQL Database Cloud Service":

Section: "Provisioning Capacity": "You provision capacity for Oracle NoSQL Database Cloud Service tables by specifying throughput and storage values. Throughput capacity is specified in terms of Read Units and Write Units."

Section: "Read and Write Units": This section explicitly defines Read Units and Write Units as the measures for read and write throughput, respectively.

2. Oracle Cloud Infrastructure Documentation, "Service and Table Limits for Oracle NoSQL Database Cloud Service":

Section: "Table Limits": This section lists the default and maximum limits for "Max Read Units" and "Max Write Units" per table, reinforcing that these are the fundamental, configurable throughput dimensions. It also lists "Max Storage (GB)" separately, distinguishing it from the rate limits.