HPE2-CP08 Implementing Object Storage for Active Archive Questions and Answers

A customer needs a solution that provides the highest availability with the lowest overhead. They have a single availability zone and twelve servers in their RING and want to be able to continue data access from the Scality RING even when three storage servers are unavailable.

Is this an Erasure Coding schema that will meet their requirements?

Solution:Erasure Coding (6,3)

Does this customer scenario represent a sweet spot for object storage using the Scality S3 Backup Operations interface?

Solution:backup data of 80-230 TB daily in an 8-12 hour backup window

A large organization is experiencing exponential object storage data growth and wants to optimize costs at a petabyte scale. Should this product be recommended to help the customer control costs with on-premises software-defined storage?

Solution:HPE Synergy 660 Gen10 compute modules with 3PAR All-Flash Arrays

Does this describe object storage?

Solution:optimized filesystem protocol

Is this the minimum amount of archive data where a combination of iCAS and Scality should be positioned?

Solution:50-150 TB with 10% growth

When implementing Scality RING, is this monitoring option provided by the StandardMonitoring service?

Solution:Availability Assurance

A customer is discussing the use of object storage for backup and recovery using Scality. Does this statement describe a best practice?

Solution:Most recent data is written to a storage pool of the backup vendor and all other backup data is migrated to the Scality Ring.

Is this statement correct when describing S3 Cloud Storage?

Solution:S3 functionality is best for random data access.

Is this a customer challenge that an enterprise object storage solution can address?

Solution:high cost to store non-mission critical long-retention data

Is this a design criteria when sizing a fully-populated HPE Apollo 4510 with 68 drives for a CEPH object storage environment?

Solution:Configure RAID1 volumes across two drives at a time to reduce CPU load.