1z0-1084-26 Exam Questions & Answers

The OCI CLI command oci events rule create requires the --actions parameter to define the destinations invoked when the Events rule condition matches. Oracle identifies --actions as a required complex parameter and explicitly supports loading its JSON representation from a local file using file://path/to/file. Oracle's Events examples show the same pattern: --actions file://actions.json. The other proposed parameters-----destinations, --targets, and --action-payload---are not valid parameters for the events rule create CLI operation. The actions file can define supported destinations such as Notifications, Streaming, or Functions. Consequently, option D precisely matches the current OCI CLI command-reference syntax for programmatically creating the rule with action definitions stored in a file.

Idle-timeout is the parameter that is used to configure the time period during which an idle function will remain in memory before Oracle Functions removes its container image from memory2.The idle-timeout parameter is specified in seconds and can be set when creating or updating a function2.The default value for idle-timeout is 30 seconds and the maximum value is 900 seconds (15 minutes)2.If a function has the --provisioned-concurrency option enabled, the idle-timeout parameter is ignored and the function instances are always kept in memory3. Verified Reference:Creating Functions,Provisioned Concurrency

The Transactional Outbox pattern addresses the distributed-system dual-write problem by recording both the business-state change and an outgoing event within one local database transaction. Rather than attempting to atomically update a database and independently publish to a messaging platform, the service writes the event into an outbox table alongside the business update. Because both database modifications occur within the same transaction, they commit or roll back together. A separate publisher subsequently reads the outbox and sends the event to the messaging infrastructure. Oracle's current microservices architecture documentation explicitly identifies Transactional Outbox as the pattern for sending a message and performing a data manipulation operation within a single local transaction. Saga and CQRS address different distributed-system concerns.

The correct answer is: fn deploy --app travel-app --all To build and deploy multiple Oracle Functions as part of a single application named 'travel-app,' you can use the fn deploy command with the appropriate options. The command fn deploy --app travel-app --all is the correct syntax. Here's what each part of the command does: fn deploy: This command is used to deploy functions and applications in Oracle Functions. --app travel-app: This option specifies the application name as 'travel-app,' indicating that you want to deploy functions to this application. --all: This option indicates that you want to deploy all the functions within the application. By using fn deploy --app travel-app --all, you can build and deploy all the functions in your travel application across different programming languages (Java, Python, and Node.js) to the 'travel-app' application in Oracle Functions.

The Twelve-Factor methodology requires configuration to be separated from application code and backing services to be treated as attached resources. Oracle's Twelve-Factor guidance specifically recommends keeping configuration outside the Docker image and supplying deployment-specific values through the environment. This allows the same application artifact to move between development, test, and production without rebuilding it. Kubernetes ConfigMaps or environment variables implement this principle effectively. The backing-services factor similarly treats databases, queues, caches, and external services as replaceable resources referenced through configuration rather than hardcoded dependencies. Consequently, switching a database or message broker should require configuration changes rather than application-code changes. Hardcoding credentials or environment-specific values violates configuration separation, while sharing one database across environments is not required for dev/prod parity. Therefore, B and D are correct. Top of Form

Bottom of Form