Updated Oct 01, 2025 Verified Pass 1Z0-1084-25 Exam in First Attempt Guaranteed
Free 1Z0-1084-25 Sample Questions and 100% Cover Real Exam Questions (Updated 101 Questions)
Oracle 1Z0-1084-25 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 28
Which is NOT a valid backend-type option available when configuring an Oracle Cloud Infrastructure (OCI) API Gateway Deployment?
- A. ORACLE_FUNCTIONS_BACKEND
- B. ORACLE STREAMS_BACKEND
- C. HTTP_BACKEND
Answer: B
Explanation:
When configuring an OCI API Gateway deployment, you need to specify the backend type for each route in your API deployment specification3. The backend type determines how the API gateway handles requests to that route and forwards them to the appropriate backend service3. The following backend types are valid options for an OCI API Gateway deployment3:
HTTP_BACKEND: The API gateway forwards requests to an HTTP or HTTPS URL as the backend service.
ORACLE_FUNCTIONS_BACKEND: The API gateway invokes an Oracle Functions function as the backend service.
STOCK_RESPONSE_BACKEND: The API gateway returns a stock response without invoking any backend service. ORACLE STREAMS_BACKEND is not a valid backend type for an OCI API Gateway deployment. Oracle Streams is a fully managed, scalable, and durable messaging service that you can use to ingest and consume large amounts of data in real-time4. However, Oracle Streams is not supported as a backend service for an OCI API Gateway deployment.
NEW QUESTION # 29
Which of these is a valid use case for OCI Queue?
- A. Managing network traffic between services
- B. Building decoupled and scalable systems
- C. Sending real-time streaming data
- D. Storing and retrieving large files
Answer: B
Explanation:
OCI Queue is a fully managed serverless service that helps decouple systems and enable asynchronous operations2. Queue handles high-volume transactional data that requires independently processed messages without loss or duplication2. A valid use case for OCI Queue is building decoupled and scalable systems, such as event-driven architectures or microservices-based applications2. For example, you can use Queue to decouple your application and build an event-driven architecture. Decoupling ensures that individual application components can scale independently and that you can future-proof your design so that as new application components are built, they can publish or subscribe to the queue2.
NEW QUESTION # 30
Which two "Action Type" options are NOT available in an Oracle Cloud Infrastructure (OCI) Events rule definition? (Choose two.)
- A. Functions
- B. Email
- C. Slack
- D. Notifications
- E. Streaming
Answer: B,C
Explanation:
The two "Action Type" options that are NOT available in an Oracle Cloud Infrastructure (OCI) Events rule definition are: Email (Correct) Slack (Correct) The available "Action Type" options in OCI Events rule definition include Functions, Notifications, and Streaming. However, email and Slack are not directly supported as action types in OCI Events. Instead, you can use Notifications to send notifications to various notification channels, including email and Slack, through the OCI Notifications service.
NEW QUESTION # 31
Which of the following step is NOT required for setting up the Container Engine for Kubernetes (OKE) cluster access using a local installation of kubectl?
- A. Generate Auth token from the OCI console to access the OKE cluster using kubectl.
- B. Generate an API signing key pair (if you do not already have one) and upload the public key of the API signing key pair.
- C. Install and configure the Oracle Cloud Infrastructure (OCI) CLI.
- D. Set up the kubeconfig file.
Answer: A
Explanation:
The step that is NOT required for setting up the Container Engine for Kubernetes (OKE) cluster access using a local installation of kubectl is to generate an Auth token from the OCI console. The authentication for accessing the OKE cluster using kubectl can be performed using the OCI CLI configuration, specifically the API signing key pair and the kubeconfig file. Here are the correct steps for setting up the OKE cluster access using a local installation of kubectl: Set up the kubeconfig file: The kubeconfig file contains the necessary information to authenticate and access the OKE cluster using kubectl. It includes details such as the cluster endpoint, authentication method, and credentials. Generate an API signing key pair (if you do not already have one) and upload the public key of the API signing key pair: The API signing key pair is used for authentication with the OCI services. The public key of the key pair needs to be uploaded to the OCI Console to associate it with your user account. Install and configure the Oracle Cloud Infrastructure (OCI) CLI: The OCI CLI provides a command-line interface to interact with the OCI services. It needs to be installed and configured with your OCI credentials, including the user's OCID, tenancy OCID, region, and the path to the API signing key pair. By completing these steps, you can configure kubectl to access and manage your OKE clusters from your local machine using the OCI CLI authentication configuration.
NEW QUESTION # 32
You are tasked with developing an application that requires the use of Oracle Cloud Infrastructure (OCI) APIs to POST messages to a stream in the OCI Streaming service. Which statement is incorrect? (Choose the best answer.)
- A. The Content-Type header must be set to application/json
- B. The request does not require an Authorization header.
- C. An HTTP 401 will be returned if the client's clock is skewed more than 5 minutes from the server's.
- D. The request must include an authorization signing string including (but not limited to) x-content-sha256, content-type, and content-length headers.
Answer: B
Explanation:
The statement that is incorrect is: "The request does not require an Authorization header." In order to POST messages to a stream in the OCI Streaming service using OCI APIs, the request does require an Authorization header. The Authorization header is used to provide authentication and ensure the request is authorized to access the stream. The correct approach is to include the Authorization header in the request, along with other required headers such as x-content-sha256, content-type, and content-length. Therefore, the incorrect statement is that the request does not require an Authorization header.\
NEW QUESTION # 33
A developer using Oracle Cloud Infrastructure (OCI) API Gateway needs to authenticate the API requests to their web application. The authentication process must be implemented using a custom scheme which accepts string-based parameters from the API caller. Which approach should the developer use in this scenario?
- A. Create an authorizer function using token-based authorization.
- B. Create a cross account functions authorizer.
- C. Create an authorizer function using request header authorization.
- D. Create an authorizer function using OCI Identity and Access Management 91AM) based authentication.
Answer: A
Explanation:
In the given scenario, the developer should use the approach of creating an authorizer function using token-based authorization. Token-based authorization is a commonly used approach for authenticating API requests. It involves generating and issuing tokens to API callers, which they can then include in the requests they make to the API. The tokens serve as proof of authentication and are validated by the server to ensure the caller's identity and access rights. By creating an authorizer function using token-based authorization, the developer can implement a custom scheme that accepts string-based parameters from the API caller. This allows the developer to define their own authentication logic and validate the provided tokens according to their requirements. The authorizer function can be configured in the OCI API Gateway to be invoked before forwarding the request to the web application. It will perform the necessary token validation and authentication checks, allowing only authorized requests to access the protected resources of the web application.
NEW QUESTION # 34
You have a containerized application that requires access to an Autonomous Transaction Processing (ATP) Database. Which option is NOT valid when the container is deployed in an OKE cluster? (Choose the best answer.)
- A. Use Kubernetes secrets to configure environment variables on the container with ATP instance OCID, and OCI API credentials. Then use the CreateConnection API endpoint from the service runtime.
- B. Install the Oracle Cloud Infrastructure Service Broker on the Kubernetes cluster and deploy ServiceInstance and ServiceBinding resources for ATP. Then use the specified binding name as a volume in the application deployment manifest.
- C. Enable Oracle REST Data Services for the required schemas and connect via HTTPS.
- D. Create a Kubernetes secret with contents from the instance Wallet files. Use this secret to create a volume mounted to the appropriate path in the application deployment manifest.
Answer: B
Explanation:
The option that is not valid for connecting to an Autonomous Transaction Processing (ATP) Database from a container in Kubernetes is: Install the Oracle Cloud Infrastructure Service Broker on the Kubernetes cluster and deploy ServiceInstance and ServiceBinding resources for ATP. Then use the specified binding name as a volume in the application deployment manifest. The Oracle Cloud Infrastructure Service Broker is not used for connecting to an ATP Database from a container in Kubernetes. The Service Broker is used for provisioning and managing cloud services directly from Kubernetes. It allows you to create and manage instances of OCI services using Kubernetes resources like ServiceInstance and ServiceBinding. To connect to an ATP Database from a container in Kubernetes, you can use one of the following valid options: Enable Oracle REST Data Services for the required schemas and connect via HTTPS. This involves enabling and configuring Oracle REST Data Services (ORDS) for the schemas in the ATP Database. You can then connect to the ATP Database using RESTful endpoints provided by ORDS. Use Kubernetes secrets to configure environment variables on the container with ATP instance OCID and OCI API credentials. Then use the CreateConnection API endpoint from the service runtime. This approach involves configuring the necessary environment variables on the container to provide the ATP instance OCID and OCI API credentials. The application can then use the OCI SDK or REST API (such as the CreateConnection endpoint) to establish a connection to the ATP Database. Create a Kubernetes secret with contents from the instance Wallet files. Use this secret to create a volume mounted to the appropriate path in the application deployment manifest. This method involves creating a Kubernetes secret that contains the necessary credentials from the ATP Database's instance wallet files. The secret can then be mounted as a volume in the application deployment, allowing the application to access the required credentials for connecting to the ATP Database. Both options 1 and 3 provide valid approaches for connecting to an ATP Database from a container in Kubernetes, depending on the specific requirements and preferences of the application.
NEW QUESTION # 35
Which is NOT a valid use case for leveraging the Oracle Cloud Infrastructure (OCI) Events service?
- A. Publishing all the OCI resource events in a specific compartment to the OCI Streaming service for later analysis.
- B. Capturing the OCI Monitoring service alarms and invoking autoscaling of compute instances.
- C. Triggering a notification action when a function completes its execution.
- D. Triggering a function deployed in Oracle Functions when new files are uploaded to an OCI Object Storage bucket.
- E. Publishing a notification when long-lived tasks complete, such as an OCI Autonomous Database backup completion.
Answer: B
Explanation:
The use case that is NOT a valid use case for leveraging the Oracle Cloud Infrastructure (OCI) Events service is "Capturing the OCI Monitoring service alarms and invoking autoscaling of compute instances." The OCI Events service is designed to provide event-driven architecture and enable automated responses to events occurring within the Oracle Cloud Infrastructure. It allows you to react to changes and activities happening within your OCI resources. The Events service can be used to trigger actions based on events like file uploads, resource changes, or task completions. However, capturing the OCI Monitoring service alarms and invoking autoscaling of compute instances is not a direct functionality provided by the OCI Events service. Autoscaling based on monitoring metrics is typically handled by the OCI Autoscaling service, which is specifically designed for that purpose. The OCI Monitoring service provides monitoring and alerting capabilities, while the Autoscaling service handles the dynamic scaling of compute instances based on predefined policies and thresholds.
NEW QUESTION # 36
Which is NOT a valid option to execute a function deployed in Oracle Functions?
- A. Send signed HTTP requests to the function's invoke endpoint.
- B. Invoke from the OCI CLI.
- C. Trigger by an event in the Oracle Cloud Infrastructure (OCI) Events service.
- D. Invoke from the Fn Project CLI.
- E. Invoke from the Docker CLI.
Answer: E
Explanation:
The correct answer is: Invoke from the Docker CLI. Explanation:: Executing a function deployed in Oracle Functions is typically done using the following options: Invoke from the Fn Project CLI: The Fn Project CLI provides a command-line interface specifically designed for interacting with Oracle Functions. You can use commands like fn invoke to invoke a function. Trigger by an event in the Oracle Cloud Infrastructure (OCI) Events service: You can configure events in OCI to trigger your function based on various criteria, such as object storage events, resource state changes, or scheduled events. Invoke from the OCI CLI: The OCI CLI (Command Line Interface) allows you to interact with various services in Oracle Cloud Infrastructure, including Oracle Functions. You can use the fn invoke command to invoke a function. Send signed HTTP requests to the function's invoke endpoint: Oracle Functions provides an HTTP endpoint that can be used to invoke functions. You can send signed HTTP requests to this endpoint using tools or programming languages that support making HTTP requests. On the other hand, invoking a function deployed in Oracle Functions using the Docker CLI is not a valid option. The Docker CLI is primarily used for managing Docker containers and images, and it does not provide a direct mechanism for invoking functions in Oracle Functions.
NEW QUESTION # 37
How are cloud native application versions deployed to an OKE cluster when using a blue/green deployment strategy?
- A. Current applications are slowly replaced with new application versions.
- B. Both old and new application versions are deployed to production at the same time.
- C. New application versions are deployed in minor increments to a select group of people.
Answer: B
Explanation:
Blue/Green deployment strategy allows releasing a new version of an application using two identical environments where one of them is active at a given time. The current version of the application is provisioned on the active environment, whereas the new version gets deployed to the standby environment1. The traffic is shifted from the active to the standby environment by updating the ingress resource2. Therefore, both old and new application versions are deployed to production at the same time, but only one of them receives the traffic. Verified Reference: Announcing new deployment strategies for OCI DevOps Service, Blue-Green OKE Deployment
NEW QUESTION # 38
Which "Action Type" option is NOT available in an Oracle Cloud Infrastructure (OCI) Events rule definition?
- A. Functions
- B. Email
- C. Notifications
- D. Streaming
Answer: B
Explanation:
An action is a response that you define for the rule to perform when the filter finds a matching event1. The action type specifies the service that you want to invoke by delivering the event message1. The following action types are available in OCI Events rule definition1:
Streaming: Send to a stream from Oracle Streaming Service.
Notifications: Send to an Oracle Notification Service topic.
Functions: Send to an Oracle Functions Service endpoint. Email is not a valid action type for OCI Events rule definition. To send an email as an action, you need to use the Notifications service and subscribe to a topic with an email protocol2.
NEW QUESTION # 39
You are developing a serverless application with Oracle Functions and Oracle Cloud Infrastructure Object Storage. Your function needs to read a JSON file object from an Object Storage bucket named "input-bucket" in compartment "qa-compartment". Your corporate security standards mandate the use of Resource Principals for this use case. Which two statements are needed to implement this use case? (Choose two.)
- A. Set up a policy to grant all functions read access to the bucket: allow all functions in compartment qa-compartment to read objects in target.bucket.name= "input-bucket'
- B. Set up a policy to grant your user account read access to the bucket: allow user XYZ to read objects in compartment qa-compartment where target.bucket.name= "input-bucket'
- C. No policies are needed. By default, every function has read access to Object Storage buckets in the tenancy.
- D. Set up the following dynamic group for your function's OCID: Name: read-file-dg Rule: resource.id = "ocid1.fnfunc.oc1.phx.aaaaaaaakeaobctakezjz5i4ujj7g25q7sx5m vr55pms6f4da'
- E. Set up a policy with the following statement to grant read access to the bucket: allow dynamic-group read-file-dg to read objects in compartment qa- compartment where target.bucket.name= 'input-bucket'
Answer: D,E
Explanation:
The correct answers are: Set up the following dynamic group for your function's OCID: Name: read-file-dg Rule: resource.id = "ocid1.fnfunc.oc1.phx.aaaaaaaakeaobctakezjz5i4ujj7g25q7sx5mvr55pms6f4da" Set up a policy with the following statement to grant read access to the bucket: Statement: allow dynamic-group read-file-dg to read objects in compartment qa-compartment where target.bucket.name = 'input-bucket' Explanation:: To implement the use case of reading a JSON file object from an Object Storage bucket using Resource Principals with Oracle Functions, you need to configure the following: Create a dynamic group named "read-file-dg" and associate it with your function's OCID. This dynamic group helps identify the function as a member of the group for policy enforcement. Create a policy that grants read access to the bucket. The policy statement should allow the dynamic group "read-file-dg" to read objects in the compartment "qa-compartment" and specify the target bucket name as "input-bucket". This policy ensures that the function has the necessary permissions to access the specified bucket. By setting up the dynamic group and policy, you ensure that the function, as a member of the dynamic group, has the required read access to the specified Object Storage bucket in the specified compartment.
NEW QUESTION # 40
You plan to implement logging in your services that will run in Oracle Cloud Infrastructure (OCI) Container Engine for Kubernetes (OKE). Which statement describes the appropriate logging approach?
- A. Each service logs to its own log file.
- B. All services log to an external logging system.
- C. All services log to standard output only.
- D. All serviceAAs log to a shared log file.
Answer: C
Explanation:
The appropriate logging approach for services running in Oracle Cloud Infrastructure (OCI) Container Engine for Kubernetes (OKE) is: "All services log to standard output only." When running services in a containerized environment like OKE, it is recommended to follow the Twelve-Factor App methodology, which suggests treating logs as event streams. According to this methodology, services should write their log events to standard output (stdout) instead of writing to log files. By logging to standard output, the container runtime (such as Kubernetes) can collect and aggregate the logs generated by the services. These logs can then be accessed and managed through the container runtime's logging infrastructure. Logging to standard output offers several advantages in a containerized environment: Simplicity and consistency: Standardizing on logging to stdout ensures a consistent approach across different services, making it easier to manage and analyze logs. Log aggregation: The container runtime can collect the logs from all the running containers and provide centralized log management, allowing you to access and search logs from different services in one place. Scalability: Since logs are written to stdout, they can be easily handled by the container runtime's log management system, which can scale to handle large volumes of log data. Separation of concerns: By logging to stdout, the responsibility of managing log files and their rotation is shifted to the container runtime, allowing the services to focus on their core functionality. While it is possible to log to log files or external logging systems, the recommended approach in a containerized environment like OKE is to log to standard output and leverage the logging infrastructure provided by the container runtime.
NEW QUESTION # 41
What is the difference between blue/green and canary deployment strategies? (Choose the best answer.)
- A. In blue/green, both old and new applications are in production at the same time. In canary, the application Is deployed incrementally to a select group of people.
- B. In blue/green, current applications are slowly replaced with new ones. In canary, the application Is deployed Incrementally to a select group of people.
- C. In blue/green, the application Is deployed In minor Increments to a select group of people. In canary, both old and new applications are simultaneously in production.
- D. In blue/green, current applications are slowly replaced with new ones. In canary, both old and new applications are in production at the same time.
Answer: A
Explanation:
The correct answer is: In blue/green deployment, both old and new applications are in production at the same time. In canary deployment, the application is deployed incrementally to a select group of people. In a blue/green deployment strategy, two identical environments, referred to as blue and green, are set up. The current production environment (blue) continues to serve live traffic while a new version of the application is deployed in the green environment. Once the new version is tested and deemed stable, traffic is routed from the blue environment to the green environment, making it the new production environment. This approach allows for a seamless switch between the old and new versions of the application. On the other hand, in a canary deployment strategy, the new version of the application is deployed incrementally to a small subset of users or a specific group. This allows for testing the new version in a real production environment while minimizing the impact of any potential issues. If the new version performs well and meets the desired criteria, it can be gradually rolled out to a larger audience or the entire user base. In summary, the main difference between blue/green and canary deployment strategies lies in how the deployment is managed. Blue/green involves simultaneous production of both old and new applications, while canary deployment focuses on incremental deployment to a select group of users.
NEW QUESTION # 42
You have two microservices, A and B, running in production. Service A relies on APIs from service B. You want to test changes to service A without deploying all of its dependencies, which include service B. Which approach should you take to test service A?
- A. There is no need to explicitly test APIs.
- B. Test the APIs in private environments.
- C. Test using API mocks.
- D. Test against production APIs.
Answer: C
Explanation:
API mocking is a technique that simulates the behavior of real APIs without requiring the actual implementation or deployment of the dependent services1. API mocking allows you to test changes to service A without deploying all of its dependencies, such as service B, by creating mock responses for the APIs that service A relies on1. API mocking has several benefits, such as1:
Faster testing: You can test your service A without waiting for service B to be ready or available, which reduces the testing time and feedback loop.
Isolated testing: You can test your service A in isolation from service B, which eliminates the possibility of external factors affecting the test results or causing errors.
Controlled testing: You can test your service A with different scenarios and edge cases by creating mock responses that mimic various situations, such as success, failure, timeout, etc.
NEW QUESTION # 43
You developed a microservices-based application that runs in an Oracle Cloud Infrastructure (OCI) Container Engine for Kubernetes (OKE) cluster. Your security team wants to use SSL termination for this application. What should you do to create a secure SSL termination for this application using the fewest steps possible?
- A. Create a self-signed certificate and its corresponding key. Create a Kubernetes secret using the certificate and the key. Then add these annotations to the Kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-tls-secret: ssl certificate-secret
- B. Add these annotations to the kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-ssl-secret-key: ssl secret-key
- C. Create a self-signed certificate and its corresponding key. Create a Kubernetes secret using the certificate and the key. Then add these annotations to the Kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-security-list management-mode: "Frontend"
- D. Generate a self-signed certificate using Let's Encrypt. Use that certificate on OCI Load Balancer. Create the Kubernetes service using this load balancer.
Answer: A
Explanation:
The correct answer is: "Create a self-signed certificate and its corresponding key. Create a Kubernetes secret using the certificate and the key. Then add these annotations to the Kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: '443' service.beta.kubernetes.io/oci-load-balancer-tls-secret: ssl certificate-secret." To create a secure SSL termination for your microservices-based application running in an OCI Container Engine for Kubernetes (OKE) cluster, you can follow these steps: Create a self-signed certificate and its corresponding key: Generate a self-signed SSL certificate and its private key using a tool like OpenSSL. Create a Kubernetes secret: Create a Kubernetes secret using the certificate and key obtained in the previous step. This secret will securely store the certificate and key within the Kubernetes cluster. Add annotations to the Kubernetes service: Modify the Kubernetes service that exposes your application and add the following annotations to enable SSL termination: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: '443' (specify the SSL port as 443) annotations: service.beta.kubernetes.io/oci-load-balancer-tls-secret: ssl certificate-secret (specify the name of the Kubernetes secret containing the certificate and key) By following these steps, you can create a secure SSL termination for your application using a self-signed certificate and Kubernetes secret. The annotations added to the Kubernetes service ensure that the SSL port is configured correctly and the TLS secret is utilized for SSL termination when traffic reaches the load balancer. The other options provided are not the most suitable approaches for achieving secure SSL termination in an OCI Container Engine for Kubernetes (OKE) cluster: Adding annotations related to the OCI load balancer SSL secret key is not the correct approach for SSL termination in this scenario. Using Let's Encrypt to generate a self-signed certificate and configuring it on the OCI Load Balancer is not necessary when you can create and manage the SSL certificate within the Kubernetes cluster using a Kubernetes secret.
NEW QUESTION # 44
A DevOps engineer is troubleshooting the Meshifyd application, which is running in an Oracle Cloud Infrastructure (OCI) environment. The engineer has set up the OCI Logging service to store access logs for the application but notices that the logs from the Meshifyd application are not showing up in the logging service. The engineer suspects that there might be an issue with the logging configuration. Which two statements are potential reasons for logs from the Meshifyd application not showing up in the OCI Logging service?
- A. The logconfig.json file has incorrect or missing OCID for the custom log group in the logGroupObjectId field.
- B. The logconfig.json file has incorrect or missing information in the application namespace in the paths field.
- C. The OCI Logging service is set up to pre access logs by creating a log group and custom log within the same compartment.
- D. The logconfig.json file has incorrect or missing information in the application namespace in the src field.
- E. The logconfig.json file has incorrect or missing OCID for the custom log in the logobjectId field.
Answer: A,E
Explanation:
The logconfig.json file is a configuration file that specifies how the Unified Monitoring Agent collects and uploads custom logs to the OCI Logging service2. The logconfig.json file contains an array of objects, each representing a custom log configuration2. Each custom log configuration object has the following fields2:
logGroupObjectId: The OCID of the log group where the custom log is stored.
logObjectId: The OCID of the custom log.
paths: An array of paths to files or directories containing the custom logs.
src: A regular expression that matches the files containing the custom logs.
parser: A parser definition that specifies how to parse the custom logs. If the logconfig.json file has incorrect or missing OCID for the custom log in the logobjectId field, or incorrect or missing OCID for the custom log group in the logGroupObjectId field, then the Unified Monitoring Agent will not be able to upload the custom logs to the OCI Logging service2. Therefore, these are potential reasons for logs from the Meshifyd application not showing up in the OCI Logging service. Verified Reference: Unified Monitoring Agent Configuration File
NEW QUESTION # 45
You are developing a polyglot serverless application using Oracle Functions. Which language cannot be used to write your function code?
- A. Java
- B. Go
- C. Python
- D. PL/SQL
- E. Node.js
Answer: D
Explanation:
Oracle Functions does not currently support PL/SQL as a language for writing function code. PL/SQL is a procedural language used in Oracle Database for developing stored procedures, triggers, and other database-related code. However, Oracle Functions supports several other popular programming languages such as Go, Node.js, Python, and Java, allowing developers to choose the language that best suits their application requirements and their familiarity with the language. While PL/SQL is powerful for working with the Oracle Database, it is not an option for writing function code in the Oracle Functions serverless architecture.
NEW QUESTION # 46
......
Download Real Oracle 1Z0-1084-25 Exam Dumps Test Engine Exam Questions: https://www.troytecdumps.com/1Z0-1084-25-troytec-exam-dumps.html
Verified 1Z0-1084-25 Dumps Q&As - 1Z0-1084-25 Test Engine with Correct Answers: https://drive.google.com/open?id=1EHSr7ox-tKRoSgAH3O4i2ypy9aNe0v3y