In which two contexts can connectors be invoked in Pega, and what are their purposes?

In Pega, connectors are crucial for integrating and interacting with external systems. Their main purpose is to facilitate communication and data exchange between Pega applications and external data sources or services.

In this context, the most accurate response highlights that connectors can be invoked in data pages to pull data and in activities to push data. Data pages serve as a powerful way to retrieve and store data from external sources, allowing for efficient data management within Pega applications. They fetch data from various sources such as REST services, databases, or third-party APIs, providing a unified view of that data.

On the other hand, activities are used to execute a sequence of steps, and connectors can be called within these activities to send data back to external systems. This is especially useful for operations like submitting records, updating entries, or triggering processes in other applications.

The other choices do not accurately reflect the primary functions of connectors. For example, data tables are not directly involved in the invocation of connectors as they are more about storing data than retrieving or sending data. User interfaces primarily focus on displaying data rather than directly invoking connectors for data manipulation. This distinction clarifies why the right choice includes both data pages for retrieval and activities for data submission.