A developer runs fn init --runtime python water-quality-check for a new OCI Function. What does that command produce?
Select an answer to reveal the explanation.
Short Explanation
fn init is unpacking the project kit on your desk: directory, func.yaml, and language starter files. It does not deploy, create the application, or push an image—that comes later.
Full Explanation
Running fn init --runtime python water-quality-check creates a local directory with func.yaml and language scaffolding without deploying. Init unpacks the project kit on the developer’s workstation—directory, metadata file, and starter sources (for example, Python handler stubs)—so civic developers can iterate locally first. Creating the OCI application, pushing to OCIR, and registering the function are later steps.
Claiming init creates the OCI application and pushes an image to OCIR in one step fails by concept because those are deploy/application operations, not what fn init performs. Registering a signed invoke endpoint on API Gateway automatically fails because API Gateway integration is a separate caller setup, not an init side effect. Provisioning a regional subnet and service gateway for the function fails because networking belongs to Functions application (and VCN) setup, not to local project scaffolding.
Exam caveat: after init you still need an application with correct subnets and an OCI CLI context before a successful cloud deploy—init alone never places code in OCI. Operational check: run init for the water-quality function, confirm func.yaml and source files exist locally, invoke locally if desired, then separately create/select the application and deploy.