Considering a template with caching and a remote include without caching, which part is cached?

The correct choice indicates that while the remote include portion is not cached, the rest of the page benefits from caching. In B2C Commerce, caching is a mechanism used to improve performance by storing frequently accessed data, such as HTML content, so that it doesn’t have to be recreated from scratch upon each request.

When a page template is set up with caching, it means that static components of the page can be stored and served quickly to end users. In contrast, a remote include is typically dynamic in nature, often pulling in real-time data or content from another location. Because of its dynamic aspect, the remote include portion is designed to be uncached to ensure users are seeing the most current information.

Thus, opting for caching on the rest of the page means that any static elements can still be served efficiently, while ensuring that the dynamic elements—represented by the remote include—are always up-to-date. This set-up allows for a balance between performance and the need for real-time content delivery.

In summary, the distinction made in the correct choice highlights the combination of caching for static portions of the page while appropriately allowing real-time content to be retrieved, ensuring that users receive accurate and current information.