Storage practice questions

OCI Data Transfer Appliance

Why wrong: Data Transfer Appliance is a physical offline data shipping device, not a network-based transfer tool.

OCI File Storage Service Mount Target

Why wrong: FSS mount targets are for cloud-native NFS access, not on-premises to cloud migration gateway caching.

OCI Archive Storage Uploader

Why wrong: No such dedicated standalone service exists by that exact name.

OCI Object Storage

Why wrong: Object Storage uses REST APIs and is not mounted via NFSv3.

OCI Archive Storage

Why wrong: Archive Storage is for long-term cold data retention with multi-hour retrieval times.

OCI Block Volume

Why wrong: Block Volume provides block storage typically attached to a single instance at a time in read-write mode.

Block Volume Backup

Why wrong: Backups create a full copy stored in Object Storage, which takes longer and is designed for disaster recovery.

Cross-Region Replication

Why wrong: Cross-Region Replication is used to replicate backups across regions, not for instant same-region point-in-time volume creation.

Volume Group Backup

Why wrong: Volume groups manage multiple volumes together, whereas a simple clone can be created directly from an individual volume.

Lower Cost

Why wrong: Lower Cost is optimized for sequential I/O workloads like backups where performance is secondary.

Ultra High Performance

Why wrong: OCI Block Volume features Balanced, Lower Cost, and Higher Performance tiers; Ultra High Performance is not an official tier name.

Balanced

Why wrong: Balanced is used for workloads that balance performance and cost, such as boot volumes and general-use databases.

Attach the Block Volume to multiple instances simultaneously across availability domains.

Why wrong: Block Volumes cannot be attached in read-write mode to multiple instances across availability domains concurrently.

Create a separate FSS file system in each availability domain and peer them.

Why wrong: FSS is regional, so a single file system can be accessed across all availability domains in the region.

Use an OCI FastConnect circuit to route NFS traffic between availability domains.

Why wrong: Intra-region FSS traffic does not require FastConnect; standard VCN routing and security lists are sufficient.

Apply an IAM policy stating that all PutObject API calls must pass customer secret keys in the header.

Why wrong: IAM policies govern authorization, not cryptographic key management selections.

Enable SSE-C (Server-Side Encryption with Customer-Provided Keys) on every individual file upload via CLI.

Why wrong: While SSE-C is supported, assigning a customer-managed key at the bucket level provides automated enforcement without requiring client-supplied keys per upload.

Write a custom OCI Functions script triggered by Object Storage events to re-encrypt objects using KMS.

Why wrong: Object Storage supports native KMS customer-managed keys without requiring custom event-driven functions.

Object Storage Lifecycle Policies

Why wrong: Lifecycle policies apply to Object Storage buckets, not FSS file systems.

FSS Object Versioning

Why wrong: Object Versioning is an Object Storage feature, not a File Storage Service feature.

Block Volume Volume Groups

Why wrong: Volume Groups are used for block storage consistency, not file storage.

Object Storage Standard Tier

Why wrong: Standard tier is designed for frequently accessed data requiring high performance.

Object Storage Infrequent Access Tier

Why wrong: Infrequent Access tier provides faster retrieval times but is more expensive than Archive Storage.

File Storage Service

Why wrong: File Storage Service is a network file system, not an object storage tier for long-term archiving.

Configure an event rule in OCI Events Service to trigger a function that modifies the storage tier after 30 days.

Why wrong: Lifecycle policies are built directly into Object Storage and do not require custom Event/Functions pipelines.

Set the bucket storage policy to automatically purge objects after 365 days and use Object Versioning to handle the 30-day tier shift.

Why wrong: Versioning manages object history, not tier transitions or automated lifecycle age-based transitions.

Create two separate rules: one for transition at 30 days and another rule evaluated independently for deletion at 335 days.

Why wrong: Deletion timing in lifecycle rules is calculated from the object creation date, meaning the second rule would need to specify 365 days, not 335.

The VCN lacks an Internet Gateway, and traffic is attempting to go over the public internet.

Why wrong: Access to Object Storage via a Service Gateway bypasses the internet, but lack of an IGW wouldn't cause 403s if internal routing is correct.

The bucket name is not globally unique within the tenancy.

Why wrong: OCI prevents duplicate bucket names within a namespace, so creation would fail rather than yielding a runtime 403 on GET.

The Object Storage bucket is configured in the Infrequent Access tier instead of Standard.

Why wrong: Tiering affects retrieval pricing and time, not access authorization resulting in 403 errors.

Object Storage Multipart Upload

Why wrong: Multipart upload is used for large object storage transfers, not block volume backups.

Individual Block Volume Backups triggered sequentially

Why wrong: Sequential backups will not guarantee crash consistency across multiple volumes.

FSS Snapshots

Why wrong: FSS snapshots apply to file storage, not block volumes.

5 TiB

Why wrong: 5 TiB is not the single PUT limit.

100 GiB

Why wrong: 100 GiB exceeds the single PUT limit.

Cross-Region Replication

Why wrong: Replication copies data to another region for disaster recovery, but doesn't inherently preserve overwrite history unless versioning is active.

Object Storage Lifecycle Management

Why wrong: Lifecycle management handles tiering and deletion, not version retention.

Bucket Retention Rules

Why wrong: Retention rules lock objects to prevent deletion or modification for compliance, but versioning specifically handles maintaining past versions upon overwrite.

Manually export the volume to an Object Storage bucket and download it in the second region.

Why wrong: While manual export/import is possible, it is not the recommended automated method.

Configure an OCI Object Storage lifecycle rule to replicate files across regions.

Why wrong: Lifecycle rules apply to Object Storage, not Block Volume backups.

Write an OCI Data Flow application to stream volume blocks across regions.

Why wrong: Data Flow is for Apache Spark processing, not block backup replication.

OCI IAM Federation

Why wrong: IAM federation is used for enterprise identity provider integration.

API Signing Keys

Why wrong: API keys are used for programmatic authentication by OCI users.

Object Storage Public Access Buckets

Why wrong: Public access makes all objects in a bucket readable to anyone on the internet, lacking granular time limits and targeted single-object control.

View the Storage Consumption metric in OCI Monitoring service aggregated by directory path.

Why wrong: OCI Monitoring tracks storage at the file system level, not broken down by internal directory paths.

Check the Object Storage Metrics explorer for FSS bucket utilization.

Why wrong: FSS is a file storage service, not an Object Storage bucket.

Enable FSS Analytics in the OCI Console under Storage Administration.

Why wrong: No such native feature as 'FSS Analytics' exists in the OCI console.

Delete the block volume while it is attached

Why wrong: OCI prevents deleting a block volume while it is actively attached to an instance.

Migrate the volume to a different availability domain

Why wrong: Block volumes cannot be migrated across availability domains while attached.

Convert a block volume into a File Storage Service mount target

Why wrong: Block storage cannot be converted directly into an FSS mount target.

Object Storage provides eventual consistency for bucket listing operations.

Why wrong: OCI Object Storage provides read-after-write consistency for all operations (PUT, GET, DELETE, and bucket listings), not eventual consistency.

Objects larger than 50 GiB must be stored using Block Volume instead.

Why wrong: Objects up to 10 TiB can be stored in Object Storage using multipart upload.

Block-level multi-attach with read-write access across availability domains

Why wrong: FSS uses NFS, not block multi-attach for block devices.

Automatic tiering from file storage to Archive Storage

Why wrong: FSS does not feature automatic tiering to Archive Storage.

Native integration with Block Volume replication policies

Why wrong: FSS and Block Volume are distinct storage services with separate management frameworks.

Directly mounting an Object Storage bucket as a local Windows NTFS drive via SMB protocol

Why wrong: Object Storage does not support native SMB mounting without third-party gateways.

Attaching an Object Storage bucket as an LVM logical volume to an on-premises server

Why wrong: Object storage cannot be formatted as an LVM logical volume.

Using Block Volume Export to push data into Object Storage buckets automatically

Why wrong: Block Volume export exports block backups, not arbitrary on-premises data streams.