Merge pull request #50347 from wwlpublish/180aadf6cd93acd32032912736311d367415abf9fc8b40e7e22e69b70ea6383e-live

JamesJBarnett · web-flow · commit 99dd201db1f7 · 2025-05-08T13:27:23.000-07:00
Modules/M02-design-application-architecture
diff --git a/learn-pr/wwl-azure/design-application-architecture/1-introduction.yml b/learn-pr/wwl-azure/design-application-architecture/1-introduction.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.introduction
 title: Introduction
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/10-knowledge-check.yml b/learn-pr/wwl-azure/design-application-architecture/10-knowledge-check.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.knowledge-check
 title: Module assessment
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Module assessment
   description: "Knowledge check"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/11-summary-resources.yml b/learn-pr/wwl-azure/design-application-architecture/11-summary-resources.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.summary-resources
 title: Summary and resources
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Summary and resources
   description: "Summary and resources"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/2-describe-message-event-scenarios.yml b/learn-pr/wwl-azure/design-application-architecture/2-describe-message-event-scenarios.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.describe-message-event-scenarios
 title: Describe message and event scenarios
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Describe message and event scenarios
   description: "Describe message and event scenarios"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/3-design-messaging-solution.yml b/learn-pr/wwl-azure/design-application-architecture/3-design-messaging-solution.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.design-application-architecture.design-messaging-solution
 title: Design a messaging solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design a messaging solution
   description: "Design a messaging solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 6
+durationInMinutes: 8
 content: |
   [!include[](includes/3-design-messaging-solution.md)]
diff --git a/learn-pr/wwl-azure/design-application-architecture/4-design-event-hub-messaging-solution.yml b/learn-pr/wwl-azure/design-application-architecture/4-design-event-hub-messaging-solution.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.design-application-architecture.design-event-hub-messaging-solution
 title: Design an Azure Event Hubs messaging solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design an Azure Event Hubs messaging solution
   description: "Design an Azure Event Hubs messaging solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 6
+durationInMinutes: 8
 content: |
   [!include[](includes/4-design-event-hub-messaging-solution.md)]
diff --git a/learn-pr/wwl-azure/design-application-architecture/5-design-event-driven-solution.yml b/learn-pr/wwl-azure/design-application-architecture/5-design-event-driven-solution.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.design-application-architecture.design-event-driven-solution
 title: Design an event-driven solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design an event-driven solution
   description: "Design an event-driven solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 5
+durationInMinutes: 7
 content: |
   [!include[](includes/5-design-event-driven-solution.md)]
diff --git a/learn-pr/wwl-azure/design-application-architecture/6-design-caching-solution.yml b/learn-pr/wwl-azure/design-application-architecture/6-design-caching-solution.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.design-caching-solution
 title: Design a caching solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design a caching solution
   description: "Design a caching solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/7-design-api-integration.yml b/learn-pr/wwl-azure/design-application-architecture/7-design-api-integration.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.design-api-integration
 title: Design API integration
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design API integration
   description: "Design API integration"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/8-design-automated-app-deployment-solution.yml b/learn-pr/wwl-azure/design-application-architecture/8-design-automated-app-deployment-solution.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.design-automated-app-deployment-solution
 title: Design an automated app deployment solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design an automated app deployment solution
   description: "Design an automated app deployment solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/9-configuration-management-solution.yml b/learn-pr/wwl-azure/design-application-architecture/9-configuration-management-solution.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-application-architecture.configuration-management-solution
 title: Design an app configuration management solution
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design an app configuration management solution
   description: "Design an app configuration management solution"
-  ms.date: 02/03/2025
+  ms.date: 05/08/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/1-introduction.md b/learn-pr/wwl-azure/design-application-architecture/includes/1-introduction.md
@@ -6,7 +6,7 @@ These design changes bring new challenges. Application states are distributed, a
 - Be resilient when failures occur.
 - Be able to integrate with other systems seamlessly.
 
-In this module, we explore how Azure lets you create applications composed of various components, including website front ends, back-end services, and triggered functions. We investigate how Azure includes various communication strategies to enable the components to pass data to each other.
+In this module, we explore how Azure lets you create AI-ready applications composed of various components, including website front ends, back-end services, and triggered functions. We investigate how Azure includes various communication strategies to enable the components to pass data to each other.
 
 ## Meet Tailwind Traders
 
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/10-knowledge-check.md b/learn-pr/wwl-azure/design-application-architecture/includes/10-knowledge-check.md
@@ -1,6 +1,7 @@
 
 
 
+
 Tailwind Traders is advancing work on its customer rewards game. With each purchase, customers are offered a chance to win cash or prizes. You're asked to provide input on engineering requirements to enable the game features. 
 
 - **Transaction processing**. When a customer makes a purchase, the order details should be grouped into a single transaction in the game.  
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/11-summary-resources.md b/learn-pr/wwl-azure/design-application-architecture/includes/11-summary-resources.md
@@ -1,4 +1,4 @@
-In this module, you learned how to evaluate and design an effective application architecture. You explored Azure solutions for exchanging messages, automating application deployment, and managing application configuration. You reviewed how to integrate Azure services with your applications by using APIs, and how to provide appropriate caching. You discovered how to use Azure services to create a scalable, efficient, event-driven solution.
+In this module, you learned how to evaluate and design an effective AI-ready application architecture. You explored Azure solutions for exchanging messages, automating application deployment, and managing application configuration. You reviewed how to integrate Azure services with your applications by using APIs, and how to provide appropriate caching. You discovered how to use Azure services to create a scalable, efficient, event-driven solution.
 
 ## Learn more with Copilot
 
@@ -12,7 +12,6 @@ Copilot can assist you in designing Azure infrastructure solutions. Copilot can
 
 - Compare and contrast the pros and cons of Azure Event Hubs and Azure Event Grid. Provide some examples. 
 
-- What is IoT? What Azure products are available? Describe and compare the different product options with usage cases.
 
 ## Learn more with Azure documentation
 
@@ -46,8 +45,6 @@ Copilot can assist you in designing Azure infrastructure solutions. Copilot can
 
 ## Learn more with optional hands-on exercises
 
-- Implement [message-based communication workflows with Azure Service Bus (sandbox)](/training/modules/implement-message-workflows-with-service-bus/).
-
 - Practice [creating an Azure Service Bus queue and topic (sandbox)](/training/modules/implement-message-workflows-with-service-bus/3-exercise-implement-a-service-bus-topic-and-queue).
 
 - Deploy [Azure infrastructure by using JSON ARM templates (sandbox)](/training/modules/create-azure-resource-manager-template-vs-code/).
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/2-describe-message-event-scenarios.md b/learn-pr/wwl-azure/design-application-architecture/includes/2-describe-message-event-scenarios.md
@@ -1,4 +1,4 @@
-Your first decision in your application architecture design is to plan how the application components communicate. Defining your component strategy helps you choose the appropriate Azure service.
+Your first decision in your AI-ready application architecture design is to plan how the application components communicate. Defining your component strategy helps you choose the appropriate Azure service.
 
 Suppose you're designing the architecture for a home improvement video-sharing application for Tailwind Traders. You want your application to be as reliable and scalable as possible. You're planning to use Azure technologies to build a robust communication infrastructure. Before you can choose the appropriate Azure services, you need to design how each application component communicates with the other components. For each type of communication, you might choose a different Azure technology.
 
@@ -18,13 +18,16 @@ In a message communication, the sending component expects the destination to pro
 
 Suppose a user uploads a new video by using your mobile video-sharing app. Your mobile app must send the video to the web API that runs in Azure. The video file must be sent, not just an alert that indicates there's a new video. The mobile app expects that the web API stores the new video in the database and makes the video available to other users.
 
+
+
 #### Events
 
 Now let's take a closer look at [events](/azure/event-grid/compare-messaging-services#event).
 
-- Events are lighter weight than messages and are most often used for broadcast communications.
+Events are lighter weight than messages and are most often used for broadcast communications. An event-driven architecture consists of event producers that generate a stream of events, event consumers that listen for these events, and event channels that transfer events from producers to consumers.
+
+:::image type="content" source="../media/event-pull.png" alt-text="Diagram of an event with producers and subscribers." border="false":::
 
-- An event has two components, a _publisher_ and _subscribers_. The event publisher sends the event. The event subscribers receive events.
 
 With events, receiving components generally decide the communications in which they're interested and then subscribe to those events. An intermediary manages the subscription process. The intermediary uses services like Azure Event Grid or Azure Event Hubs. When publishers send an event, the intermediary routes that event to any interested parties. This pattern is known as a _publish-subscribe_ architecture and is the most used. 
 
@@ -40,6 +43,8 @@ Events have the following characteristics:
 
 - An event is a discrete unit that's unrelated to other events, but an event might be part of a related and ordered series.
 
+
+
 ### Things to consider when choosing messages or events
 
 Review the following scenarios regarding when to choose message or event communication for your application architecture for Tailwind Traders.
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/3-design-messaging-solution.md b/learn-pr/wwl-azure/design-application-architecture/includes/3-design-messaging-solution.md
@@ -4,7 +4,9 @@ One of your design tasks for Tailwind Traders is to recommend a design for their
 - Ensure all content files are uploaded to the web API reliably from the mobile app. Files include text, images, and video.
 - Deliver details about new files directly to the app, such as when a customer posts a new product review or a video is added. 
 
-For these app requirements, the ideal solution is a message-based system.
+For these app requirements, the ideal solution is a message-based system. This video from the Developer course explains the different message queue solutions.
+
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=69784674-a8c7-42e9-b7ce-b239a865aafc]
 
 ### Things to know about Azure Queue Storage
 
@@ -40,12 +42,6 @@ For these app requirements, the ideal solution is a message-based system.
 
 Azure Service Bus message queues are intended for enterprise applications, such as an app that uses communication protocols and different data contracts. 
 
-#### Publish-subscribe topics
-
-[Azure Service Bus publish-subscribe topics](/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions) are like queues but can have multiple subscribers. When a message is sent to a topic, multiple components can be triggered to perform a task. 
-
-:::image type="content" source="../media/service-bus-topic.png" alt-text="Illustration that shows a sender and multiple receivers communicating through subscriptions." border="false":::
-
 #### Business scenario
 
 Consider the scenario where a customer is watching a video on an app. The app supports both user history and fan lists. You can support both actions by using publish-subscribe topic attributes:
@@ -64,4 +60,7 @@ Each Azure messaging solution has a slightly different set of features and capab
 | --- | --- |
  **Azure Queue Storage** | _You want a simple queue to organize messages_.<br><br> _You need an audit trail of all messages that pass through the queue_.<br><br>  _The queue storage exceeds 80 GB_.<br><br> _You'd like to track progress for processing a message inside of the queue_. |
 |  **Azure Service Bus** <br> _message queues_ |_You require an at-most-once delivery guarantee_.<br><br> _You require at-least-once message processing (PeekLock receive mode)_.<br><br> _You require at-most-once message processing (ReceiveAndDelete receive mode)_.<br><br> _You want to group messages into transactions_.<br><br> _You want to receive messages without polling the queue_.<br><br> _You need to handle messages larger than 64 KB_.<br><br> _The queue storage doesn't exceed 80 GB_.<br><br> _You'd like to publish and consume batches of messages_. |
-| **Azure Service Bus** <br> _publish-subscribe topics_ | _You need multiple receivers to handle each message_.<br><br> _You expect multiple destinations for a single message but need queue-like behavior_. | 
+| **Azure Service Bus** <br> _publish-subscribe topics_ | _You need multiple receivers to handle each message_.<br><br> _You expect multiple destinations for a single message but need queue-like behavior_. | 
+
+> [!TIP]
+> Continue your learning with the [Discover Azure message queues](/training/modules/discover-azure-message-queue/) module. 
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/4-design-event-hub-messaging-solution.md b/learn-pr/wwl-azure/design-application-architecture/includes/4-design-event-hub-messaging-solution.md
@@ -2,7 +2,9 @@ Certain applications produce a massive number of events from almost as many sour
 
 Suppose you're designing the architecture for a Tailwind Traders home security monitoring application. Each security system has a dozen or more cameras sensors. Before the house can be deemed secure, the sensors and cameras are connected to a test harness and put through their paces. Additionally, cached video camera footage data is streamed when the security system is connected to the datacenter monitoring headquarters.
 
-For this architecture, you might choose a messaging solution that uses _event hubs_. Event hubs can receive and process millions of events per second. Data sent to an event hub can be transformed in real time and stored for later analysis. 
+For this architecture, you might choose a messaging solution that uses _event hubs_. Event hubs can receive and process millions of events per second. Data sent to an event hub can be transformed in real time and stored for later analysis. This on-demand video from the Developer course provides a nice overview of Event Hubs.
+
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=4cf29c37-5ebd-4eb8-8b15-23b9ecdae040]
 
 ### Things to know about Azure Event Hubs
 
@@ -54,4 +56,7 @@ As you plan for how Azure Event Hubs can be a part of your messaging solution, c
 
 - **Consider message failures**. Remember Azure Event Hubs doesn't handle messages that aren't processed as expected. Suppose a message consumer malfunctions because of data format. Event Hubs won't detect this issue. The message remains until its `time-to-live` setting expires.
 
-- **Consider data stream access**. Event Hubs adds received events to the end of its data stream, and the events are ordered according to the time they're received. Event consumers can seek along the data stream by using time offsets.
+- **Consider data stream access**. Event Hubs adds received events to the end of its data stream, and the events are ordered according to the time they're received. Event consumers can seek along the data stream by using time offsets.
+
+> [!TIP]
+> Learn more with the [Explore Azure Event Hubs](/training/modules/azure-event-hubs/) module. 
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/5-design-event-driven-solution.md b/learn-pr/wwl-azure/design-application-architecture/includes/5-design-event-driven-solution.md
@@ -6,7 +6,11 @@ Let's reconsider our design for the Tailwind Traders product demo application, a
 
 ### Things to know about Azure Event Grid
 
-[Azure Event Grid](/azure/event-grid/overview) is a fully managed event routing service that runs on [Azure Service Fabric](/azure/service-fabric/service-fabric-overview). Event Grid exists to make it easier to build event-based and serverless applications on Azure. Examine the following characteristics of the service.
+[Azure Event Grid](/azure/event-grid/overview) is a fully managed event routing service that runs on [Azure Service Fabric](/azure/service-fabric/service-fabric-overview). Event Grid exists to make it easier to build event-based and serverless applications on Azure. 
+
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=1c380564-a19d-49a4-9902-8509a0bcfc30]
+
+Review the following characteristics of the service.
 
 - Azure Event Grid aggregates all your events and provides routing from any source to any destination. 
 
@@ -48,4 +52,7 @@ Azure Event Grid can be an ideal solution for an event-driven application archit
 
 - **Consider linking services**. Link Azure services together to form an event and data pipeline stream. In this scenario, Azure Event Grid responds to events in other services. The following illustration demonstrates how several Azure services can be linked together as an event and data pipeline to stream data.
    
-   :::image type="content" source="../media/services-integration.png" alt-text="Illustration that shows how Azure Event Hubs, Event Grid, and Functions link together to respond to events and stream data." border="false":::
+   :::image type="content" source="../media/services-integration.png" alt-text="Illustration that shows how Azure Event Hubs, Event Grid, and Functions link together to respond to events and stream data." border="false":::
+
+> [!TIP]
+> Consider reviewing the [Explore Azure Event Grid](/training/modules/azure-event-grid/) module.
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/6-design-caching-solution.md b/learn-pr/wwl-azure/design-application-architecture/includes/6-design-caching-solution.md
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/7-design-api-integration.md b/learn-pr/wwl-azure/design-application-architecture/includes/7-design-api-integration.md
diff --git a/learn-pr/wwl-azure/design-application-architecture/includes/8-design-automated-app-deployment-solution.md b/learn-pr/wwl-azure/design-application-architecture/includes/8-design-automated-app-deployment-solution.md
diff --git a/learn-pr/wwl-azure/design-application-architecture/index.yml b/learn-pr/wwl-azure/design-application-architecture/index.yml
diff --git a/learn-pr/wwl-azure/design-application-architecture/media/azure-cache-for-redis.png b/learn-pr/wwl-azure/design-application-architecture/media/azure-cache-for-redis.png
diff --git a/learn-pr/wwl-azure/design-application-architecture/media/event-pull.png b/learn-pr/wwl-azure/design-application-architecture/media/event-pull.png
diff --git a/learn-pr/wwl-azure/design-application-architecture/media/service-bus-queue.png b/learn-pr/wwl-azure/design-application-architecture/media/service-bus-queue.png
diff --git a/learn-pr/wwl-azure/design-application-architecture/media/service-bus-topic.png b/learn-pr/wwl-azure/design-application-architecture/media/service-bus-topic.png
