Question: In Intent-Driven Management for Mobile Networks, when specifying Expectation Objects without using identifiers, what format does the `objectContext` typically follow to filter and identify desired objects?
Option 1: A single attribute-value pair (e.g., "location: city_ABC")
Option 2: A context list with entries as a tuple of (attribute, condition, specific value)
Option 3: A hierarchical structure of object types and geographical locations
Option 4: A Boolean expression combining multiple object attributes
Explanation: The correct answer is Option 2 because, according to the principles outlined for managing expectations in mobile networks without relying on object identifiers, the `objectContext` is structured as a context list. Each entry within this list is a tuple that contains three crucial elements: an attribute (defining what aspect of the object is being filtered), a condition (specifying how the attribute should match, e.g., equals, contains), and a value range (the specific value or set of values the attribute should meet to filter in the desired objects). This structured approach allows for precise and flexible identification of objects based on various criteria.