{
  "id": "10",
  "content": [
    {
      "type": "heading",
      "text": "Build a Site Successfully from DNS Up"
    },
    {
      "type": "text",
      "html": "A reliable launch starts with a domain inventory, DNS plan, hosting target, email plan, canonical host, HTTPS, redirects, analytics, backups, monitoring, and a rollback path."
    },
    {
      "type": "text",
      "html": "DNS is quiet when it works and painful when it is guessed. Successful sites treat DNS as infrastructure: documented, reviewed, tested, and owned."
    },
    {
      "type": "callout",
      "style": "info",
      "html": "<strong>Practice:</strong> Use a launch checklist before every domain change. Include current records, intended records, TTL plan, validation steps, responsible person, and rollback notes."
    }
  ],
  "quiz": {
    "questions": [
      {
        "id": "q1",
        "type": "single",
        "text": "What should a DNS-based launch plan include?",
        "options": [
          {
            "id": "a",
            "text": "DNS, hosting, email, HTTPS, redirects, analytics, and rollback"
          },
          {
            "id": "b",
            "text": "Only a random CNAME with no notes"
          },
          {
            "id": "c",
            "text": "Only a new button color"
          }
        ],
        "correct": [
          "a"
        ]
      },
      {
        "id": "q2",
        "type": "single",
        "text": "How should DNS be treated for successful sites?",
        "options": [
          {
            "id": "a",
            "text": "As documented and owned infrastructure"
          },
          {
            "id": "b",
            "text": "As something to guess under pressure"
          },
          {
            "id": "c",
            "text": "As unrelated to launches"
          }
        ],
        "correct": [
          "a"
        ]
      }
    ]
  }
}
