Why deployment target affects architecture in Astro - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the deployment target in Astro config.

Astro

export default {
  output: '[1]',
};

Drag options to blanks, or click blank then click option'

Astatic

Bnode

Cnetlify

Dvercel

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing server options like node or netlify when deploying a static site.

Not specifying any output.

The static output mode is used for static site deployment, which affects how Astro builds the site.

2fill in blank

medium

Complete the code to import the correct adapter for deploying to Vercel.

Astro

import [1] from '@astrojs/vercel/serverless';

Drag options to blanks, or click blank then click option'

Avercel

BvercelStatic

CvercelEdge

DvercelServer

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect adapter names like vercelStatic or vercelEdge.

Forgetting to import the adapter before using it.

The correct import for Vercel server adapter is vercel.

3fill in blank

hard

Fix the error in the Astro config by completing the adapter assignment.

Astro

export default {
  adapter: [1],
};

Drag options to blanks, or click blank then click option'

AvercelAdapter()

Bvercel

Cvercel()

Dadapter.vercel()

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning the adapter without parentheses.

Using incorrect variable names.

The adapter must be called as a function, so vercel() is correct.

4fill in blank

hard

Fill both blanks to configure Astro for Netlify deployment with the correct import and adapter call.

Astro

import [1] from '@astrojs/netlify/functions';

export default {
  adapter: [2](),
};

Drag options to blanks, or click blank then click option'

Anetlify

BnetlifyAdapter

CNetlify

DnetlifyFunctions

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for import and adapter call.

Capitalizing adapter names incorrectly.

The correct import and adapter call use netlify as the identifier.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps deployment targets to their adapter imports.

Astro

const adapters = {
  'vercel': [1],
  'netlify': [2],
  'static': [3]
};

Drag options to blanks, or click blank then click option'

Avercel()

Bnetlify()

Cstatic()

Dadapter()

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting parentheses after adapter names.

Using a generic adapter() call for all keys.

Each deployment target key maps to its adapter function call.

Practice

1. Why does the deployment target affect the architecture of an Astro project?

easy

A. Because it controls the font sizes used in the UI

B. Because it determines how and where the project is built and served

C. Because it decides the color scheme of the website

D. Because it changes the programming language used in the project

Solution

1. Step 1: Understand deployment target role

   The deployment target tells Astro how to build the project, such as static site or server-rendered.

2. Step 2: Connect deployment target to architecture

   This choice affects the build output, hosting options, and runtime behavior, shaping the architecture.

3. Final Answer:

   Because it determines how and where the project is built and served -> Option B

4. Quick Check:

   Deployment target = build and serve method [OK]

Hint: Deployment target controls build and hosting method [OK]

Common Mistakes:

• Thinking deployment target changes programming language
• Confusing deployment target with UI design choices
• Assuming deployment target affects only performance

2. Which of the following is a correct way to specify a deployment target in Astro's configuration?

easy

A. Adding deploymentTarget = 'vercel' in the HTML head

B. Using setDeployment('cloudflare') in a component script

C. "adapter: netlify()" inside the astro.config.mjs file

D. Writing deploy: 'static' in the CSS file

Solution

1. Step 1: Identify correct config location

   Astro uses astro.config.mjs to set deployment adapters.

2. Step 2: Recognize correct syntax

   Setting adapter: netlify() inside the config file is the proper way.

3. Final Answer:

   "adapter: netlify()" inside the astro.config.mjs file -> Option C

4. Quick Check:

   Deployment target set in config file [OK]

Hint: Deployment targets go in astro.config.mjs adapters [OK]

Common Mistakes:

• Trying to set deployment target in HTML or CSS
• Using non-existent functions like setDeployment()
• Confusing deployment target with runtime code

3. Given this Astro config snippet:

import vercel from '@astrojs/vercel';
export default {
  adapter: vercel()
};

What is the expected deployment behavior?

medium

A. The project builds a static site with no server functions

B. The project runs only on local development servers

C. The project uses Netlify-specific features

D. The project deploys with serverless functions on Vercel

Solution

1. Step 1: Identify adapter used

   The snippet imports and uses the '@astrojs/vercel' adapter, which targets Vercel platform.

2. Step 2: Understand Vercel adapter behavior

   This adapter enables serverless functions and dynamic rendering on Vercel.

3. Final Answer:

   The project deploys with serverless functions on Vercel -> Option D

4. Quick Check:

   Vercel adapter = serverless deployment [OK]

Hint: Adapter name hints deployment platform and features [OK]

Common Mistakes:

• Assuming Vercel adapter builds only static sites
• Confusing local dev with deployment behavior
• Mixing up Netlify and Vercel features

4. You set adapter: netlify() in your config but get a build error saying the adapter is missing. What is the likely cause?

medium

A. You forgot to install the adapter package via npm

B. The adapter name is misspelled in the config

C. Astro does not support Netlify deployment

D. You need to add the adapter in your HTML file

Solution

1. Step 1: Understand adapter usage

   Astro requires installing adapter packages separately before use.

2. Step 2: Identify common cause of missing adapter error

   Not installing the adapter package via npm causes build errors.

3. Final Answer:

   You forgot to install the adapter package via npm -> Option A

4. Quick Check:

   Missing adapter error = missing npm install [OK]

Hint: Always npm install adapter packages before building [OK]

Common Mistakes:

• Assuming Astro lacks Netlify support
• Thinking adapter goes in HTML instead of config
• Ignoring npm install step

5. You want to deploy an Astro project that uses server-side rendering (SSR) and dynamic API routes. Which deployment target should you choose and why?

hard

A. Netlify adapter, because it supports SSR and serverless functions

B. Static site adapter, because SSR is not needed for dynamic content

C. Static site adapter, because it is faster for all apps

D. No adapter needed, just upload files to any web host

Solution

1. Step 1: Identify requirements

   The project needs SSR and dynamic API routes, which require server-side code execution.

2. Step 2: Match deployment target to needs

   Netlify adapter supports SSR and serverless functions, enabling dynamic behavior.

3. Step 3: Exclude static-only options

   Static adapters cannot handle SSR or dynamic APIs, so they are unsuitable.

4. Final Answer:

   Netlify adapter, because it supports SSR and serverless functions -> Option A

5. Quick Check:

   SSR + dynamic API = serverless adapter [OK]

Hint: SSR needs serverless adapter like Netlify or Vercel [OK]

Common Mistakes:

• Choosing static adapter for SSR needs
• Thinking no adapter is needed for dynamic routes
• Assuming static is always faster regardless of app type