```latex
% !TEX program = xelatex
\documentclass[11pt]{article}

% ── Fonts, layout, and packages ───────────────────────────────────────────────
\usepackage{fontspec}
\setmainfont{TeX Gyre Pagella}
\setsansfont{TeX Gyre Heros}
\setmonofont{JetBrains Mono}
\usepackage{xcolor}
\usepackage[a4paper,margin=0.7in]{geometry}
\usepackage{enumitem}
\usepackage{titlesec}
\usepackage{hyperref}
\hypersetup{
  colorlinks=true,
  urlcolor=[rgb]{0.0,0.2,0.6},
  linkcolor=[rgb]{0.0,0.2,0.6},
  citecolor=[rgb]{0.0,0.2,0.6}
}
\usepackage{fancyhdr}
\usepackage{microtype}
\usepackage{array}
\usepackage{multicol}
\usepackage{tabularx}
\usepackage{booktabs}
\usepackage{colortbl}
\usepackage{tikz}
\usetikzlibrary{arrows.meta,positioning,calc,fit,backgrounds}
\usepackage[most]{tcolorbox}
\tcbuselibrary{skins,breakable}
\usepackage{pifont}
\usepackage{advdate}

% ── Colour palette ────────────────────────────────────────────────────────────
\definecolor{SecNavy}{HTML}{0D3B6E}
\definecolor{SecRed}{HTML}{C8102E}
\definecolor{ExamGold}{HTML}{F2C94C}
\definecolor{InfoBlue}{HTML}{2D9CDB}
\definecolor{SoftGray}{HTML}{F4F6F8}
\definecolor{Ink}{HTML}{1F2937}
\definecolor{GreenOK}{HTML}{2E7D32}
\definecolor{Warn}{HTML}{B00020}
\definecolor{AccentBlue}{HTML}{1565C0}
\definecolor{AccentTeal}{HTML}{00695C}
\definecolor{RowShade}{HTML}{F0F4F8}

\pagecolor{white}
\color{Ink}
\emergencystretch=2em

% ── Section and list formatting ───────────────────────────────────────────────
\titleformat{\section}{\Large\bfseries\sffamily\color{SecRed}}{}{0em}{}
\titleformat{\subsection}{\large\bfseries\sffamily\color{Ink}}{}{0em}{}
\titleformat{\subsubsection}{\normalsize\bfseries\sffamily\color{Ink}}{}{0em}{}
\setlist[itemize]{topsep=4pt,itemsep=2pt,parsep=0pt,partopsep=2pt}
\setlist[enumerate]{topsep=4pt,itemsep=2pt,parsep=0pt,partopsep=2pt}

% ── Reusable callout boxes ────────────────────────────────────────────────────
\newtcolorbox{examhint}{
  enhanced, breakable,
  colback=ExamGold!20, colframe=SecRed!70!black,
  coltitle=black,
  title={Key Point}, fonttitle=\bfseries\sffamily,
  attach boxed title to top left={yshift=-2mm, xshift=3mm},
  boxed title style={colback=ExamGold, colframe=SecRed!70!black},
  left=6mm,right=6mm,top=3mm,bottom=3mm
}
\newtcolorbox{lecturehint}{
  enhanced, breakable,
  colback=SoftGray, colframe=InfoBlue!60!black,
  title={Note}, fonttitle=\bfseries\sffamily,
  left=6mm,right=6mm,top=3mm,bottom=3mm
}
\newtcolorbox{definition}{
  enhanced, breakable,
  colback=white, colframe=Ink!20!black,
  title={Definition}, fonttitle=\bfseries\sffamily,
  borderline west={2pt}{0pt}{InfoBlue},
  left=6mm,right=6mm,top=3mm,bottom=3mm
}
\newtcolorbox{examplebox}{
  enhanced, breakable,
  colback=white, colframe=Ink!20!black,
  title={Example}, fonttitle=\bfseries\sffamily,
  borderline west={2pt}{0pt}{SecRed},
  left=6mm,right=6mm,top=3mm,bottom=3mm
}
\newcommand{\cmark}{\textcolor{GreenOK}{\ding{51}}}
\newcommand{\xmark}{\textcolor{Warn}{\ding{55}}}

% ── Replace these values for each lesson ──────────────────────────────────────
\newcommand{\LessonTitle}{Lesson Title}
\newcommand{\LessonDomain}{Domain X: Domain Name}
\newcommand{\LessonNumber}{X.X.X}

% ── Branded title block ───────────────────────────────────────────────────────
\makeatletter
\def\maketitle{%
  \AdvanceDate[-1]
  \begin{tcolorbox}[
    enhanced, sharp corners, boxrule=0pt,
    colback=SecNavy, colframe=SecNavy,
    left=5mm, right=5mm, top=4mm, bottom=4mm,
    after skip=0pt,
  ]
    \begin{minipage}[c]{0.6\linewidth}
      {\fontsize{22}{24}\selectfont\sffamily\bfseries\color{white}PM}%
      \hspace{7pt}{\small\sffamily\color{white!60!SecNavy}ProfessorMesser.com}
    \end{minipage}%
    \begin{minipage}[c]{0.4\linewidth}
      \raggedleft{\small\sffamily\itshape\color{white!60!SecNavy}\today}
    \end{minipage}
  \end{tcolorbox}
  \AdvanceDate[1]
  \begin{tcolorbox}[
    enhanced, sharp corners,
    colback=white, frame hidden,
    before skip=0pt,
    borderline west={0.4pt}{0pt}{Ink!15},
    borderline east={0.4pt}{0pt}{Ink!15},
    borderline south={0.4pt}{0pt}{Ink!15},
    left=2mm, right=2mm, top=5mm, bottom=5mm,
  ]
    {\LARGE\sffamily\bfseries\color{Ink}\LessonTitle}
    \par\vspace{3pt}
    {\small\sffamily\color{SecNavy!80!black}%
      SY0-701 Series\enspace\textbullet\enspace
      \LessonDomain\enspace\textbullet\enspace
      Objective \LessonNumber}
  \end{tcolorbox}
  \vspace{1em}
}
\makeatother

% ── Footer ────────────────────────────────────────────────────────────────────
\pagestyle{fancy}
\fancyhf{}
\fancyfoot[L]{\small\sffamily\color{Ink}ProfessorMesser.com}
\fancyfoot[C]{\small\sffamily\color{Ink}\thepage}
% Always use the complete lesson number: X.X.X --- Lesson Title
\fancyfoot[R]{\small\sffamily\color{Ink}\LessonNumber\ --- \LessonTitle}
\renewcommand{\headrulewidth}{0pt}

\begin{document}
\maketitle

% ── OVERVIEW ──────────────────────────────────────────────────────────────────
\section*{Overview}

Start each note with a concise explanation of the lesson and a short list of the ideas it
covers. Write for recognition on the Security+ exam: define the concept, explain how it
works, and identify the wording that distinguishes it from related concepts.

\begin{itemize}
  \item State the primary security concept or objective.
  \item Explain the important mechanisms, workflow, or components.
  \item Include realistic examples and exam-recognition clues.
  \item End with a summary and quick-reference checklist.
\end{itemize}

\begin{examhint}
Use \textbf{Key Point} boxes for facts, distinctions, or scenario clues that are especially
likely to help identify the correct answer on an exam question.
\end{examhint}

% ── CONCEPT ───────────────────────────────────────────────────────────────────
\section*{Core Concept}

\begin{definition}
\textbf{Core concept} --- Put the exam-ready definition here. Define the term clearly
before discussing its implementation, benefits, limitations, or related technologies.
\end{definition}

Use normal paragraphs for the explanation. Add subsections only when they make the lesson
easier to scan. Keep the prose focused on what the technology does, where it is used, and
what a question scenario would look like.

\subsection*{How It Works}

When a process has distinct stages, present them in a simple sequence:
\begin{enumerate}
  \item Identify the request, condition, or security need.
  \item Apply the relevant control, policy, or technical mechanism.
  \item Validate the result and record or respond to the outcome.
\end{enumerate}

\begin{examplebox}
\textbf{Scenario:} Describe a realistic environment, identify the relevant clue, and state
why the concept is the best answer. Keep the example short and directly tied to the lesson.
\end{examplebox}

\begin{lecturehint}
Use \textbf{Note} boxes for useful context, operational cautions, or details that support
understanding but are not the central exam distinction.
\end{lecturehint}

% ── TIKZ DIAGRAM SAMPLES ─────────────────────────────────────────────────────
\section*{TikZ Diagram Samples}

Use TikZ diagrams when a picture makes a process, trust boundary, or relationship easier
to understand. Keep diagrams purposeful, labeled, and consistent with the page palette.
These two patterns cover most course-note visuals.

\subsection*{1. Process / Attack-Flow Diagram}

Use this pattern for a workflow, attack path, mitigation sequence, certificate process, or
other left-to-right progression. Replace the labels and colors; keep node names unique.

\begin{center}
\begin{tikzpicture}[
  node distance=0.9cm and 1.5cm,
  flowbox/.style={
    rectangle, rounded corners=4pt, draw=Ink!30, fill=SoftGray,
    minimum width=2.65cm, minimum height=0.9cm,
    font=\sffamily\footnotesize\bfseries, align=center
  },
  event/.style={
    rectangle, rounded corners=4pt, draw=Warn!60, fill=Warn!12,
    minimum width=2.45cm, minimum height=0.9cm,
    font=\sffamily\footnotesize\bfseries\color{Warn}, align=center
  },
  arr/.style={-{Stealth[length=5pt]}, thick, color=Ink!45},
  lbl/.style={font=\tiny\sffamily\color{Ink!60}, align=center}
]
  \node[flowbox, fill=AccentBlue!10, draw=AccentBlue!50] (identify) {Identify\\request or risk};
  \node[flowbox, right=of identify] (validate) {Validate identity\\or condition};
  \node[event, right=of validate] (decision) {Allow, deny,\\or detect event};
  \node[flowbox, fill=AccentTeal!10, draw=AccentTeal!50, right=of decision] (respond) {Apply control\\and record result};
  \node[flowbox, fill=ExamGold!20, draw=SecRed!55, below=0.8cm of decision] (fallback) {Compensating or\\response action};

  \draw[arr] (identify) -- node[above,lbl]{request} (validate);
  \draw[arr] (validate) -- node[above,lbl]{policy check} (decision);
  \draw[arr] (decision) -- node[above,lbl]{approved / alert} (respond);
  \draw[arr, dashed, color=SecRed!70!black] (decision) -- node[right,lbl]{exception} (fallback);
\end{tikzpicture}
\end{center}

\subsection*{2. Trust Boundary / Component Diagram}

Use this pattern to show a protected zone, network segment, PKI trust chain, zero-trust
access path, or any relationship between an untrusted source and protected resource.

\begin{center}
\begin{tikzpicture}[
  node distance=0.9cm and 2.1cm,
  box/.style={
    rectangle, rounded corners=4pt, draw=Ink!30, fill=SoftGray,
    minimum width=2.6cm, minimum height=0.9cm,
    font=\sffamily\footnotesize\bfseries, align=center
  },
  control/.style={
    rectangle, rounded corners=4pt, draw=AccentBlue!55, fill=AccentBlue!10,
    minimum width=2.7cm, minimum height=0.9cm,
    font=\sffamily\footnotesize\bfseries\color{AccentBlue}, align=center
  },
  resource/.style={
    rectangle, rounded corners=4pt, draw=AccentTeal!55, fill=AccentTeal!10,
    minimum width=2.7cm, minimum height=0.9cm,
    font=\sffamily\footnotesize\bfseries\color{AccentTeal}, align=center
  },
  arr/.style={-{Stealth[length=5pt]}, thick, color=Ink!45},
  lbl/.style={font=\tiny\sffamily\color{Ink!60}, align=center}
]
  \node[box, draw=Warn!55, fill=Warn!10, text=Warn] (source) {Untrusted user,\\device, or process};
  \node[control, right=of source] (pep) {Policy enforcement\\point / control};
  \node[resource, right=of pep] (resource) {Specific protected\\resource};
  \node[box, below=0.9cm of pep] (policy) {Identity, device posture,\\location, and policy};

  \draw[arr] (source) -- node[above,lbl]{access request} (pep);
  \draw[arr] (pep) -- node[above,lbl]{least-privilege\\access} (resource);
  \draw[arr, dashed] (policy) -- node[right,lbl]{evaluates context} (pep);

  \begin{scope}[on background layer]
    \node[draw=AccentTeal!40, fill=AccentTeal!4, rounded corners=6pt,
      fit=(pep)(resource)(policy), inner sep=8pt,
      label={[font=\tiny\sffamily\color{AccentTeal}]below:Protected / Trusted Zone}] {};
  \end{scope}
\end{tikzpicture}
\end{center}

\begin{lecturehint}
For every TikZ diagram: define reusable styles inside the \texttt{tikzpicture}, use
\texttt{node distance} and relative positioning rather than hard-coded coordinates when
possible, and use \texttt{font=\textbackslash sffamily\textbackslash footnotesize} for readable labels.
\end{lecturehint}

% ── REFERENCE TABLE ──────────────────────────────────────────────────────────
\section*{Reference Table}

Use a table when the reader needs a compact lookup rather than a visual relationship.

\begin{center}
\begin{tabularx}{0.97\textwidth}{
  >{\raggedright\arraybackslash\bfseries\sffamily}p{3.2cm}
  >{\raggedright\arraybackslash}X
  >{\raggedright\arraybackslash}X
}
\toprule
\textbf{Item} & \textbf{Purpose} & \textbf{Exam clue} \\
\midrule
\rowcolor{RowShade}
Control or mechanism A & Explain its primary function. & Include the words likely to appear in a scenario. \\[4pt]
Control or mechanism B & Explain its primary function. & Identify the differentiating condition. \\
\bottomrule
\end{tabularx}
\end{center}

% ── KEY DISTINCTIONS ──────────────────────────────────────────────────────────
\section*{Key Distinctions for the Exam}

% Do not use a standalone ``A vs. B'' comparison table as the only explanation.
% Explain each distinction with Key Point boxes like these.
\begin{examhint}
\textbf{Concept A vs. concept B} --- Explain the practical difference in complete
sentences. State what each concept does and the clue that identifies it in a scenario.
\end{examhint}

\begin{examhint}
\textbf{Scope or timing distinction} --- Explain whether the controls differ by where they
operate, when they act, who they affect, or the purpose they serve. This is where most
``which is the best answer?'' clues belong.
\end{examhint}

\begin{examhint}
\textbf{Exam wording} --- State the trigger words or facts that should lead the student to
the correct concept. Avoid vague statements; tie every clue to a meaningful difference.
\end{examhint}

% ── KEY CONCEPTS SUMMARY ──────────────────────────────────────────────────────
\section*{Key Concepts Summary}

\begin{definition}
\textbf{Core concept} --- Restate the central definition in one concise sentence.\\[4pt]
\textbf{Mechanism} --- State how the control, process, or technology operates.\\[4pt]
\textbf{Exam distinction} --- State the most important difference from the related concept
students are likely to confuse with it.
\end{definition}

% ── QUICK REFERENCE CHECKLIST ─────────────────────────────────────────────────
\section*{Quick Reference Checklist}

\begin{multicols}{2}
\begin{itemize}[leftmargin=8pt]
  \item Core concept and definition \cmark
  \item Primary purpose and scope \cmark
  \item Important workflow or components \cmark
  \item Relevant security control or mitigation \cmark
  \item Scenario clue for concept A \cmark
  \item Scenario clue for concept B \cmark
  \item Key distinction explained in prose \cmark
  \item Limitations or operational caveats \cmark
  \item Summary definitions reviewed \cmark
  \item Footer uses the complete X.X.X lesson number \cmark
\end{itemize}
\end{multicols}

\end{document}
```