Which entity is responsible for encrypting data in transit using an IaaS model versus a SaaS model?

Cloud Application Developer and Cloud SLA Manager are not the primary entities responsible for shared responsibility model aspects of data encryption in transit in IaaS/SaaS scenarios.

Cloud Application Developer and Cloud SLA Manager are not the primary entities responsible for shared responsibility model aspects of data encryption in transit in IaaS/SaaS scenarios.

This option incorrectly assigns the responsibility; the Cloud Service Provider in IaaS only provides the underlying infrastructure, leaving data encryption to the customer, and the SaaS provider is responsible for the application and its data encryption.

Under the IaaS model, the customer manages the operating systems, applications, and data, making them responsible for implementing encryption for data in transit; conversely, with SaaS, the provider manages the entire application stack, including data handling, thus making the Cloud Service Provider responsible for encrypting data in transit.