1z0-1072-25 Oracle Cloud Infrastructure 2025 Architect Associate Questions and Answers

In Oracle Cloud Infrastructure (OCI), when a block volume is detached from an instance, its performance level is automatically adjusted to the "Lower Cost" tier, which provides 0 VPUs (Volume Performance Units) per GB. This adjustment helps reduce costs when the block volume is not actively being used by a compute instance.

Key Points:

Volume Performance Levels: OCI offers various performance tiers for block volumes, including "Higher Performance," "Balanced," and "Lower Cost." These tiers determine the level of IOPS (Input/Output Operations Per Second) and throughput available to the volume.

Automatic Adjustment: When a block volume is detached from an instance, OCI automatically optimizes the cost by switching the volume to the "Lower Cost" performance tier. This tier offers minimal performance, suitable for data that is not actively accessed.

Cost Management: This automatic adjustment is beneficial for managing costs, as it prevents users from incurring unnecessary charges for higher performance levels when the volume is not in use.

Oracle Cloud Infrastructure (OCI) File Storage Service offers robust encryption capabilities to ensure data security.

B. Customer-Managed Encryption: Customers can choose to encrypt their data using their own keys stored in the OCI Vault service. This gives customers control over their encryption keys and enhances data security.

D. Oracle-Managed Encryption: By default, all data stored in OCI File Storage is encrypted using Oracle-managed keys. This ensures that data is encrypted at rest without requiring any action from the customer.

Incorrect Statements:

A. Communication is not encrypted via HTTPS when accessing file systems; instead, encryption in transit is typically managed via NFS over TLS.

C. Encryption of communication to a mount target is handled via network configurations, not through export options.

For a fully redundant connection from an on-premises data center to a VCN in the OCI us-ashburn-1 region, it is important to ensure high availability and fault tolerance. Here's how each option contributes to redundancy:

Option B: Two FastConnect Virtual Circuits:

FastConnect provides a dedicated, private connection with higher bandwidth and more consistent performance compared to a VPN. To achieve redundancy, you can configure two FastConnect circuits in the same region (us-ashburn-1), each terminated on diverse hardware on-premises. This setup ensures that even if one circuit or its associated hardware fails, the other circuit can maintain the connection. This ensures no single point of failure in the connectivity to OCI. Thus, option B is correct.

Option D: FastConnect and Site-to-Site VPN:

Another approach to redundancy is to have a mix of connection types. By setting up one FastConnect circuit and one Site-to-Site VPN, both terminating in the same region (us-ashburn-1), you create a diverse connection path. If the FastConnect connection fails, traffic can automatically route through the VPN connection, maintaining connectivity. This setup adds an extra layer of redundancy, making option D correct as well.

Incorrect Options:

Option A: Only configuring a Site-to-Site VPN from a single on-premises CPE does not provide redundancy because it involves just one connection path. If that connection or the CPE fails, there would be no fallback.

Option C: Configuring FastConnect circuits to different regions (us-ashburn-1 and us-phoenix-1) does not provide redundancy within a single region but rather across regions, which is not required for regional redundancy.

Relevant OCI Documentation:

OCI FastConnect Overview

Using Site-to-Site VPN and FastConnect for Redundancy

These references offer more detailed information on setting up redundant connections and the benefits of each connection type within OCI.

=================

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.

In Oracle Cloud Infrastructure (OCI), block volumes are designed to be highly flexible and can be used in various ways:

A. Restoring from a volume backup to a larger volume: This is supported and allows for resizing during the restoration process.

B. Cloning an existing volume to a new, larger volume: You can clone a block volume and specify a larger size for the new volume.

C. Expanding an existing volume in place with offline resizing: OCI allows you to increase the size of an existing block volume without needing to take it offline.

Option D is NOT valid because block volumes can only be attached to compute instances within the same availability domain. Cross-availability domain attachment of block volumes is not supported directly.

On-demand capacity is the compute capacity type in Oracle Cloud Infrastructure (OCI) that allows you to provision and use compute instances whenever needed, without any long-term commitment. This flexibility is ideal for various workloads, including development, testing, and production environments, where immediate availability and scalability are crucial.

Key Points:

On-Demand Capacity: On-demand compute instances provide users with the flexibility to spin up instances as required and only pay for the time the instances are running. This model is most suitable for workloads with unpredictable usage patterns or short-term requirements.

Flexibility and Scalability: With on-demand capacity, you can quickly scale your resources up or down based on your application's needs, ensuring that you only pay for the resources you actually use.

No Commitment: Unlike reserved capacity, on-demand capacity does not require any long-term commitment or upfront payment, making it an attractive option for organizations looking to avoid capital expenditures.

In Oracle Cloud Infrastructure (OCI), to ensure high availability and distribution across Availability Domains (ADs), the recommended approach is as follows:

Capacity Reservations for High Availability: To achieve high availability, especially across all three Availability Domains in a region, you should create three capacity reservations. Each reservation corresponds to one AD, ensuring that your instances or resources are evenly distributed and resilient to AD-level failures.

Why Three: This setup provides redundancy and load distribution across the ADs, meeting the high availability requirements.

Relevant OCI Documentation:

Capacity Reservations

This document outlines how to create and manage capacity reservations to meet high availability and fault tolerance requirements.

=================

Restoring a block volume from a backup in OCI provides flexibility and options for scaling and recovery:

Restoring to a Larger Volume Size: When restoring a block volume from a backup, you have the option to restore it to a volume that is larger than the original. This is particularly useful if you anticipate needing more storage capacity after the restore.

Full and Incremental Backups: OCI supports both full and incremental backups. You can restore from any backup type, which makes it possible to restore data efficiently depending on the backup strategy used.

Multiple Restores: Multiple volumes can be restored from a single backup, providing flexibility in disaster recovery scenarios.

Availability Domain: The restored volume can be created in any availability domain within the same region, not necessarily the same one where the original volume was located.

Relevant OCI Documentation:

Block Volume Service Overview

Restoring a Block Volume

These references explain the process and options available for restoring block volumes from backups.

=================

Setting up a Site-to-Site VPN on Oracle Cloud Infrastructure offers several key benefits related to connectivity and reliability:

Static or Dynamic Routing (BGP): OCI allows customers to configure Site-to-Site VPN with either static routing or dynamic routing using Border Gateway Protocol (BGP). This flexibility enables customers to choose the routing method that best suits their network configuration and requirements.

Redundant VPN Tunnels: OCI automatically provisions redundant VPN tunnels when you set up a Site-to-Site VPN. These redundant tunnels ensure high availability and fault tolerance, so if one tunnel fails, traffic can continue to flow through the other tunnel without interruption.

Bandwidth Considerations: While the VPN provides a reliable connection, it typically does not exceed 2 Gbps in bandwidth. Higher bandwidth connections usually require FastConnect.

Private Connection: The VPN does create a secure and private connection between on-premises data centers and OCI, but it does not inherently provide a consistent network experience in the way that a dedicated connection like FastConnect does.

Relevant OCI Documentation:

Site-to-Site VPN Overview

Configuring Routing for VPNs

These references detail the benefits and technical specifications of setting up Site-to-Site VPNs on OCI.

=================

In Oracle Cloud Infrastructure (OCI), understanding how private IP addresses work is crucial for configuring network interfaces and managing instances within your Virtual Cloud Network (VCN).

Primary VNIC and Private IP Address:

When an instance is launched in OCI, it is attached to a Virtual Network Interface Card (VNIC). The primary VNIC, which is automatically created during the instance launch, is associated with a primary private IP address by default. This private IP address is essential for the instance to communicate within the VCN. The primary private IP address is automatically assigned and cannot be removed from the primary VNIC while the instance is running. This supports the statement C.

Additional Private IPs:

Contrary to statement B, each VNIC can indeed have multiple private IP addresses, but by default, the primary VNIC comes with only one primary private IP. You can manually add secondary private IPs if needed. However, the additional IPs are not assigned by default; hence, A is incorrect.

Public IP Association:

For instances requiring internet access, a public IP address can be optionally assigned to the private IP address if the instance is in a public subnet. This is critical for scenarios where an instance needs to communicate with the internet or external networks. This aligns with statement D.

Relevant OCI Documentation:

Oracle Cloud Infrastructure Networking Overview

VNICs and Private IPs

These references provide additional context and detail on how private IP addresses work within OCI and clarify the correct statements.

=================

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.

=================

For an online trading platform requiring high availability and fault tolerance, it's critical to ensure data durability and avoid any costly service disruptions. In Oracle Cloud Infrastructure (OCI), Object Storage is often used to store critical data, such as transaction logs or user data, due to its scalability, durability, and reliability.

Option B is the most suitable approach for ensuring data durability and availability across regions. Here's why:

Cross-Region Replication (CRR): OCI offers a feature called Cross-Region Replication for Object Storage. This feature allows you to automatically and asynchronously replicate objects in a bucket from one OCI region to another. This setup ensures that even if one region experiences a failure, the data is still available in another region, thereby meeting the requirements for high availability and fault tolerance.

Data Durability: By replicating data to another region, you protect against regional outages. OCI guarantees 99.95% availability for replicated data, which is critical for a financial firm's trading platform where data consistency and durability are paramount.

Disaster Recovery: With data replicated in another region, the trading platform can quickly switch to using the data in the secondary region in case of a disaster in the primary region. This setup significantly reduces recovery time objectives (RTO) and ensures business continuity.