adding summary and faqs

Author: anupras-mohapatra-arm

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/2-environment-setup.md

@@ -13,7 +13,7 @@ Set up an Arm Cobalt environment first, then keep your toolchain and runtime con
 
 Start with the [Azure Cobalt Learning Path](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cobalt/) and complete VM provisioning.
 
-This path was validated with Ubuntu 24.04 LTS on Azure Cobalt in `westus2` (example VM size: `Standard_D2ps_v6`, 2 vCPUs).
+The Learning Path was validated with Ubuntu 24.04 LTS on Azure Cobalt in `westus2` (example VM size: `Standard_D2ps_v6`, 2 vCPUs).
 
 ### Install tools on the Azure virtual machine
 

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/_index.md

@@ -15,13 +15,66 @@ learning_objectives:
 
 prerequisites:
     - Azure account with permissions to create virtual machines
+    - An Azure Cobalt 100-based virtual machine
     - Azure CLI (`az`) installed locally
     - Docker and .NET 9 SDK familiarity
     - Basic Linux command-line knowledge
 
+# START generated_summary_faq
+generated_summary_faq:
+  template_version: summary-faq-v3
+  generated_at: '2026-07-06T20:45:31Z'
+  generator: ai
+  ai_assisted: true
+  ai_review_required: true
+  model: gpt-5
+  prompt_template: summary-faq-v3
+  source_hash: af2852fa1dd4be29fbbc90cffe30efbecf96abad0d960681950ee1b104722e60
+  summary_generated_at: '2026-07-06T20:45:31Z'
+  summary_source_hash: af2852fa1dd4be29fbbc90cffe30efbecf96abad0d960681950ee1b104722e60
+  faq_generated_at: '2026-07-06T20:45:31Z'
+  faq_source_hash: af2852fa1dd4be29fbbc90cffe30efbecf96abad0d960681950ee1b104722e60
+  summary: >-
+    You'll learn how to migrate a .NET nopCommerce application to an
+    Arm-based virtual machine powered by Azure Cobalt 100, create a reproducible baseline, and apply
+    measured runtime tuning. First, you'll pin a specific nopCommerce release, verify a clean build,
+    and capture an endpoint baseline on Arm to control for drift. By running dependency discovery and generating SBOM, you'll surface direct, transitive, and native payloads early to reduce surprises during
+    deployment. You'll compare and choose a containerization path between a Dockerfile workflow and a .NET
+    SDK publish with guardrails for multi-architecture delivery. Finally, you'll apply
+    architecture-conditional runtime settings and validate them against fixed workloads so you
+    can keep or discard changes based on repeatable results.
+  faqs:
+  - question: How should I choose the Azure VM configuration for the baseline?
+    answer: >-
+      Provision an Azure Cobalt environment as described in the Azure Cobalt Learning Path and
+      keep the toolchain and runtime configuration stable across runs. The flow was validated
+      with Ubuntu 24.04 LTS in `westus2` on an example size of `Standard_D2ps_v6`.
+  - question: What should I record when pinning the nopCommerce source?
+    answer: >-
+      Check out the specified release tag and run `git rev-parse --short=10` to capture the exact
+      commit. Record the tag and short commit alongside the baseline results to avoid dependency
+      drift.
+  - question: How do I map direct and transitive dependencies before migration?
+    answer: >-
+      From the repository root, use `rg -n "<PackageReference|<ProjectReference" src` to identify
+      direct references and the owning projects. Then generate an SBOM and review transitive packages
+      to uncover native payloads that could affect Arm deployment.
+  - question: Which containerization path should I start with?
+    answer: >-
+      Use the Dockerfile workflow as the default path for nopCommerce. Switch to .NET SDK publish
+      when you want MSBuild-owned image metadata and have a repeatable plan for native packages,
+      ensuring the SDK image matches Linux runtime dependencies and smoke-test results.
+  - question: How do I know performance tuning changes took effect?
+    answer: >-
+      Stop the baseline process, set the runtime environment variables, and restart the application
+      so the .NET runtime reads the new settings. Measure with fixed workloads and compare against
+      the Arm endpoint baseline, keeping settings outside the code to switch profiles without
+      rebuilding.
+# END generated_summary_faq
+
 author: Joe Stech
 
-generate_summary_faq: true
+generate_summary_faq: false
 rerun_summary: false
 rerun_faqs: false