Pass the Oracle Cloud Infrastructure 1z0-1084-26 Questions and answers with ExamsMirror

Explanation

To dynamically make Kubernetes resources discoverable to public DNS servers, you can use ExternalDNS. ExternalDNS is a Kubernetes add-on that automates the management of DNS records for your Kubernetes services and ingresses. It can be configured to monitor the changes in your Kubernetes resources and automatically update DNS records in a supported DNS provider. By integrating ExternalDNS with your Kubernetes cluster, you can ensure that the DNS records for your services and ingresses are automatically created, updated, or deleted based on changes in your Kubernetes resources. This allows your Kubernetes resources to be discoverable by external systems through public DNS servers.

Explanation

The maximum execution time of Oracle Functions is 300 seconds, which is equivalent to 5 minutes. This means that a function running within Oracle Functions cannot exceed a runtime of 5 minutes. If a function requires longer execution times, alternative approaches such as invoking external services asynchronously or using long-running processes should be considered. It is important to design functions with this execution time limitation in mind to ensure optimal performance and efficiency within the Oracle Functions platform.

Oracle Events uses the singular top-level field eventType to identify the type of event represented by an event message. When a rule must match more than one event type, Oracle explicitly documents placing multiple event-type strings in a JSON array assigned to eventType. Values within that array operate as alternatives, allowing the condition to match an event corresponding to any listed type. eventTypes, actionTypes, and filterType are not valid substitutes for the documented field. Likewise, concatenating event types into a single pipe-delimited or comma-delimited string does not create multiple event matches. Option D therefore implements the exact structure Oracle shows in its Events filtering examples for a rule covering multiple event types.

OCI API Gateway supports the following authentication methods for accessing an API deployment3:

HTTP Basic: The client sends a username and password with each request. The credentials are validated against a user database in Oracle Identity Cloud Service (IDCS).

API Key: The client sends an API key with each request. The API key is validated against a list of keys stored in IDCS or OCI Vault.

OAuth: The client obtains an access token from an authorization server (such as IDCS) and sends it with each request. The access token is validated against the authorization server and optionally checked for required scopes.

JWT Token: The client obtains a JSON Web Token (JWT) from an identity provider (such as IDCS or OCI IAM) and sends it with each request. The JWT is validated against the identity provider’s public key and optionally checked for required claims. SAML Token is not a valid authentication method for accessing an OCI API Gateway deployment. SAML is an XML-based standard for exchanging authentication and authorization data between different parties, such as a service provider and an identity provider4. SAML tokens are typically used for web browser single sign-on (SSO) scenarios, not for API access4.

Oracle ' s current OCI Streaming limits specify that each stream partition supports a total data write rate of 1 MB per second. Partition count is therefore a fundamental capacity-planning parameter for producer workloads. If an application is expected to produce more than 1 MB per second, the stream must contain enough partitions to distribute the required ingress throughput appropriately. Oracle ' s partitioning guidance likewise states that expected throughput should be calculated before stream creation because each partition is limited to the 1 MB-per-second write rate. The 2 MB figure is not the documented write limit, while 4 MB and 8 MB exceed the per-partition ingress capacity. Therefore, the maximum write throughput represented by the available choices is 1 MB per second.

Explanation

The correct answer is: " Adding a custom certificate authority (CA) or custom CA bundle to your gateway ' s trust store for mTLS is optional unless you need to reject certificates that do not contain particular values (such as a domain name). " The statement that is NOT valid regarding the mTLS options in OCI API Gateway is: " Adding a custom certificate authority (CA) or custom CA bundle to your gateway ' s trust store for mTLS is optional unless you need to reject certificates that do not contain particular values (such as a domain name). " In OCI API Gateway, adding a custom certificate authority (CA) or custom CA bundle to the gateway ' s trust store is not optional. It is a necessary step when configuring mTLS authentication. The trust store in the gateway is used to validate the client certificates presented during mTLS authentication. The other options listed are valid regarding the mTLS options in OCI API Gateway: Once the mTLS request policy is enabled, all requests with valid certificates are routed to the backend unless specific values (such as a domain name) are defined. This means that only requests with valid client certificates will be allowed to access the backend microservices. The mTLS request policy can only be enabled at the API deployment specification level, and it applies globally to all routes in that deployment. This ensures consistent mTLS authentication across all routes and endpoints in the API deployment. Custom CA or custom CA bundles can be added to the gateway ' s trust store, but only if they already exist in the OCI Certificates service. This allows you to include trusted CAs or CA bundles to validate client certificates during mTLS authentication.

Explanation

The correct approach to receive an email each time a Terraform action begins in Oracle Cloud Infrastructure (OCI) Resource Manager without writing any code is as follows: Create an OCI Notification topic and email subscription with the destination email address. This will define the email delivery configuration. Create an OCI Events rule that matches the " Resource Manager Job - Create " condition. This rule will be triggered when a Resource Manager job is created. In the OCI Events rule, select the notification topic that was created in step 1 as the action for the corresponding event. This will ensure that the notification is sent to the specified email address. By following these steps, you can configure the OCI Events service to send an email notification whenever a Resource Manager job is created in OCI Resource Manager.

OCI Vault provides both Secret Expiry Rules and Secret Reuse Rules. secret_version_expiry_interval uses an ISO 8601 duration, so P30D establishes a 30-day validity period. Setting is_secret_content_retrieval_blocked_on_expiry to true ensures secret contents cannot be retrieved after expiry, satisfying the first requirement. For the second requirement, a SECRET_REUSE_RULE prevents previously used secret contents from being reused across versions. Oracle ' s SDK documentation confirms that is_enforced_on_deleted_secret_versions=true extends that restriction even when the previous secret version has been deleted. Setting either Boolean to false would weaken the stated controls. HSM_PURGE_RULE is not one of the documented OCI Vault secret-rule types. Therefore, C and D jointly satisfy both requirements.

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.

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.