@AnilKumarTechy Yes, your understanding is correct. In a typical Pega deployment using Kubernetes (especially in Pega Cloud 3 or any modern containerized setup), the application artifacts like rules, data schema, and static resources are stored centrally in the database or shared file systems. All pods in the deployment access the same shared resources, which ensures consistency across the environment. This design allows you to scale horizontally (add more pods) without needing to replicate artifacts manually. Each pod pulls the latest data and rule artifacts from the shared storage or database, so there’s no risk of version mismatch. Therefore, artifacts are effectively shared across all pods in the deployment.