What are two reasons that an architect should recommend ECS when a customer is considering an object platform to refresh a Centera infrastructure? (Select 2)

Question

Options

• AECS CAS enables CAS SDK-based client applications to use ECS as a storage target without
• BECS natively supports all Centera features, including Single Instance Storage and Data Shredding.
• CECS supports Centera CAS and S3 API data access within the same bucket.
• DECS supports the same retention features as Centera for applications using the CAS API, including

• A
  80% (24)
• B
  7% (2)
• C
  13% (4)

Explanation

A is correct because ECS's CAS compatibility layer allows existing Centera/CAS SDK-based applications to redirect to ECS as a storage target with no code modifications - eliminating the costliest part of a migration. D is correct because ECS replicates Centera's retention model (Governance and Compliance modes) when accessed via the CAS API, making it a compliant drop-in replacement for regulated data environments.

B is wrong because ECS does not natively support all Centera features - notably, Single Instance Storage (deduplication) and Data Shredding (secure erasure) are Centera-specific capabilities that ECS either handles differently or does not fully replicate. Overstating compatibility is a classic exam trap.

C is wrong because ECS does not allow CAS and S3 API access within the same bucket - they operate in separate namespaces. Mixed-protocol access within a single bucket is not supported.

Memory tip: Think "A = Apps don't break, D = Data retention holds" - the two pillars of a Centera refresh are application continuity and compliance continuity, which map directly to A and D.

No community discussion yet for this question.