CertSafari
    Snowflake SnowPro Advanced: MLOps Engineer (MLA-B01)· Lessons

    Domain 5 · Lesson 15/17

    Privileges for Feature Store, Model Registry and compute pools

    Enforce Snowflake security policies.

    12 min read
    5.33% of exam
    6 sources
    Published 20 Oct 2026
    Docs as of 18 Oct 2026

    What you will be able to do

    • Grant the minimum privileges for Feature Store producer and consumer roles, including grants that cover feature views created later
    • Fix a feature view registration that fails because change tracking is off on a source table owned by another role
    • Choose between OWNERSHIP, USAGE and READ on a registered model for each kind of inference
    • Decide which compute pool privilege a role needs to run, operate, inspect or own ML compute
    • Identify which object each ML component's privileges are granted on, and which role grants them

    Key concept

    ML assets are governed as ordinary Snowflake objects — Feature stores, models and compute pools are schema- or account-level objects. You control access to them with the same role-based grants used for tables and warehouses, and you usually arrange those grants in a role hierarchy rather than granting them user by user.

    1.Producer and consumer roles on a Feature Store schema

    A Feature Store has two kinds of user, and each gets its own role. Producers create and operate feature views. Consumers only read feature views and entities. A Feature Store is a schema (see Feature Store schema and entities (join keys)), and its feature views are dynamic tables or views. That makes every Feature Store permission a grant on that schema or on the objects inside it. There is no separate ML permission model to learn.

    The consumer minimum is short. It covers USAGE on the database and schema, SELECT and MONITOR on the schema's dynamic tables, SELECT and REFERENCE on its views, and USAGE on the warehouse passed to the feature store initializer. None of these grants touches the source tables behind the feature views. A consumer reads what the store has already materialized. Consumers who also build training datasets need more: CREATE TABLE and CREATE DATASET on the destination schema, SELECT and REFERENCE on the tables there, and USAGE on the DATASETs.

    Producers hold everything a consumer holds and add the privileges that create and run feature views. They need CREATE DYNAMIC TABLE, CREATE VIEW and CREATE TAG on the Feature Store schema, CREATE TABLE and CREATE DATASET for training data, OPERATE on the schema's dynamic tables and tasks to manage refresh settings, and USAGE on the warehouse. Producers inherit the consumer grants through the role hierarchy, not through duplicate grants. The setup script grants the consumer role to the producer role and the producer role to SYSADMIN.

    Feature Store privileges by role
    PrivilegeGranted onConsumerProducer
    USAGEFeature store database and schemaRequiredRequired (inherited)
    SELECT, MONITORDynamic tables in the schemaRequiredRequired (inherited)
    SELECT, REFERENCEViews in the schemaRequiredRequired (inherited)
    USAGEWarehouse passed to the initializerRequiredRequired
    CREATE DYNAMIC TABLE, CREATE VIEW, CREATE TAGFeature store schemaNot grantedRequired
    CREATE TABLE, CREATE DATASETFeature store or destination schemaOptional, for training datasetsRequired for training datasets
    OPERATEDynamic tables and tasks in the schemaNot grantedRequired to manage refresh

    Producers add new feature views all the time, so consumer grants must reach objects that do not exist yet. The setup script grants each object privilege twice. The ON ALL grant covers dynamic tables, views and datasets that already exist, and the ON FUTURE grant covers the ones producers create later. Without the FUTURE grant, every new feature view stays invisible to consumers until an administrator runs another GRANT.

    Consumer grants from the Feature Store setup script: ALL for existing objects, FUTURE for objects producers add latersql
    -- Grant CONSUMER role privileges
    GRANT USAGE ON DATABASE IDENTIFIER($FS_DATABASE) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    GRANT USAGE ON SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    
    GRANT SELECT, MONITOR ON FUTURE DYNAMIC TABLES IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    GRANT SELECT, MONITOR ON ALL DYNAMIC TABLES IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    
    GRANT SELECT, REFERENCES ON FUTURE VIEWS IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    GRANT SELECT, REFERENCES ON ALL VIEWS IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);

    Only a role with MANAGE GRANTS, CREATE ROLE and CREATE SCHEMA on the database can set all of this up. That can be ACCOUNTADMIN or a narrower custom role. From snowflake-ml-python 1.6.3, the setup_feature_store utility creates the producer and consumer roles and their grants in one call. With several feature stores, give each store, or each logical group of stores, its own producer and consumer pair.

    Access to any Snowflake ML component comes from privileges granted to roles, and what changes from one component to the next is the object the grant lands on. For a Feature Store, the grants sit on its schema and the dynamic tables and views inside it. For a registered model, the owner grants USAGE or READ on the model itself to the role that will call it. For a compute pool, the grants sit on the pool: USAGE to run work there, while creating a new pool takes CREATE COMPUTE POOL on the account. Grant to roles rather than to individual users, and give each role only the privileges its job needs.

    Checkpoint 1 of 6· Fill the gap

    Producers keep adding feature views to this Feature Store schema. The consumer role must be able to read the dynamic tables that exist now and also the ones producers create later, without anyone running another GRANT. Which keyword completes the first statement?

    GRANT SELECT, MONITOR ON  ?  DYNAMIC TABLES IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);
    GRANT SELECT, MONITOR ON ALL DYNAMIC TABLES IN SCHEMA IDENTIFIER($SCHEMA_FQN) TO ROLE IDENTIFIER($FS_ROLE_CONSUMER);

    Checkpoint 2 of 6· Exam question

    A data science team needs a consumer role that can read feature views for batch inference in a Feature Store schema, but must not create or refresh feature views. Which set of grants is the minimal one?

    Sources123

    2.Change tracking on source tables you do not own

    An incremental feature view needs change tracking on its source tables, and turning it on is an owner's action. When the producer role owns the source tables, Snowflake enables change tracking automatically as the feature view is created. When another team's role owns them, registration fails with a 'change tracking is not enabled' error.

    You can fix this without taking the table away from its owner in two ways. The owning role can enable change tracking itself with one ALTER TABLE. The alternative is to transfer OWNERSHIP to the creating role, create the dynamic table so change tracking turns on automatically, and then transfer OWNERSHIP back. The ALTER TABLE route is the cleaner one, because ownership never changes hands.

    The source table's owner enables change trackingsql
    ALTER TABLE mydb.myschema.raw_orders SET CHANGE_TRACKING = TRUE;

    OPERATE does not solve this. OPERATE applies to the Feature Store's own dynamic tables and tasks, and it controls their refresh settings. It grants nothing on the upstream source table. A view over untracked tables raises the same error, so enable change tracking on the base tables that the view references.

    Checkpoint 3 of 6· Check yourself

    A producer role tries to register an incremental feature view on raw_orders, a table owned by another team's role. Registration fails with a 'change tracking is not enabled' error. Which fix resolves it while the other team keeps ownership of the table throughout?

    Checkpoint 4 of 6· Exam question

    A producer role registers a feature view with incremental refresh over a source table owned by another team's role. Registration fails because change tracking is not enabled on the source table. What resolves this while keeping ownership with the other team?

    Sources14

    3.OWNERSHIP, USAGE and READ on registered models

    A registered model has exactly three privileges. The difference between USAGE and READ follows where inference runs. USAGE allows warehouse inference and SHOW commands but blocks the code, weights and artifacts. READ allows inference on Snowpark Container Services (SPCS) and access to the model files. OWNERSHIP covers everything else: managing versions, updating metadata and granting the other two privileges.

    Model object privileges
    PrivilegeAllowsDoes not allow
    OWNERSHIPManaging model versions, accessing artifacts, updating metadataBeing held by more than one role at a time
    USAGEWarehouse inference, SHOW MODELS, SHOW VERSIONS IN MODELModel code, weights or other artifacts
    READSPCS inference, model files and metadata, SHOW MODELS, SHOW VERSIONS IN MODELManaging versions or updating metadata
    The model owner grants inference access to a production rolesql
    GRANT USAGE ON MODEL my_model TO ROLE prod_role;
    -- OR
    GRANT READ ON MODEL my_model TO ROLE prod_role;

    Only one role can own a model. Shared control comes from granting that owning role to several users or roles. This matters once promotion to production is someone else's job. When production lives in a separate schema, the role that copies a version into it needs OWNERSHIP or READ on the source model. USAGE is not enough, because USAGE cannot reach the artifacts.

    Checkpoint 5 of 6· Check yourself

    Data scientists own a model in a development schema. A separate platform role will copy approved versions into a production schema and serve them on Snowpark Container Services, but it must not take ownership of the source model. Which privilege on the source model should the model owner grant to the platform role?

    Sources2

    4.Privileges for ML compute pools

    Compute pools supply the container compute for ML Jobs and SPCS services, and each pool privilege matches one job function. USAGE lets a role run services and jobs on the pool. OPERATE lets it suspend and resume the pool. MODIFY lets it change the pool's properties. MONITOR lets it see the pool and what is running there. OWNERSHIP gives full control and, as with models, belongs to one role at a time.

    Compute pool privileges and the ML role that typically needs each
    PrivilegeEnablesTypical holder
    USAGERunning a service or a job; communicating with the serviceData scientists submitting ML Jobs, inference services
    OPERATESuspending or resuming the compute poolPlatform operators
    MODIFYAltering the compute pool and setting propertiesPlatform administrators
    MONITORViewing pool usage, properties, and listing poolsObservability and cost reviewers
    OWNERSHIPFull control; one role at a timeThe platform team that created the pool

    USAGE on the pool alone does not let a role run an ML Job. The role also needs USAGE on the database and schema where the job runs, CREATE SERVICE on that schema, and USAGE on a stage for the job payload. If the stage does not exist yet, the role needs CREATE STAGE so the job can create it. The role also needs privileges on whatever tables and warehouses the workload reads. Creating a new pool instead of reusing one takes CREATE COMPUTE POOL on the account.

    Checkpoint 6 of 6· Check yourself

    An ML Job will run on an existing compute pool. The data scientist's role already holds USAGE on that pool, on the job's database and schema, and on the payload stage, plus SELECT on the tables the job reads. Which grant is still missing before the role can run the job?

    Sources56

    Sources

    (6)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “Consumers can read information about feature views and entities in the feature store.”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “SELECT and REFERENCE on views in the feature store schema.”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “OPERATE on the dynamic tables and tasks in the feature store schema to manage Feature View refresh settings.”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “GRANT ROLE IDENTIFIER($FS_ROLE_CONSUMER) TO ROLE IDENTIFIER($FS_ROLE_PRODUCER);”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “A role with MANAGE GRANTS, CREATE ROLE, and CREATE SCHEMA ON DATABASE <DB> privileges is needed to configure the necessary Feature Store roles”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “snowflake-ml-python package version 1.6.3 and later include a setup_feature_store utility API”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “the source tables must have change tracking enabled, or the user must have OWNERSHIP of these tables”
      ↩︎ Change tracking on source tables you do not own
      “SELECT on and MONITOR on DYNAMIC TABLES in the feature store schema.”
      ↩︎ Prediction
      “the source tables must have change tracking enabled, or the user must have OWNERSHIP of these tables to automatically enable change tracking”
      ↩︎ Checkpoint
    2. 2.
      “The owner of a model can grant access to any role as follows:”
      ↩︎ Producer and consumer roles on a Feature Store schema
      “Model objects have three privileges: OWNERSHIP, USAGE, and READ.”
      ↩︎ OWNERSHIP, USAGE and READ on registered models
      “Only one role can own the model, but you can grant that role to multiple users or to other roles.”
      ↩︎ OWNERSHIP, USAGE and READ on registered models
      “Note that the role that promotes models to production should have OWNERSHIP or READ privilege on the source model.”
      ↩︎ OWNERSHIP, USAGE and READ on registered models
      “Because machine learning models are first-class objects in Snowflake, you can use all standard Snowflake governance capabilities with them, including role-based access control”
      ↩︎ Key concept
      “Roles with only USAGE cannot access the model code, weights, or other artifacts.”
      ↩︎ Exam trap 2
    3. 3.
      “To create a compute pool in an account, the current role needs the CREATE COMPUTE POOL privilege on the account.”
      ↩︎ Producer and consumer roles on a Feature Store schema
    4. 4.
      “Alternatively, grant OWNERSHIP on the base table to the creating role, create the dynamic table (which auto-enables change tracking), and then transfer OWNERSHIP back.”
      ↩︎ Change tracking on source tables you do not own
      “Views that reference tables without change tracking also cause this error.”
      ↩︎ Change tracking on source tables you do not own
      “If another role owns the base tables, ask the owner to enable change tracking:”
      ↩︎ Exam trap 1
    5. 5.
      “Enables suspending or resuming a compute pool.”
      ↩︎ Privileges for ML compute pools
      “Enables viewing compute pool usage (number of services and jobs running), properties, and listing compute pools”
      ↩︎ Privileges for ML compute pools
    6. 6.
      “USAGE privilege on the compute pool to allow it to be used for ML workloads”
      ↩︎ Privileges for ML compute pools
      “CREATE SERVICE privilege on the schema to create and manage ML Jobs”
      ↩︎ Privileges for ML compute pools

    Continue to part 2 of 2

    Masking, row access and tag-based policies for ML data

    Spotted a mistake, or was something unclear? Tell us.