Exam CCSP topic 1 question 218 discussion

Object storage systems are commonly accessed via cloud-specific APIs (e.g., Amazon S3), which can be proprietary. If a cloud customer builds their application tightly around a particular object's storage API, they risk becoming locked in to that vendor's ecosystem. Special consideration is needed to design in a way that minimizes this risk, such as abstracting the storage layer to allow for easier migration between vendors.

B. Object Object storage in a cloud environment requires special consideration on the part of the cloud customer to ensure they do not program themselves into a vendor lock-in situation. Object storage systems use a unique approach to store data, which involves the use of flat address spaces and metadata associated with each object. Different cloud providers implement their own proprietary APIs and storage protocols for object storage, making it more challenging to move data between providers without significant effort or re-architecting.

It should be B. Object. This is because object storage uses a flat addressing structure for files, which means that the file paths and folder structures are not stored as metadata with the files, making it difficult to switch to another vendor without significant reconfiguration of the data

Unstructured storage for auxiliary files would not lock a customer into a specific provider Why unstructured is limited to auxiliary files ? could be all files...

Agree with the answer but the explanation's last sentence of "With volume and object storage, because the cloud customer maintains their own systems with IaaS, moving and replicating to a different cloud provider would be very easy." is a little off. cloud storage is almost entirely PaaS not IaaS except for ephemeral drives on VMs. You are almost always connecting to a PaaS cloud service even for volumes. They are PaaS storage they are just presented or formatted as volumes.