A developer has finished developing a new eCommerce site that is broken out into several different Kubernetes pods. In order to promote the new application to production, a storage location for static content that the site uses needs to be defined in the file.
Application requirements:
versioning
WORM
Replication
Which solution should the administrator choose?
- Objects
- Volumes
- Files with SMB
- Files with NFS
Answer(s): A
Explanation:
Object storage is a good fit for applications that require versioning, replication, and a write-once- read-many (WORM) access model. Since eCommerce sites often store a large amount of unstructured data such as images, videos, and other multimedia content, object storage can provide a scalable, cost-effective, and highly available solution.
Object storage is also a good fit for Kubernetes-based applications that use microservices architecture, as objects can be accessed from multiple pods at the same time, without the need for complex file system sharing. Additionally, object storage can be easily integrated with Kubernetes using operators or API calls.
On the other hand, while volumes and file storage solutions such as SMB and NFS can also store static content, they may not be the best fit for the given application requirements. Volumes are often limited in terms of scalability and replication, while file storage solutions may not provide the same level of versioning and WORM capabilities as object storage.
As a result, the best solution for the given application requirements is Object storage.
Note that the exact implementation and configuration of the object storage solution may vary based on factors such as performance, availability, and security requirements.
Reference:
https://next.nutanix.com/community-blog-154/maintaining-compliance-with-worm-for-nutanix- objects-33239
Reveal Solution Next Question