The primary function of the Oracle NoSQL Database Cloud Service SDK (Software Development Kit) is to provide a high-level, language-specific programming interface for developers. It simplifies application development by abstracting the complexities of the underlying REST API. The SDK handles low-level details such as request signing for authentication, data serialization/deserialization, and retry logic for transient errors. This allows developers to perform data (CRUD) and table (DDL) operations using familiar programming constructs in languages like Java, Python, or Go, rather than manually constructing and managing raw HTTP requests.

A. Physical storage layout is an internal detail managed entirely by the Oracle Cloud service, not controlled by a client-side SDK.

C. Underlying infrastructure (e.g., servers, storage) is managed through Oracle Cloud Infrastructure (OCI) control plane tools like the Console, CLI, or Terraform, not the data-focused NoSQL SDK.

D. Network security policies are configured at the OCI platform level using services like Identity and Access Management (IAM) and Virtual Cloud Network (VCN), not via the application SDK.

1. Oracle Cloud Infrastructure Documentation, "About the Oracle NoSQL Database Cloud SDKs": "The Oracle NoSQL Database Cloud SDKs provide interfaces for developing applications that use the Oracle NoSQL Database Cloud Service. The SDKs are built on top of the Oracle Cloud Infrastructure SDKs and provide a higher-level interface to the Oracle NoSQL Database Cloud Service." This source confirms the SDK's role as a high-level programming interface for application development.

2. Oracle NoSQL Database Cloud Service Developer Guide, "Overview of APIs": "The Oracle NoSQL SDKs provide a higher-level, easy-to-use API that lets you develop applications. The SDKs are built on top of the Oracle Cloud Infrastructure (OCI) SDKs and use the OCI infrastructure for authentication and request signing. The SDKs simplify the process of writing code to work with the service by providing pre-written code that handles tasks such as request signing, retries, and error handling." This directly supports the abstraction of low-level details (Option B) and refutes the management of infrastructure or security (Options C and D).