Free 1Z0-1072-26 Practice Test Questions and Answers (2026)

OCI File Storage is an availability-domain-scoped resource; a file system resides within a single AD and does not automatically span ADs or regions. To achieve data durability and high availability beyond a single AD/region, File Storage supports snapshots and File System Replication. Snapshots capture point-in-time consistent states, and OCI's replication/cross-region copy capability lets you replicate those snapshots to file systems in other availability domains or regions. This provides a recoverable, durable copy without manual intervention. Among the options, configuring snapshots with OCI's cross-region replication of snapshots is the officially supported, automated mechanism ensuring both durability (redundant copies) and high availability (recoverable targets in separate failure domains), making option A the most correct and directly applicable approach.

B. Manual replication is error-prone, not automated, and not an officially recommended HA mechanism for durability.

C. False—File Storage has no "default replication policy" that auto-replicates across all ADs; file systems are AD-scoped.

D. Object Storage is a different service; substituting it does not make File Storage highly available.

1. Oracle Cloud Infrastructure Documentation, File Storage Overview — "Resource Availability" and "Availability Domain" scoping of file systems.

2. Oracle Cloud Infrastructure Documentation, Using File System Replication — replication of file systems/snapshots across availability domains and regions.

3. Oracle Cloud Infrastructure Documentation, Managing Snapshots — point-in-time snapshot creation and consistency.

4. Oracle Cloud Infrastructure Documentation, File Storage Scenarios / Disaster Recovery — recommended durability and HA patterns using snapshots and replication.

5. Oracle Cloud Infrastructure Documentation, Regions and Availability Domains — AD-level isolation and fault domain concepts.

The OCI Cross-Region File Storage Sync service is specifically designed for data replication across regions. This aligns with the need for redundancy and availability in disaster recovery planning.

A. OCI Object Storage's features do not apply to File Storage replication directly.

B. OCI Data Guard is not used for file system replication; it is primarily for databases.

D. Manual snapshots and clones are not optimal and may incur downtime.

- Oracle Cloud Infrastructure Documentation, "OCI File Storage Service," available at https://docs.oracle.com/en/iaas/Content/File/Concepts/overview.htm (Section: File Storage Service Overview).

- Oracle Cloud Infrastructure Documentation, "Replication Overview," available at https://docs.oracle.com/en/iaas/Content/File/Tasks/replicating.htm (Section: Replication Strategy).

Oracle Cloud Infrastructure (OCI) File Storage Service (FSS) is a fully managed, elastic file system that scales automatically as data is added. For billing and metering purposes, usage is calculated based on the actual storage capacity consumed by file system data and snapshot data over time, measured in gigabyte-hours (GB-hours). Metering runs periodically throughout the billing cycle to record storage utilization, taking into account the peak storage capacity consumed within each billing window. Users are charged solely for the capacity allocated by their files and snapshots without needing to pre-provision storage capacity in advance.

A. File Storage capacity is elastic and not pre-provisioned, meaning users do not pay for fixed provisioned storage capacity regardless of actual usage.

B. Inbound data transfers are free, and billing for File Storage itself depends on consumed storage capacity rather than internal file transfer volume.

D. Metering is based on the total byte-hours of storage capacity consumed by file systems and snapshots, not simply the total count of created snapshots.

- Oracle Cloud Infrastructure Documentation, "File Storage Service Concepts and Metering", Section: Billing for File Storage, 2024.

- Oracle Cloud Infrastructure FAQ, "File Storage FAQ: How is File Storage metered?", 2024.

The OCI File Storage service (FSS) is a fully managed, enterprise-grade, regional file system that natively supports Network File System (NFSv3) protocols. It allows thousands of compute instances across different availability domains within the same region to access shared storage concurrently with high durability and scalability. Using OCI File Storage directly satisfies requirements for POSIX-compliant shared file access for Linux instances while delivering consistent high performance and robust security control via Network Security Groups (NSGs), Security Lists, and export options. It eliminates the operational overhead and performance bottlenecks associated with third-party software, Object Storage mounts, or multi-attach block volume configurations across availability domains.

Option B: Block volumes are block-level storage devices designed for single instances or multi-attach read-only scenarios, not concurrent multi-AD shared file systems.

Option C: Building a custom third-party shared file system introduces unnecessary architectural complexity, higher operational overhead, and potential performance bottlenecks compared to managed FSS.

Option D: Object Storage is designed for unstructured object data via REST APIs; mounting it as a filesystem yields poor performance for shared transactional file workloads.

- Oracle Cloud Infrastructure Documentation, "Overview of File Storage," Storage Section. https://docs.oracle.com/en-us/iaas/Content/File/Concepts/filestorageoverview.htm

- Oracle Cloud Infrastructure Documentation, "Mounting File Systems," File Storage Service User Guide. https://docs.oracle.com/en-us/iaas/Content/File/Tasks/mountingfilesystems.htm

Oracle Cloud Infrastructure (OCI) Block Volume cross-region replication provides automated, asynchronous continuous replication of block and boot volumes to a secondary target region. To align with robust disaster recovery (DR) objectives and maintain a low Recovery Point Objective (RPO), automating cross-region replication ensures that data updates are continuously and automatically synchronized without requiring manual operator intervention. This automated background synchronization maintains data consistency across regions, ensuring high availability and seamless data restoration during regional outages. Setting up automated replication schedules or continuous replication policies guarantees that critical workload storage remains synchronized, minimizing potential data loss and enabling rapid failover in disaster recovery scenarios.

A. Non-critical workloads do not prioritize disaster recovery; cross-region replication is primarily intended for protecting mission-critical enterprise applications and data.

B. Manual snapshots require human intervention, making them prone to delay, increased RPO, and inconsistency compared to automated, continuous cross-region replication mechanisms.

D. Selecting the lowest performance tier blindly can severely degrade DR failover application performance, violating Recovery Time Objectives (RTO) and operational SLAs.

- Oracle Cloud Infrastructure Documentation, "Replicating a Volume Across Regions", OCI Block Volume Service Guide, Section: Storage - Block Volume Replication.

- Oracle Cloud Infrastructure Documentation, "Volume Groups and Cross-Region Replication", OCI Core Services Guide, Section: Disaster Recovery for Block Volumes.

In Oracle Cloud Infrastructure Identity and Access Management (OCI IAM), Authentication (AuthN) and Authorization (AuthZ) represent two fundamental security controls. Authentication is the process of confirming the claimed identity of a user, service, or system component using credentials such as passwords, multi-factor authentication (MFA) tokens, or API signing keys. Once identity is successfully validated, Authorization determines the specific actions, permissions, and privileges granted to that authenticated identity. AuthZ evaluates IAM policies, group memberships, and compartment scopes to grant or deny access to OCI resources. Thus, AuthN addresses identity verification ("who you are"), while AuthZ governs resource access control ("what you are permitted to do").

Option B: This option reverses the definitions; AuthN verifies user credentials to establish identity, whereas AuthZ evaluates permissions and roles.

Option C: Both AuthN and AuthZ apply universally across all user categories, including administrators, system services, and end-users alike.

Option D: AuthN and AuthZ describe distinct operational stages in security; authentication confirms identity, whereas authorization controls privilege boundaries.

- Oracle Cloud Infrastructure Documentation, "Overview of Identity and Access Management", Section: Authentication and Authorization Framework, Doc ID: OCI-IAM-100. https://docs.oracle.com/en-us/iaas/Content/Identity/Concepts/overview.htm#Auth

- IEEE Standard for Identity and Access Management Framework, IEEE Std 2830-2021, DOI: 10.1109/IEEESTD.2021.9442807.

In Oracle Cloud Infrastructure (OCI), compartments are fundamental logical constructs used to organize and isolate cloud resources such as compute instances, VCNs, and storage volumes. Unlike physical hardware partitioning, compartments are logical boundaries that do not impact hardware performance or physical separation. They allow organizations to enforce the principle of least privilege through Identity and Access Management (IAM) policies. By defining access policies scoped to specific compartments, administrators can grant users access only to the resources necessary for their roles. Furthermore, compartments simplify resource management, cost tracking, and administrative governance across different business units, project teams, and environments without requiring separate tenancy infrastructures.

A. Compartments are purely logical administrative constructs and do not physically separate cloud hardware, servers, or underlying physical infrastructure in OCI regions.

B. Compartments do not automatically replicate resources across regions; cross-region disaster recovery requires explicit service configurations such as database replication or volume backups.

D. Compartments are management and security boundaries for access control, and do not allocate additional compute capacity or increase the processing power of resources.

- Oracle Cloud Infrastructure Documentation, "Identity and Access Management: Overview of Compartments", Section "Managing Access and Security".

- Oracle Cloud Infrastructure Documentation, "Security Guide: Compartment Design Best Practices".

Oracle Cloud Infrastructure Identity and Access Management (IAM) policies are declarative statements that define access control across resources. The primary function of IAM policies is to specify who can access which specific OCI resources and the precise actions or methods by which they can access them. Policies follow a strict structure consisting of subject groups, verbs representing permissions (such as inspect, read, use, and manage), resource types, and compartments or tenant boundaries. Through granular policy definitions, administrators enforce the principle of least privilege, ensuring authorized entities possess only necessary operational rights while restricting unauthorized access across compartments, tenancy environments, and cloud infrastructure services.

Option B: Encryption at rest and in transit is managed by Oracle Key Management Cloud Service (KMS), TLS protocols, and default storage encryption settings, not IAM access control policies.

Option C: Compute shape specifications and resource allocation mechanisms manage CPU and memory allocation for OCI services, whereas IAM policies strictly govern authorization permissions.

Option D: Monitoring, tracking availability, and collecting metrics for OCI services are handled by OCI Monitoring, Telemetry, and Alarm services rather than IAM access control policies.

- Oracle Cloud Infrastructure Documentation, "Overview of Identity and Access Management", Access Control Concepts and Policy Syntax Section.

- Oracle Cloud Infrastructure Documentation, "How Policies Work", Declarative Policy Structure and Verb Authorization Rules.

OCI Security Zones and OCI Cloud Guard work together to deliver comprehensive security posture management across an OCI tenancy. Security Zones are associated with compartments to strictly enforce security policies, automatically preventing users from making non-compliant configuration changes or creating insecure resources within critical workloads. Meanwhile, Cloud Guard offers enterprise-wide visibility by continuously monitoring resources, configurations, and user activity across tenancy compartments. It automatically detects potential security threats and misconfigurations, providing automated or guided remediation through detector and responder recipes. Activating Cloud Guard alongside enforcing Security Zones creates a strong defense posture combining active policy prevention with continuous monitoring and automated threat response.

A. Security Zones enforce preventative security policy recipes on compartment resources, not dynamic adjustment of NSG rules based on traffic patterns.

B. Security Advisor assists in deploying resources aligned with security best practices using guided workflows, not sending manual daily security report emails.

C. Cloud Guard monitors target resources across entire compartments or tenancies, including compute, storage, and IAM, not exclusively VCN network traffic.

- Oracle Cloud Infrastructure Documentation, "Cloud Guard Concepts", Section: "Detector and Responder Recipes".

- Oracle Cloud Infrastructure Documentation, "Overview of Security Zones", Section: "Security Zone Policies and Compartments".

- Oracle Cloud Infrastructure Documentation, "Overview of Security Advisor", Section: "Using Security Advisor to Deploy Resources".

Oracle Cloud Infrastructure Object Storage provides Object Lifecycle Management to automate the archival, reclassification, or deletion of stored data according to user-defined lifecycle rules. By establishing lifecycle policies at the bucket level, organizations can define conditions based on object age or prefix matches to automatically transition objects from high-performance Standard storage to cost-effective Infrequent Access or Archive tiers. This automated tiering process eliminates the need for manual data management, ensuring that data is stored on the most cost-effective tier throughout its lifecycle while optimizing storage expenditure and maintaining operational efficiency without affecting application availability or requiring custom scripting.

Option B: Manually copying objects between tiers requires active operational effort, script management, and elevated administrative overhead, failing to provide automated policy-driven lifecycle transition.

Option C: Storage Gateway facilitates local file system access to cloud object buckets but does not automate tiering rules directly within OCI Object Storage buckets.

Option D: Increasing storage capacity expands available bucket quota or space but does not configure automated data movement or lifecycle tiering between storage classes.

- Oracle Cloud Infrastructure Documentation, "Object Lifecycle Management", Section: Automating Object Tiering and Expiration Policies, Reference Doc ID: oci-object-lifecycle.

- Oracle Cloud Infrastructure Documentation, "OCI Object Storage Overview", Section: Storage Tiers and Policy Management.