diff --git a/xxx-ConfluentCloudOnAzure/Coach/Lectures.pptx b/xxx-ConfluentCloudOnAzure/Coach/Lectures.pptx new file mode 100644 index 0000000000..e7303f385c Binary files /dev/null and b/xxx-ConfluentCloudOnAzure/Coach/Lectures.pptx differ diff --git a/xxx-ConfluentCloudOnAzure/Coach/README.md b/xxx-ConfluentCloudOnAzure/Coach/README.md new file mode 100644 index 0000000000..50dfbfa3e0 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/README.md @@ -0,0 +1,99 @@ +# What The Hack - ConfluentCloudOnAzure - Coach Guide + +## Introduction + +Welcome to the coach's guide for the ConfluentCloudOnAzure What The Hack. Here you will find links to specific guidance for coaches for each of the challenges. + +This hack includes an optional [lecture presentation](Lectures.pptx) that features short presentations to introduce key topics associated with each challenge. It is recommended that the host present each short presentation before attendees kick off that challenge. + +**NOTE:** If you are a Hackathon participant, this is the answer guide. Don't cheat yourself by looking at these during the hack! Go learn something. :) + +## Coach's Guides + +- Challenge 00: **[Prerequisites - Ready, Set, GO!](./Solution-00.md)** + - Prepare your workstation to work with Azure. +- Challenge 01: **[Title of Challenge](./Solution-01.md)** + - Description of challenge +- Challenge 02: **[Title of Challenge](./Solution-02.md)** + - Description of challenge +- Challenge 03: **[Title of Challenge](./Solution-03.md)** + - Description of challenge +- Challenge 04: **[Title of Challenge](./Solution-04.md)** + - Description of challenge +- Challenge 05: **[Title of Challenge](./Solution-05.md)** + - Description of challenge +- Challenge 06: **[Title of Challenge](./Solution-06.md)** + - Description of challenge +- Challenge 07: **[Title of Challenge](./Solution-07.md)** + - Description of challenge +- Challenge 08: **[Title of Challenge](./Solution-08.md)** + - Description of challenge +- Challenge 09: **[Title of Challenge](./Solution-09.md)** + - Description of challenge +- Challenge 10: **[Title of Challenge](./Solution-10.md)** + - Description of challenge +- Challenge 11: **[Title of Challenge](./Solution-11.md)** + - Description of challenge +- Challenge 12: **[Title of Challenge](./Solution-12.md)** + - Description of challenge +- Challenge 13: **[Title of Challenge](./Solution-13.md)** + - Description of challenge +- Challenge 14: **[Title of Challenge](./Solution-14.md)** + - Description of challenge +- Challenge 15: **[Title of Challenge](./Solution-15.md)** + - Description of challenge + +## Coach Prerequisites + +This hack has pre-reqs that a coach is responsible for understanding and/or setting up BEFORE hosting an event. Please review the [What The Hack Hosting Guide](https://aka.ms/wthhost) for information on how to host a hack event. + +The guide covers the common preparation steps a coach needs to do before any What The Hack event, including how to properly configure Microsoft Teams. + +### Student Resources + +Before the hack, it is the Coach's responsibility to download and package up the contents of the `/Student/Resources` folder of this hack into a "Resources.zip" file. The coach should then provide a copy of the Resources.zip file to all students at the start of the hack. + +Always refer students to the [What The Hack website](https://aka.ms/wth) for the student guide: [https://aka.ms/wth](https://aka.ms/wth) + +**NOTE:** Students should **not** be given a link to the What The Hack repo before or during a hack. The student guide does **NOT** have any links to the Coach's guide or the What The Hack repo on GitHub. + +### Additional Coach Prerequisites (Optional) + +_Please list any additional pre-event setup steps a coach would be required to set up such as, creating or hosting a shared dataset, or deploying a lab environment._ + +## Azure Requirements + +This hack requires students to have access to an Azure subscription where they can create and consume Azure resources. These Azure requirements should be shared with a stakeholder in the organization that will be providing the Azure subscription(s) that will be used by the students. + +_Please list Azure subscription requirements._ + +_For example:_ + +- Azure resources that will be consumed by a student implementing the hack's challenges +- Azure permissions required by a student to complete the hack's challenges. + +## Suggested Hack Agenda (Optional) + +_This section is optional. You may wish to provide an estimate of how long each challenge should take for an average squad of students to complete and/or a proposal of how many challenges a coach should structure each session for a multi-session hack event. For example:_ + +- Sample Day 1 + - Challenge 1 (1 hour) + - Challenge 2 (30 mins) + - Challenge 3 (2 hours) +- Sample Day 2 + - Challenge 4 (45 mins) + - Challenge 5 (1 hour) + - Challenge 6 (45 mins) + +## Repository Contents + +_The default files & folders are listed below. You may add to this if you want to specify what is in additional sub-folders you may add._ + +- `./Coach` + - Coach's Guide and related files +- `./Coach/Solutions` + - Solution files with completed example answers to a challenge +- `./Student` + - Student's Challenge Guide +- `./Student/Resources` + - Resource files, sample code, scripts, etc meant to be provided to students. (Must be packaged up by the coach and provided to students at start of event) diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-00.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-00.md new file mode 100644 index 0000000000..8ca1a44d71 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-00.md @@ -0,0 +1,20 @@ +# Challenge 00 - - Coach's Guide + +**[Home](./README.md)** - [Next Solution >](./Solution-01.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-01.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-01.md new file mode 100644 index 0000000000..01d1e30c27 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-01.md @@ -0,0 +1,20 @@ +# Challenge 01 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-00.md) - **[Home](./README.md)** - [Next Solution >](./Solution-02.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-02.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-02.md new file mode 100644 index 0000000000..1ef8ca5035 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-02.md @@ -0,0 +1,20 @@ +# Challenge 02 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-01.md) - **[Home](./README.md)** - [Next Solution >](./Solution-03.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-03.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-03.md new file mode 100644 index 0000000000..9591196509 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-03.md @@ -0,0 +1,20 @@ +# Challenge 03 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-02.md) - **[Home](./README.md)** - [Next Solution >](./Solution-04.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-04.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-04.md new file mode 100644 index 0000000000..90a770fdb3 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-04.md @@ -0,0 +1,20 @@ +# Challenge 04 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-03.md) - **[Home](./README.md)** - [Next Solution >](./Solution-05.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-05.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-05.md new file mode 100644 index 0000000000..811c053840 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-05.md @@ -0,0 +1,20 @@ +# Challenge 05 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-04.md) - **[Home](./README.md)** - [Next Solution >](./Solution-06.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-06.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-06.md new file mode 100644 index 0000000000..0100770cfa --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-06.md @@ -0,0 +1,20 @@ +# Challenge 06 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-05.md) - **[Home](./README.md)** - [Next Solution >](./Solution-07.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-07.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-07.md new file mode 100644 index 0000000000..d0dce03848 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-07.md @@ -0,0 +1,20 @@ +# Challenge 07 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-06.md) - **[Home](./README.md)** - [Next Solution >](./Solution-08.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-08.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-08.md new file mode 100644 index 0000000000..dd606228fe --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-08.md @@ -0,0 +1,20 @@ +# Challenge 08 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-07.md) - **[Home](./README.md)** - [Next Solution >](./Solution-09.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-09.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-09.md new file mode 100644 index 0000000000..fb3e4977be --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-09.md @@ -0,0 +1,20 @@ +# Challenge 09 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-08.md) - **[Home](./README.md)** - [Next Solution >](./Solution-10.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-10.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-10.md new file mode 100644 index 0000000000..333d00f4e5 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-10.md @@ -0,0 +1,20 @@ +# Challenge 10 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-09.md) - **[Home](./README.md)** - [Next Solution >](./Solution-11.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-11.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-11.md new file mode 100644 index 0000000000..bfe08eb196 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-11.md @@ -0,0 +1,20 @@ +# Challenge 11 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-10.md) - **[Home](./README.md)** - [Next Solution >](./Solution-12.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-12.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-12.md new file mode 100644 index 0000000000..1298296f72 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-12.md @@ -0,0 +1,20 @@ +# Challenge 12 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-11.md) - **[Home](./README.md)** - [Next Solution >](./Solution-13.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-13.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-13.md new file mode 100644 index 0000000000..b2cd42e5c4 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-13.md @@ -0,0 +1,20 @@ +# Challenge 13 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-12.md) - **[Home](./README.md)** - [Next Solution >](./Solution-14.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-14.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-14.md new file mode 100644 index 0000000000..392d0d9f58 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-14.md @@ -0,0 +1,20 @@ +# Challenge 14 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-13.md) - **[Home](./README.md)** - [Next Solution >](./Solution-15.md) + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solution-15.md b/xxx-ConfluentCloudOnAzure/Coach/Solution-15.md new file mode 100644 index 0000000000..2630ab3d7e --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Coach/Solution-15.md @@ -0,0 +1,20 @@ +# Challenge 15 - <Title of Challenge> - Coach's Guide + +[< Previous Solution](./Solution-14.md) - **[Home](./README.md)** + +## Notes & Guidance + +This is the only section you need to include. + +Use general non-bulleted text for the beginning of a solution area for this challenge + +- Then move into bullets + - And sub-bullets and even + - sub-sub-bullets + +Break things apart with more than one bullet list + +- Like this +- One +- Right +- Here diff --git a/xxx-ConfluentCloudOnAzure/Coach/Solutions/.gitkeep b/xxx-ConfluentCloudOnAzure/Coach/Solutions/.gitkeep new file mode 100644 index 0000000000..e69de29bb2 diff --git a/xxx-ConfluentCloudOnAzure/README.md b/xxx-ConfluentCloudOnAzure/README.md new file mode 100644 index 0000000000..4fd7131475 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/README.md @@ -0,0 +1,48 @@ +# What The Hack - Confluent Cloud Integration with Microsoft Azure + +## Introduction + +This introductory hackathon will provide participants with hands-on experience on how to integrate the Confluent Cloud offering with Microsoft Azure platform services. + +## Learning Objectives + +The objective of the hackathon is to demonstrate different strategies for integrating Confluent Cloud on Azure with Azure Platform products across various scenarios. + +## Exit Competencies +Upon completion, the participants should be able to: +- Master basic concepts involved with event stream processing with Confluent Cloud leveraging the Apache Kafka Ecosystem components such as Producers, Consumers, Kafka Connect, Kafka Streams, KSQL and Schema Registry. +- Understand the different source and sink connectors available for integration on Microsoft Azure. +- Provision and configure Confluent Cloud and the various ecosystem components. +- Secure access to Confluent Cloud Resources. +- Integrate Azure Private Virtual Networks with Confluent Cloud +- Perform capacity planning and quota enforcement for Confluent Cloud resources. +- Manage availability, business continuity and disaster recovery. + +## Challenges + +These are the 5 challenges for the Hack. +- Challenge 00: **[ Prerequisites, Sizing & Capacity Planning](Student/Challenge-00.md)** + - Prepare your workstation to work with Azure. Deploy the Confluent & Azure resources needed for starting the Hack. +- Challenge 01: **[Data Definition and Core Concepts for Storage](Student/Challenge-01.md)** + - DDL: Design, configure and create Kafka topics and Schema Registry instance for the Kafka events/messages. +- Challenge 02: **[Data Manipulation Reading and Writing Data Directly with Topics](Student/Challenge-02.md)** + - DML: Write data from Kafka producers and read data with Kafka consumers. Enrich and display events coming back from Kafka topics. +- Challenge 03: **[Kafka Connect Ecosystem and Architecture](Student/Challenge-03.md)** + - The glue: leverage the Kafka Connect ecosystem to bring data into Kafka topics from different data stores and write events out to different data stores using Kafka Connect. +- Challenge 04: **[Bringing it All Together, Processing Streams in Realtime with KSQLDB](Student/Challenge-04.md)** + - Real-time JOINS: Leverage Kafka Streams and KSQLDB to bring together multiple streams of events, facts and dimensions to enrich, filter, process and generate new events from existing streams. +- Challenge 05: **[Realtime Visualization of Streams](Student/Challenge-05.md)** + - A picture is worth 1024 words. Generate cool visualizations that captures the state of the streams in realtime. + +## Prerequisites + +- Access to an Azure subscription with Owner access + - If you don’t have one, Sign Up for Azure [HERE](https://azure.microsoft.com/en-us/free/) + - Familiarity with [Azure Cloud Shell](https://learn.microsoft.com/en-us/azure/cloud-shell/overview#multiple-access-points) +- Access to [Confluent Cloud on Azure](https://learn.microsoft.com/en-us/azure/partner-solutions/apache-kafka-confluent-cloud/overview), an Azure Native ISV Services +- An IDE: [Visual Studio Code](https://code.visualstudio.com/), [WebStorm](https://www.jetbrains.com/webstorm/download/), [PyCharm](https://www.jetbrains.com/pycharm/download/) or [IntelliJ](https://www.jetbrains.com/idea/download/) + +## Contributors + +- [Israel Ekpo](https://github.com/izzymsft) +- [Jacob Bogie](https://github.com/JakeBogie) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-00.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-00.md new file mode 100644 index 0000000000..246284752c --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-00.md @@ -0,0 +1,75 @@ +# Challenge 00 - Prerequisites, Sizing & Capacity Planning + +**[Home](../README.md)** - [Next Challenge >](./Challenge-01.md) + +## Introduction + +Thank you for participating in the Confluent on Azure What The Hack. Before you can hack, you will need to set up some prerequisites. + +## Common Prerequisites + +We have compiled a list of common tools and software that will come in handy to complete most What The Hack Azure-based hacks! + +You might not need all of them for the hack you are participating in. However, if you work with Azure on a regular basis, these are all things you should consider having in your toolbox. + +- [Azure Subscription](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-subscription) +- [Azure Portal](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-portal) +- [Azure CLI](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-cli) +- [Note for Windows Users](../../000-HowToHack/WTH-Common-Prerequisites.md#note-for-windows-users) +- [Azure PowerShell CmdLets](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-powershell-cmdlets) +- [Azure Cloud Shell](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-cloud-shell) +- [Visual Studio Code](../../000-HowToHack/WTH-Common-Prerequisites.md#visual-studio-code) +- [VS Code plugin for ARM Templates](../../000-HowToHack/WTH-Common-Prerequisites.md#visual-studio-code-plugins-for-arm-templates) +- [Azure Storage Explorer](../../000-HowToHack/WTH-Common-Prerequisites.md#azure-storage-explorer) + +## Background Story +Contoso Retail is an online grocery platform that sells food that can be shipped to customers. Clients of Contoso Retail should be able to purchase the grocery items and also return items for any reason. Contoso Retail also works with suppliers that bring inventory daily for replenishment to the warehouse where customer orders are shipped from. The inventory is constantly been incremented or decremented from activities such as customer purchases, supplier replenishments and customer returns (if the item is still in good condition and can be resold). + +One average, there are approximately 35,000 transactions every hour that gets generated across multiple orders. Each transaction generates about 500kB of data going into the Kafka cluster and these events have to be retained for at least 90 days as per department of commerce regulations. + +The suppliers send notifications for inventory replenishments in various data formats including but not limited to CSV, JSON, Protobuf and Avro formats. The order database is a MySQL database that keeps track of all purchases and the returns databases is a Cosmos DB collection that tracks all the items returned. + +## Description + +Based on the background story, determine the appropriate Confluent Cloud cluster and SKU as well as the necessary Kafka components as well as the Azure resources that is necessary to support the workload necessary for the solution that Contoso Retail needs. + +Deploy the ARM template for the Cosmos DB database, Data Generators and Azure functions and set up the initial Confluent Cloud Cluster. The Cosmos DB database contains collections for Users and Products + +For this hack, we will need to deploy a Confluent Cloud on Azure instance as well as other Azure data stores and compute resources needed for the hack. + +Now that you have the common pre-requisites installed on your workstation, there are prerequisites specific to this hack. + +Your coach will provide you with a Resources.zip file that contains resources you will need to complete the hack. If you plan to work locally, you should unpack it on your workstation. If you plan to use the Azure Cloud Shell, you should upload it to the Cloud Shell and unpack it there. + +Please install these additional tools: + +- [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) extension for Visual Studio Code +- .NET SDK 6.0 or later installed on your development machine. This can be downloaded from [here](https://www.microsoft.com/net/download/all) for multiple platforms. + +In the `/Challenge00/` folder of the Resources.zip file, you will find an ARM template, `setupIoTEnvironment.json` that sets up the initial hack environment in Azure you will work with in subsequent challenges. + +Please deploy the template by running the following Azure CLI commands from the location of the template file: +``` +az group create --name myIoT-rg --location eastus +az group deployment create -g myIoT-rg --name HackEnvironment -f setupIoTEnvironment.json +``` + +## Success Criteria + +To complete this challenge successfully, you should be able to: + +- Verify that you have a bash shell with the Azure CLI available. +- Verify that the ARM template has deployed the following resources in Azure: + - Azure Function App + - Virtual Network + - Azure Cosmos DB Instance +- Verify that the Confluent Cloud on Azure instance has been deployed successfully + +## Learning Resources + +_Confluent and Azure resource links:_ + +- [Apache Kafka for Confluent Cloud on Azure](https://learn.microsoft.com/en-us/azure/partner-solutions/apache-kafka-confluent-cloud/overview) +- [Azure Cosmos DB](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction) +- [Azure Function Premium Plan](https://learn.microsoft.com/en-us/azure/azure-functions/create-premium-plan-function-app-portal) +- [Confluent Developer Courses](https://developer.confluent.io/learn-kafka/) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-01.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-01.md new file mode 100644 index 0000000000..a472f905d7 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-01.md @@ -0,0 +1,42 @@ +# Challenge 01 - Data Definition and Core Concepts for Storage + +[< Previous Challenge](./Challenge-00.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-02.md) + +## Introduction + +Just like SQL tables, Apache Kafka has topics that serves to hold the events that are sent to be stored/buffered on the Kafka cluster. +The Confluent Schema Registry is a resources that helps to keep track of the different versions of messages/events that are stored in these topics. + +## Description + +There are some Azure functions that have been deployed to push retail activity data into the cluster. + +These functions are currently disabled. These functions will be generating activities and events in the following categories, so we need to set up topics to store the events: +- Purchases +- Returns +- Inventory Replenishment +- Users +- Product Ratings +- Products +- Inventory on Hand + +Each topic should have 4 partitions. + +You will need to create topics and set up a schema registry instance and create topics for these event/message types on the cluster that will hold these event streams from the data generators (Azure Functions). + +Enable the functions and restart the function app with the correct configurations after your schema registry instance and Kafka topics have been created. + +## Success Criteria + +To complete this challenge successfully, you should be able to: +- Verify each of the topics listed are created using valid topic names. +- Verify that you can write events and read events from each topic using the CLI tools. +- Verify that the Schema Registry is aware of the data structure in each Kafka topic. + +## Learning Resources + +*Sample IoT resource links:* + +- [Confluent Schema Registry](https://docs.confluent.io/platform/current/schema-registry/index.html) +- [Kafka CLI Tools](https://docs.confluent.io/kafka/operations-tools/kafka-tools.html) +- [Confluent Developer Courses](https://developer.confluent.io/learn-kafka/) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-02.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-02.md new file mode 100644 index 0000000000..22b0b88c0f --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-02.md @@ -0,0 +1,44 @@ +# Challenge 02 - Data Manipulation Reading and Writing Data Directly with Topics + +[< Previous Challenge](./Challenge-01.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-03.md) + +## Introduction + +When interacting with Kafka topics, clients generally fall into two categories: +- Producers +- Consumers + +An Apache Kafka® Producer is a client application that publishes (writes) events to a Kafka cluster. + +The producer is thread safe and sharing a single producer instance across threads will generally be faster than having multiple instances. + +It typically publishes messages to topics as key-value pairs. The keys are used to route the events to different partitions of that topic. + +A Kafka Consumer is a client that consumes or reads records from a Kafka cluster. This client transparently handles the failure of Kafka brokers, and transparently adapts as topic partitions it fetches migrate within the cluster. This client also interacts with the broker to allow groups of consumers to load balance consumption using consumer groups. The consumer maintains TCP connections to the necessary brokers to fetch data. Failure to close the consumer after use will leak these connections. The consumer is not thread-safe. See Multi-threaded Processing for more details. + +## Description + +Contoso Retail needs to create two Kafka clients that can perform the tasks of continually writing a review by sending in a rating between 1 to 5 stars every 15 seconds for a random product (1 out of 10 products in the database). This app will pick a random user out of the Cosmos DB database to write the review (rating) each time. + +The first Kafka client will do the following: +- Create a product rating entry containing the product id, user id, rating and current date. +- Rating score should be between 1 and 5 inclusive +- Sent to the Product Ratings topic + +The second Kafka client should do the following, combining data from the Cosmos DB collections: +- Retrieve the product rating from the topic as soon as it is written +- Display the full name, email address and country of the user as well as the full price, product name and rating of the product. +- Also display the offset, the key, partition id where the rating event was stored +- Start with one consumer, then 2 consumers and then increase to 7 consumers. Make a note of what you observe when the number of consumers exceed the number of partitions in the topic. + +## Success Criteria + +To complete this challenge successfully, you should be able to: +- Verify that the clients are able to write successfully to the topics +- Verify that the clients are able to read successfully from the topics +- + +## Learning Resources +- [Kafka Consumer](https://docs.confluent.io/platform/current/clients/consumer.html) +- [Kafka Producer](https://docs.confluent.io/platform/current/clients/producer.html) +- [Schemas and Serializers](https://docs.confluent.io/platform/current/clients/app-development.html) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-03.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-03.md new file mode 100644 index 0000000000..c1c9b2b7a1 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-03.md @@ -0,0 +1,47 @@ +# Challenge 03 - Kafka Connect Ecosystem and Architecture + +[< Previous Challenge](./Challenge-02.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-04.md) + +## Introduction + +Kafka Connect is a tool for scalably and reliably streaming data between Apache Kafka® and other data systems. + +It makes it simple to quickly define connectors that move large data sets in and out of Kafka. + +Kafka Connect can ingest entire databases or collect metrics from all your application servers into Kafka topics, making the data available for stream processing with low latency. + +An export connector can deliver data from Kafka topics into secondary storage outside Kafka like Azure Cognitive Search, Cosmos DB and Blob Store + + +## Description + +In this challenge we are going to bring in the Kafka Connect ecosystem and leverage it to stream changes from CosmosDB into Kafka as well as stream new events from the Apache Kafka topics into CosmosDB. In this challenge, create a Kafka Connect Sink and Source for the Cosmos DB resource you have deployed. + +For the Cosmos DB Source Connector, configure it to stream changes from the following collections into their equivalent Kafka cluster topics +- Users +- Products + +For the Cosmos DB Sink Connector, configure it to stream changes from the following topics into their equivalent Cosmos DB collections: +- Purchases +- Returns +- Inventory Replenishment +- Users +- Product Ratings +- Products +- Product Inventory Capacity (contains the expected number of inventory, the maximum and minimum) +- Inventory on Hand +- Top 5 Products + + +To complete this challenge successfully, you should be able to: +- Verify that all the users and products from the Cosmos DB database have been loaded into the Kafka topics. +- Verify that all the generated events have been successfully stored in the Cosmos DB collections. +- Verify that all the records from the users and products collections in Cosmos DB are accounted for in the Azure Cognitive Search instance + +## Learning Resources + +- [Kafka Connect 101 Course](https://developer.confluent.io/learn-kafka/kafka-connect/intro/) +- [Kafka Connect Overview](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/kafka-connector) +- [Azure Cognitive Search Sink Connector](https://docs.confluent.io/kafka-connectors/azure-search/current/overview.html) +- [Cosmos DB Source Connector](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/kafka-connector-source) +- [Cosmos DB Sink Connector](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/kafka-connector-sink) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-04.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-04.md new file mode 100644 index 0000000000..e5bcf01897 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-04.md @@ -0,0 +1,39 @@ +# Challenge 04 - Bringing it All Together, Processing Streams in Realtime with KSQLDB + +[< Previous Challenge](./Challenge-03.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-05.md) + +## Introduction +Kafka Streams is a client library for processing and analyzing data stored in Kafka. It builds upon important stream processing concepts such as properly distinguishing between event time and processing time, windowing support, and simple yet efficient management and real-time querying of application state + +ksqlDB is a database that's purpose-built for stream processing applications. It is built on top of Kafka Streams and provides a SQL interface for defining and processing streams from Kafka topics and writing them back to destination topics. + +## Description + +In this challenge, our goal is to figure out in near-real-time how much inventory we have on-hand based on the activities from the following event streams: +- Inventory Replenishment +- Order Returns/Refunds +- Product Purchases from new orders + +We will use events from 3 topics to compute in real time the amount of inventory at hand based on purchases, returns and replenishment events and store this data in a new topic called Inventory on Hand. This will have the name of the product, the product identifier and how much inventory we have on hand (an integer) + +We will also create a new topic that stores the current top 5 products based on ratings at any given time. This topic will contain the following pieces of data +- Product name +- Unit Price +- Total Ratings: how many customers rated the product +- Highest Rating +- Lowest Rating +- Most Recent Rating +- Rating Score (average of all ratings so far) + + +## Success Criteria + +To complete this challenge successfully, you should be able to: +- Verify that the inventory counts are accurate based on retail purchases, returns and inventory replenishment. +- Verify that the ratings displayed are accurate. + +## Learning Resources + +- [Kafka Streams](https://kafka.apache.org/34/documentation/streams/core-concepts) +- [KSQLDB Overview](https://ksqldb.io/overview.html) +- [kSQLDB Documentation](https://docs.ksqldb.io/en/latest/) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-05.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-05.md new file mode 100644 index 0000000000..1792f6c98c --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-05.md @@ -0,0 +1,39 @@ +# Challenge 05 - Realtime Visualization of Streams + +[< Previous Challenge](./Challenge-04.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-06.md) + +## Introduction + +Power BI with real-time streaming helps you stream data and update dashboards in real time. + +Any visual or dashboard created in Power BI can display and update real-time data and visuals. + +The devices and sources of streaming data can be factory sensors, Azure data stores, social media sources, service usage metrics, or many other time-sensitive data collectors or transmitters. + +With Azure services and Power BI, you can turn your data processing efforts into analytics and reports that provide real-time insights into your business. Whether your data processing is cloud-based or on-premises, straightforward, or complex, single-sourced or massively scaled, warehoused, or real-time, Azure and Power BI have the built-in connectivity and integration to bring your business intelligence efforts to life. + +Power BI has a multitude of Azure connections available, and the business intelligence solutions you can create with those services are as unique as your business. You can connect as few as one Azure data source, or a handful, then shape and refine your data to build customized reports. + +## Description + +Now that we have all these streams, we need to visualize the streams. + +- Create a PowerBI dashboard that displays the top 5 products as well as the inventory on hand for all 10 products at any given time. +- Create a PowerBI dashboard that displays the top 3 products returned in the last 5 minutes. +- Create a PowerBI dashboard that displays the top 3 products purchased in the last 15 minutes. +- Create a PowerBI dashboard that displays the top 3 products supplied via inventory replenishment in the last 10 minutes. +- Create a PowerBI dashboard for all out of stock products. +- Create a PowerBI dashboard for all products whose inventory counts are critical (below minimum count but above zero) + +## Success Criteria + +To complete this challenge successfully, you should be able to: +- Verify that the events from the topics are visible within 3 seconds of landing in Cosmos DB and Cognitive Search +- Verify that there is no decline in performance after a certain amount of time. + +## Learning Resources +- [Power BI Desktop](https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-getting-started) +- [Visualize Cosmos DB Data with PowerBI](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/powerbi-visualize) +- [Using Cognitive Search in Power BI](https://learn.microsoft.com/en-us/power-bi/connect-data/service-tutorial-use-cognitive-services) +- [PowerBI and Knowledge Stores](https://learn.microsoft.com/en-us/azure/search/knowledge-store-connect-power-bi) +- [Streaming Dataasets in PowerBi](https://learn.microsoft.com/en-us/power-bi/connect-data/service-real-time-streaming) diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-06.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-06.md new file mode 100644 index 0000000000..59e43d9bae --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-06.md @@ -0,0 +1,99 @@ +# Challenge 06 - <Title of Challenge> + +[< Previous Challenge](./Challenge-05.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-07.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-07.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-07.md new file mode 100644 index 0000000000..82cb7e727e --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-07.md @@ -0,0 +1,99 @@ +# Challenge 07 - <Title of Challenge> + +[< Previous Challenge](./Challenge-06.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-08.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-08.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-08.md new file mode 100644 index 0000000000..4fffe19429 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-08.md @@ -0,0 +1,99 @@ +# Challenge 08 - <Title of Challenge> + +[< Previous Challenge](./Challenge-07.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-09.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-09.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-09.md new file mode 100644 index 0000000000..0c74d60da8 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-09.md @@ -0,0 +1,99 @@ +# Challenge 09 - <Title of Challenge> + +[< Previous Challenge](./Challenge-08.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-10.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-10.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-10.md new file mode 100644 index 0000000000..9c3983adf6 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-10.md @@ -0,0 +1,99 @@ +# Challenge 10 - <Title of Challenge> + +[< Previous Challenge](./Challenge-09.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-11.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-11.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-11.md new file mode 100644 index 0000000000..2275ef98be --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-11.md @@ -0,0 +1,99 @@ +# Challenge 11 - <Title of Challenge> + +[< Previous Challenge](./Challenge-10.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-12.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-12.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-12.md new file mode 100644 index 0000000000..629ff23c7f --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-12.md @@ -0,0 +1,99 @@ +# Challenge 12 - <Title of Challenge> + +[< Previous Challenge](./Challenge-11.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-13.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-13.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-13.md new file mode 100644 index 0000000000..e4f6cbbaef --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-13.md @@ -0,0 +1,99 @@ +# Challenge 13 - <Title of Challenge> + +[< Previous Challenge](./Challenge-12.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-14.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-14.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-14.md new file mode 100644 index 0000000000..0ac99972f1 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-14.md @@ -0,0 +1,99 @@ +# Challenge 14 - <Title of Challenge> + +[< Previous Challenge](./Challenge-13.md) - **[Home](../README.md)** - [Next Challenge >](./Challenge-15.md) + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Challenge-15.md b/xxx-ConfluentCloudOnAzure/Student/Challenge-15.md new file mode 100644 index 0000000000..364e5ea492 --- /dev/null +++ b/xxx-ConfluentCloudOnAzure/Student/Challenge-15.md @@ -0,0 +1,99 @@ +# Challenge 15 - <Title of Challenge> + +[< Previous Challenge](./Challenge-14.md) - **[Home](../README.md)** + +***This is a template for a single challenge. The italicized text provides hints & examples of what should or should NOT go in each section. You should remove all italicized & sample text and replace with your content.*** + +## Pre-requisites (Optional) + +*Your hack's "Challenge 0" should cover pre-requisites for the entire hack, and thus this section is optional and may be omitted. If you wish to spell out specific previous challenges that must be completed before starting this challenge, you may do so here.* + +## Introduction + +*This section should provide an overview of the technologies or tasks that will be needed to complete the this challenge. This includes the technical context for the challenge, as well as any new "lessons" the attendees should learn before completing the challenge.* + +*Optionally, the coach or event host is encouraged to present a mini-lesson (with a PPT or video) to set up the context & introduction to each challenge. A summary of the content of that mini-lesson is a good candidate for this Introduction section* + +*For example:* + +When setting up an IoT device, it is important to understand how 'thingamajigs' work. Thingamajigs are a key part of every IoT device and ensure they are able to communicate properly with edge servers. Thingamajigs require IP addresses to be assigned to them by a server and thus must have unique MAC addresses. In this challenge, you will get hands on with a thingamajig and learn how one is configured. + +## Description + +*This section should clearly state the goals of the challenge and any high-level instructions you want the students to follow. You may provide a list of specifications required to meet the goals. If this is more than 2-3 paragraphs, it is likely you are not doing it right.* + +***NOTE:** Do NOT use ordered lists as that is an indicator of 'step-by-step' instructions. Instead, use bullet lists to list out goals and/or specifications.* + +***NOTE:** You may use Markdown sub-headers to organize key sections of your challenge description.* + +*Optionally, you may provide resource files such as a sample application, code snippets, or templates as learning aids for the students. These files are stored in the hack's `Student/Resources` folder. It is the coach's responsibility to package these resources into a Resources.zip file and provide it to the students at the start of the hack.* + +***NOTE:** Do NOT provide direct links to files or folders in the What The Hack repository from the student guide. Instead, you should refer to the Resource.zip file provided by the coach.* + +***NOTE:** As an exception, you may provide a GitHub 'raw' link to an individual file such as a PDF or Office document, so long as it does not open the contents of the file in the What The Hack repo on the GitHub website.* + +***NOTE:** Any direct links to the What The Hack repo will be flagged for review during the review process by the WTH V-Team, including exception cases.* + +*Sample challenge text for the IoT Hack Of The Century:* + +In this challenge, you will properly configure the thingamajig for your IoT device so that it can communicate with the mother ship. + +You can find a sample `thingamajig.config` file in the `/ChallengeXX` folder of the Resources.zip file provided by your coach. This is a good starting reference, but you will need to discover how to set exact settings. + +Please configure the thingamajig with the following specifications: +- Use dynamic IP addresses +- Only trust the following whitelisted servers: "mothership", "IoTQueenBee" +- Deny access to "IoTProxyShip" + +You can view an architectural diagram of an IoT thingamajig here: [Thingamajig.PDF](/Student/Resources/Architecture.PDF?raw=true). + +## Success Criteria + +*Success criteria goes here. The success criteria should be a list of checks so a student knows they have completed the challenge successfully. These should be things that can be demonstrated to a coach.* + +*The success criteria should not be a list of instructions.* + +*Success criteria should always start with language like: "Validate XXX..." or "Verify YYY..." or "Show ZZZ..." or "Demonstrate you understand VVV..."* + +*Sample success criteria for the IoT sample challenge:* + +To complete this challenge successfully, you should be able to: +- Verify that the IoT device boots properly after its thingamajig is configured. +- Verify that the thingamajig can connect to the mothership. +- Demonstrate that the thingamajic will not connect to the IoTProxyShip + +## Learning Resources + +_List of relevant links and online articles that should give the attendees the knowledge needed to complete the challenge._ + +*Think of this list as giving the students a head start on some easy Internet searches. However, try not to include documentation links that are the literal step-by-step answer of the challenge's scenario.* + +***Note:** Use descriptive text for each link instead of just URLs.* + +*Sample IoT resource links:* + +- [What is a Thingamajig?](https://www.bing.com/search?q=what+is+a+thingamajig) +- [10 Tips for Never Forgetting Your Thingamajic](https://www.youtube.com/watch?v=dQw4w9WgXcQ) +- [IoT & Thingamajigs: Together Forever](https://www.youtube.com/watch?v=yPYZpwSpKmA) + +## Tips + +*This section is optional and may be omitted.* + +*Add tips and hints here to give students food for thought. Sample IoT tips:* + +- IoTDevices can fail from a broken heart if they are not together with their thingamajig. Your device will display a broken heart emoji on its screen if this happens. +- An IoTDevice can have one or more thingamajigs attached which allow them to connect to multiple networks. + +## Advanced Challenges (Optional) + +*If you want, you may provide additional goals to this challenge for folks who are eager.* + +*This section is optional and may be omitted.* + +*Sample IoT advanced challenges:* + +Too comfortable? Eager to do more? Try these additional challenges! + +- Observe what happens if your IoTDevice is separated from its thingamajig. +- Configure your IoTDevice to connect to BOTH the mothership and IoTQueenBee at the same time. diff --git a/xxx-ConfluentCloudOnAzure/Student/Resources/.gitkeep b/xxx-ConfluentCloudOnAzure/Student/Resources/.gitkeep new file mode 100644 index 0000000000..e69de29bb2