What prevented the value type of field my_attribute from changing?

An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API. The Architect creates a new attribute my_attribute in the admin panel with frontend type select.

Later, the Architect sees that Productinterface already has the field my_atcribute, but returns an mc value. The Architect wants this field to be a new type that contains both option id and label.

To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:

After calling command setup:upgrade, the introspection of Productlnterface field xy_attribute remains int.

What prevented the value type of field my_attribute from changing?
A . The fields of Productlnterface are checked during processing schema.graphqls files. If
they have a corresponding attribute, then the backendjype of product attribute is set for field type.
B. The interface Productlnterface is already declared in Magento.CatalogGraphQI module. Extending requires use of the keyword -xceni before a new declaration of Productlnterface.
C. The Magento.CatalogGraphQI module occurs later in sequence than the Magento.GraphQI module and merging output of dynamic attributes schema reader overrides types declared in schema.graphqls

View Answer

Answer: C

Explanation:

products query is a GraphQL query that returns information about products that match specified search criteria. It also shows how to use ProductInterface fields to retrieve product data.

https://devdocs.magento.com/guides/v2.3/graphql/queries/products.html