Which option is NOT a method for creating persistence in PDTs?

Creating persistence in Persistent Derived Tables (PDTs) in Looker is a key aspect of optimizing data modeling and performance. The correct choice focuses on understanding the methods that are explicitly used for managing when PDTs are refreshed or rebuilt.

Using a datagroup_trigger allows for controlling when the PDT should be rebuilt based on changes to the underlying data. This method takes advantage of datagroups, which can monitor specific tables for changes and trigger a rebuild accordingly.

The sql_trigger_value method enables the definition of custom SQL that determines whether a PDT should be treated as stale. If the SQL specified returns a value that changes, the PDT will be rebuilt during subsequent queries, ensuring that users have access to the most current data.

The persist_for parameter indicates how long the results of a PDT should be stored before being considered stale, allowing developers to manage the freshness of data efficiently without unnecessary computations.

Conversely, the instance_trigger is not a recognized method within the context of creating persistence for PDTs in Looker. This term does not align with the protocols outlined in LookML for managing PDTs, which may lead to confusion. Therefore, it does not contribute to ensuring the persistence of a PDT in the same way that the other options do. Understanding these distinctions