Ignore pattern for Udemy course broken link.

.linkcheck.json

@@ -15,6 +15,7 @@
         { "pattern": "^https://github.com" },
         { "pattern": "^https://help.looker.com"},
         { "pattern": "^https://mozilla-hub.atlassian.net" },
-        { "pattern": "^https:///mozilla.slack.com" }
+        { "pattern": "^https:///mozilla.slack.com" },
+        { "pattern": "^https://mozilla.udemy.com"},
     ]
 }

src/cookbooks/data_modeling/using_aggregates.md

@@ -63,7 +63,7 @@ This doc is about when to use different options to aggregate data, their limitat
   - BigQuery aggregate tables are backfilled using the managed-backfill process.
   - Materialized views cannot be backfilled, instead a materialized view needs to be re-created. Schema changes in base tables invalidate the view and requires it to be re-created. Materialized views scan all historical data of their referenced base tables by default, so **ensure to set a date filter to reduce the amount of data to be scanned**.
     - Add a date filter to materialized views to limit the amount of data to be scanned when these views get deployed initially. Otherwise, they will scan the entire data in referenced base tables.
-  - Looker PDTs require following a [protocol to backfill documented in Section 5 - Chapter 17 of the [Mozilla Looker Developers](https://mozilla.udemy.com/course/looker-training-for-developers/) course.
+  - Looker PDTs require following the [protocol to backfill described in the [Mozilla Looker Developers course](https://mozilla.udemy.com/course/looker-training-for-developers/learn/lecture/35440216#overview).
 - Using indices, partition and clustering is allowed for all cases. Looker requires that they are defined in the base table.
 - There is a limit of 20 materialized views per table.
 - When considering materialized views, a common practice is to use a combination of an aggregate table to store historical data (e.g. older than 2 days) and use a materialized view to track data in real-time (e.g. aggregate data that is just coming in). This allows to run backfills on the aggregate table.