Free 1Z0-931-26 Practice Test Questions and Answers (2026)

To authenticate API calls made through Oracle Cloud Infrastructure (OCI) Software Development Kits (SDKs), Command Line Interface (CLI), or REST APIs, users must configure an API signing key pair (an RSA public/private key pair in PEM format). The public key component of this key pair is added directly through the OCI Console under user profile administration. To perform this setup, an administrator or user navigates to the Identity & Access Management service in the OCI Console, selects the Users panel, opens the specific user's detail page, navigates to the API Keys section, and selects "Add Public Key" (or Add API Key) to upload or paste the key.

A: User authentication keys for OCI API access are managed centrally under OCI Identity and Access Management (IAM), not within the Autonomous Database Console. B: OCI requires asymmetric key pairs (API signing keys) to authenticate and authorize CLI, SDK, and REST API service calls. C: API keys can be conveniently added, managed, and deleted directly through the graphical OCI Console interface under IAM user details.

Oracle Cloud Infrastructure Documentation, Identity and Access Management, Section: "Managing User Credentials - How to Add an API Signing Key".

Oracle Cloud Infrastructure Security Guide, User Authentication and API Key Provisioning, Section: "API Signing Keys".

When planning and instituting access control policy and network infrastructure for an Autonomous Database Dedicated environment, Oracle best practice guidelines recommend creating at least two of each core resource type: subnets, compartments, and user groups. Having at least two compartments enables strict isolation between network infrastructure management and database workload management. Having at least two private subnets across availability or fault domains ensures network redundancy and proper segregation of client applications. Finally, establishing at least two distinct user groups (such as Fleet Administrators and Database Administrators) enforces the security principle of least privilege and separation of duties across cloud infrastructure roles and database operations within the dedicated cloud deployment.

Option A: Oracle documentation does not restrict dedicated environments to a single subnet or compartment, and segregating resources across multiple compartments is strongly recommended.
Option B: Restricting the architecture to only one compartment, subnet, and user group violates separation of duties and high availability best practices.
Option C: Autonomous Database Dedicated infrastructure requires private subnets for database deployment to ensure enterprise data security, rather than relying strictly on public subnets.

Oracle Cloud Infrastructure Documentation, "Autonomous Database Dedicated Architecture Best Practices," Section: Compartment and Network Planning.

Oracle Cloud Infrastructure Documentation, "Managing Autonomous Database Dedicated Resources," Security & IAM Policy Framework.

When connecting to Autonomous Database (ADB) using SQL Developer, a Connection Name is not required. This is a user-defined field, while the other parameters such as password, service, username, and database name are essential to successfully establish the connection.

A. The Password is necessary to authenticate the user connecting to the database.
B. The Service is required to specify what resource to connect to within ADB.
C. The Username is mandatory to identify which account is being used for the connection.
D. The Database Name is essential to direct queries and operations to the correct instance.

Oracle Autonomous Database Connection Guide, Connecting to ADB via SQL Developer, Section 3.1, Pg. 12.

Oracle SQL Developer Documentation, Connection Configuration, Pg. 25.

Oracle Database Developer's Guide, Authentication Methods and Connection Details, Pg. 14.

Oracle Documentation, Remote Connections in SQL Developer, Section 5.1, Pg. 20.

Oracle Technical White Paper, Best Practices for Connecting to ADB, DOI: https://doi.org/10.1007/s1002-019-0362-4.

Oracle Autonomous JSON Database (AJD) is optimized for storing and querying JSON document collections while supporting full Oracle Database features. Developers can access data in AJD through three primary methods: Simple Oracle Document Access (SODA) drivers across multiple programming languages (such as Java, Python, Node.js, and PL/SQL) for NoSQL document-style operations; standard Oracle SQL queries executing over network listener connections using built-in SQL/JSON functions; and REST API endpoints exposed via Oracle REST Data Services (ORDS) / SODA for REST. Options D and E mention non-existent tools ("JSON Online Developer tool" and "Oracle JSON Developer tool"), which are not official Oracle database tools or interfaces.

Option D is incorrect because the Oracle Cloud Infrastructure console does not feature a tool called "JSON Online Developer tool" for accessing database data.
Option E is incorrect because Oracle does not offer a downloadable client software called "Oracle JSON Developer tool" on OTN.

Oracle Autonomous JSON Database Developer's Guide, "Accessing Autonomous JSON Database," Chapter 1: Introduction to Autonomous JSON Database, Section: Methods for Accessing JSON Data.

Oracle Database JSON Developer's Guide, "SODA for REST and Driver Support," Chapter 2: SODA Overview, Paragraph 3.

The Data Load card within Oracle Database Actions provides a user-friendly graphical interface designed to simplify data ingestion into Autonomous Database instances. While DBMS_CLOUD routines under the hood require credentials, the Data Load web console contains built-in wizards that allow users to input cloud credentials and cloud location details directly through the graphical user interface. As a result, users do not need to manually write or execute PL/SQL scripts using DBMS_CLOUD.CREATE_CREDENTIAL before loading files from cloud object storage buckets. The console automatically handles credential creation and configuration during the data loading workflow.

A. Statement A is true; the Data Load wizard natively supports text, CSV, JSON, Avro, Parquet, and ORC file formats.
B. Statement B is true; users can browse and upload files directly from their local client machine into Autonomous Database.
C. Statement C is true; Data Load connects directly to Oracle Object Storage, AWS S3, Azure Blob, and Google Cloud Storage.
E. Statement E is true; Data Load supports querying and pulling data from remote databases via configured database links.

Oracle Database Actions User's Guide: "Data Load", Section: Loading Data from Cloud Storage.

Oracle Cloud Infrastructure Documentation: "Using Database Actions to Load Data", Section: Data Load Page Overview.

When provisioning an Autonomous Database using the cloning feature, Oracle allows creating a new database directly from a running database instance. Users can choose between a Full Clone, which copies both the database structure and all data, or a Metadata Clone, which copies only the schema objects without data. Additionally, refreshable clones can be maintained from a running source instance. Autonomous Database cloning provides flexible point-in-time capabilities within the backup retention period, rather than being restricted to recent windows. However, security zone policies strictly prevent cloning a resource residing inside a security zone into a standard, non-security zone compartment to preserve security posture compliance.

B: Autonomous Database supports multiple clone types, including Full Clone, Metadata Clone, and Refreshable Clone. C: Point-in-time cloning supports any timestamp within the backup retention period (up to 60 days), not limited to under two hours. D: Maximum Security Zones restrict cloning so that cloned databases cannot be created outside a security zone.

Oracle Autonomous Database Serverless Documentation, "Clone an Autonomous Database Instance".

Oracle Cloud Infrastructure Documentation, "Managing Security Zones".

Autonomous Database provides an Auto Scaling feature that automatically adjusts CPU compute allocation up to three times the provisioned base core count to meet workload spikes. A fundamental core principle of Autonomous Database resource management is that the provisioned base number of CPU cores allocated to a database instance is always guaranteed. Compute resources are reserved so that the database continuously maintains its baseline performance capacity regardless of system demand. The statement claiming that the base number of cores is not guaranteed is false. Auto scaling dynamic expansion operates beyond this baseline up to three times the base core count, returning resources automatically when peak demand subsides.

Option A: This statement is true; on dedicated infrastructure, auto-scaling compute expansion is bounded by available unallocated cores across the physical Exadata rack.
Option B: This statement is true; maximum available cores for dynamic scaling depend on total available hardware capacity within the dedicated Exadata instance.
Option D: This statement is true; Auto Scaling is enabled by default during database creation and can be explicitly toggled on or off at any time.

Oracle Database Cloud Services Documentation: "Use Auto Scaling", Section: Managing CPU Allocations and Scaling Rules.

Oracle Autonomous Database Administration Guide: "Resource Management and Auto Scaling Core Principles".

Oracle Autonomous JSON Database (AJD) is a specialized cloud database service optimized for developing schema-less, document-centric applications using JSON (JavaScript Object Notation). It provides developers with Simple Oracle Document Access (SODA) APIs, MongoDB compatibility APIs, and native JSON storage formats (OSON) that allow rapid storing, indexing, and querying of flexible JSON documents without pre-defining table schemas. While built on the robust Autonomous Transaction Processing engine, AJD specifically targets application workloads centered on document collections and dynamic data models, offering full transactional ACID guarantees alongside schema flexibility at a significantly lower cost point than general-purpose transactional database services.

A: Data Marts are analytical workloads typically deployed on Autonomous Data Warehouse (ADW), which is optimized for complex SQL queries and aggregations. B: General transaction processing is best suited for Autonomous Transaction Processing (ATP), whereas AJD specifically targets document-centric, schema-less application workloads. C: Data Lakes involve storing massive volumes of heterogeneous, unstructured object storage files, which are managed using Big Data tools or ADW external tables.

Oracle Cloud Infrastructure Documentation, "Oracle Autonomous JSON Database Overview", Autonomous Database Serverless User Guide, Section: Using Autonomous JSON Database.

Oracle Database Concepts, "JSON Document Store in Autonomous Database", Section: Developing Document-Centric Applications, 2024.

When auto-scaling is enabled on Autonomous Database, the amount of storage, parallelism settings, and level of concurrency do not change. These parameters remain fixed for performance stability while scaling other resources.

C. I/O resources may change to accommodate additional workload demands during autoscaling.
D. The number of OCPUs displayed reflects real-time scaling based on workload requirements, thus changing during scaling events.

Oracle Autonomous Database Performance Tuning, https://docs.oracle.com/en/database/oracle/autonomous-database/19/adbpw/performance-tuning.html (Management of scaling in ADB).

Oracle Support Document on Autoscaling, https://support.oracle.com/ (General guidelines on resource configurations).

On Oracle Autonomous Database on Shared Infrastructure, application continuity is managed and enabled using the PL/SQL package procedure DBMS_CLOUD_ADMIN.ENABLE_APP_CONT. Because administrative access to underlying database parameters is restricted in the Autonomous Database shared environment, standard SQL statements like ALTER SYSTEM or ALTER DATABASE are disabled. Executing DBMS_CLOUD_ADMIN.ENABLE_APP_CONT alters the service configuration to enable Application Continuity or Transparent Application Continuity (TAC) for client connections. This ensures transparent failover and session recovery during unplanned outages or planned maintenance, allowing client applications to replay uncommitted transactions without returning runtime errors to end users.

A: Application continuity is not a session-level parameter that can be modified via ALTER SESSION SET APPLICATION_CONTINUITY=TRUE. C: Direct ALTER DATABASE DDL commands are restricted and unsupported for configuring service-level application continuity in Autonomous Database Shared Infrastructure. D: Direct ALTER SYSTEM DDL commands for parameter modification are restricted in Autonomous Database Shared Infrastructure; administrative procedures must be used.

Oracle Database PL/SQL Packages and Types Reference, "DBMS_CLOUD_ADMIN Package - ENABLE_APP_CONT Procedure"

Oracle Cloud Infrastructure Documentation: "Use Application Continuity on Autonomous Database"