In Oracle Cloud Infrastructure (OCI), cross-region access is facilitated by configuring IAM policies that grant users or groups permissions to access resources in other regions. IAM policies in OCI are global, meaning they apply across all regions by default. However, an administrator can specifically configure these policies to allow or restrict access to resources in different regions.
Example: An administrator can write a policy that allows a user to manage compute instances in a specific region by including the region's name in the policy statement.
Reference:
Oracle Cloud Infrastructure Documentation: IAM Policies

Remote peering in Oracle Cloud Infrastructure allows two VCNs in different regions to communicate securely. To establish remote peering, the following components are required:
Two VCNs with Nonoverlapping CIDRs:
The CIDR blocks of the two VCNs must not overlap. This is crucial to avoid routing conflicts and ensure that traffic is correctly routed between the VCNs.
Dynamic Routing Gateway (DRG) Attached to Each VCN:
A DRG is a virtual router that provides a path for traffic between the VCN and networks outside the VCN, such as other VCNs via remote peering, on-premises networks, or other cloud services. Each VCN needs its own DRG.
Remote Peering Connection (RPC):
An RPC is a specialized connection on the DRG used specifically for remote peering. You need to create an RPC on each DRG associated with the VCNs you wish to peer.
Connection Between RPCs:
Finally, a connection must be established between the RPCs of the two DRGs. This connection facilitates the secure and private exchange of traffic between the VCNs over Oracle's backbone network.
Incorrect Options:
Option A involves a single VCN, which does not fulfill the requirement of remote peering between two VCNs.
Option B involves overlapping CIDRs and VPN gateways, which are incorrect for remote peering.
Option C suggests peering within the same region, which would be considered local peering rather than remote peering.
Relevant OCI Documentation:
OCI Remote VCN Peering
Dynamic Routing Gateway (DRG) Overview
These resources provide a detailed guide on configuring remote peering in OCI, ensuring secure and effective communication between VCNs across regions.

In Oracle Cloud Infrastructure (OCI), there are two primary types of capture filters used for network monitoring:
Flow Log Capture Filters: These filters are used to capture and log network flow information (e.g., source and destination IP addresses, ports, protocols). Flow logs provide insights into the traffic patterns within your VCN.
VTAP Capture Filters: Virtual Test Access Point (VTAP) capture filters allow you to capture and inspect traffic from specific network interfaces or subnets without affecting the flow of traffic. This is particularly useful for deep packet inspection and monitoring purposes.
Reference:
Oracle Cloud Infrastructure Documentation: Flow Logs
Oracle Cloud Infrastructure Documentation: VTAP

When performing a multipart upload using the Multipart Upload API in Oracle Cloud Infrastructure (OCI) Object Storage, the following points are true:
C . Each part can be as large as 50 GiB: OCI allows each part of a multipart upload to be up to 50 GiB in size. This enables the efficient uploading of large objects in smaller, manageable parts.
D . You can keep adding parts as long as the total number is less than 10,000: The Multipart Upload API supports up to 10,000 parts for a single object. This allows the upload of very large objects by dividing them into multiple parts.
Incorrect Statements:
A . After uploading all parts, you must commit the upload to finalize the multipart upload and combine all parts into a single object.
B . The object must be split into parts before uploading when using the Multipart Upload API.
Reference:
Oracle Cloud Infrastructure Documentation: Multipart Uploads

Oracle Cloud Infrastructure (OCI) Object Storage is a scalable, highly durable service that allows you to store any type of data in a secure and cost-effective manner. The correct and incorrect statements regarding OCI Object Storage are as follows:
A . Immutable Option: You can indeed set an immutable option for data in Object Storage using retention rules. This feature ensures that once data is written, it cannot be modified or deleted until the retention period expires, making it ideal for regulatory compliance.
C . Object Lifecycle Rules: Object lifecycle policies allow you to automate the archiving or deletion of objects based on their age or other criteria, helping manage storage costs and data retention efficiently.
D . Object Versioning: Versioning is enabled at the bucket level, not the namespace level. However, once enabled for a bucket, it helps retain, retrieve, and restore every version of every object stored in that bucket.
B . Object Storage Sharing Across Tenancies: This statement is not true. OCI Object Storage buckets and objects are specific to a tenancy and cannot be shared across different tenancies directly. Access to Object Storage resources is controlled within a single tenancy through IAM policies.
Relevant OCI Documentation:
OCI Object Storage Overview
Object Lifecycle Management
These references provide details on how Object Storage functions and the features available.