1Z0-1085-23 · Question #111
What is the primary purpose of Oracle Cloud infrastructure functions?
The correct answer is A. To execute code in response to events or HTTP requests. The primary purpose of Oracle Cloud Infrastructure Functions is to execute code in response to events or HTTP requests. Functions is a fully managed, serverless platform that allows users to deploy and run code without provisioning or managing any infrastructure. Functions can…
Question
What is the primary purpose of Oracle Cloud infrastructure functions?
Options
- ATo execute code in response to events or HTTP requests
- BTo store and manage files
- CTo provide a managed database service
- DTo deploy and manage virtual machine
How the community answered
(57 responses)- A81% (46)
- B4% (2)
- C5% (3)
- D11% (6)
Explanation
The primary purpose of Oracle Cloud Infrastructure Functions is to execute code in response to events or HTTP requests. Functions is a fully managed, serverless platform that allows users to deploy and run code without provisioning or managing any infrastructure. Functions can be triggered by various sources, such as object storage, streaming, API gateway, or other cloud
Topics
Community Discussion
8
Toby R.Jun 27, 2026A is correct. OCI Functions is a serverless compute service, meaning you write a function and it runs when triggered by an event or an HTTP call, no server management needed. The other options describe Object Storage, Autonomous Database, and Compute instances respectively, all completely separate services.
Fatima Z.Jun 27, 2026Hook is "Functions Fire on Triggers," saw this exact Q on my exam and A clicked instantly because fire equals event or HTTP, not storage, not VMs, not databases, boom, done.
Dragan P.Jun 29, 2026Good mnemonic but careful with "not storage" because Object Storage fires Events service notifications that absolutely can invoke a Function, and that showed up in the 2023 exam refresh right alongside the HTTP and streaming triggers.
Wesley A.Jun 27, 2026OCI Functions is the serverless compute layer, meaning you never touch the underlying infrastructure and your code only runs when something triggers it, whether that is an event from another OCI service or a direct HTTP call. Quick check though: when they say "in response to events or HTTP requests," do you have a solid picture of what kinds of events can actually trigger a function, like Object Storage uploads or streaming messages, versus what would need a different compute service?
Fatima Z.Jun 28, 2026Just burn "SHOE" into your brain for the classic OCI Functions triggers, S for Streaming messages, H for HTTP via API Gateway, O for Object Storage events, and E for Events Service rules, because the exam loves testing whether you know that anything needing persistent processes or GPU work belongs on Compute or Container Engine instead.
Dragan P.Jun 19, 2026A is the only defensible answer, though "events or HTTP requests" undersells it since invocations also come from OCI Events, Notifications, API Gateway, and Logging, not just raw HTTP.
Carlos M.Jun 27, 2026OCI Functions is serverless compute, so the whole point is that you trigger a function by an event or HTTP call and the platform handles everything else underneath. Quick check though, do you know what kind of events can actually kick off a function in OCI, like is it only HTTP or can other OCI services trigger it too?
Fatima Z.Jun 28, 2026OCI Functions can be triggered by way more than HTTP alone, think of the acronym NOSE to remember the four main sources: Notifications service, Object Storage events, Streaming (Kafka-compatible), and Events service (which hooks into dozens of OCI resource actions like compute instance changes or DB backups).