Bird
Raised Fist0
Vueframework~20 mins

Server routes and API in Vue - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
Server Routes & API Mastery
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ component_behavior
intermediate
2:00remaining
What does this Vue component display after fetching data?

Consider this Vue 3 component using the Composition API. It fetches user data from an API route and displays the user's name.

import { ref, onMounted } from 'vue';

export default {
  setup() {
    const userName = ref('');
    onMounted(async () => {
      const response = await fetch('/api/user');
      const data = await response.json();
      userName.value = data.name;
    });
    return { userName };
  }
}

Assuming the API returns { "name": "Alice" }, what will the component render inside <div>?

Vue
<template>
  <div>{{ userName }}</div>
</template>

<script setup>
import { ref, onMounted } from 'vue';

const userName = ref('');
onMounted(async () => {
  const response = await fetch('/api/user');
  const data = await response.json();
  userName.value = data.name;
});
</script>
AThe div will remain empty because fetch is asynchronous and userName is never updated.
BThe div will show 'Alice' after the fetch completes.
CThe div will show '[object Promise]' because fetch returns a promise.
DThe div will show 'undefined' because data.name is not set.
Attempts:
2 left
💡 Hint

Remember that ref is reactive and updates the template when its value changes.

📝 Syntax
intermediate
1:30remaining
Which option correctly defines a Vue 3 API route handler using server routes?

In a Vue 3 project using server routes, you want to create an API endpoint that returns JSON with a message.

Which code snippet correctly exports the handler?

Aexport default async function() { return JSON.stringify({ message: 'Hello' }) }
Bexport function handler() { return { message: 'Hello' } }
Cexport default () => { return { message: 'Hello' } }
Dexport default defineEventHandler(() => ({ message: 'Hello' }))
Attempts:
2 left
💡 Hint

Look for the official way to define event handlers in Vue server routes.

🔧 Debug
advanced
2:00remaining
Why does this Vue 3 server route handler cause a runtime error?

Examine this server route handler code:

export default defineEventHandler(async (event) => {
  const body = await useBody(event);
  return { greeting: `Hello, ${body.name}` };
});

When sending a POST request with JSON { "name": "Bob" }, the server crashes with TypeError: useBody is not a function. Why?

AThe handler must not be async to use <code>useBody</code>.
BThe <code>body</code> variable is undefined because the request has no body.
CThe <code>useBody</code> function is not imported or available in this context.
DThe event parameter is missing required properties for <code>useBody</code>.
Attempts:
2 left
💡 Hint

Check if all helper functions are imported or globally available.

❓ state_output
advanced
2:00remaining
What is the final state of the Vue component after multiple API calls?

This Vue 3 component fetches a counter value from an API and increments it on button click:

import { ref } from 'vue';

export default {
  setup() {
    const count = ref(0);
    async function fetchCount() {
      const res = await fetch('/api/counter');
      const data = await res.json();
      count.value = data.count;
    }
    async function increment() {
      await fetch('/api/counter/increment', { method: 'POST' });
      await fetchCount();
    }
    fetchCount();
    return { count, increment };
  }
}

If the initial API returns { count: 5 } and each increment increases the count by 1 on the server, what will count.value be after calling increment() twice?

Vue
<template>
  <div>{{ count }}</div>
  <button @click="increment">Increment</button>
</template>
A7
B6
C8
D5
Attempts:
2 left
💡 Hint

Each increment call updates the server count and then fetches the new value.

🧠 Conceptual
expert
1:30remaining
Which statement best describes the role of server routes in Vue 3 projects?

Choose the most accurate description of server routes in Vue 3 applications.

AServer routes handle backend logic and API responses, allowing separation from frontend code while sharing the same project.
BServer routes are used only for client-side routing and navigation between pages.
CServer routes automatically generate static HTML pages without any backend logic.
DServer routes replace Vue components and are used to build the entire UI.
Attempts:
2 left
💡 Hint

Think about the difference between frontend and backend responsibilities.

Practice

(1/5)
1. What is the main purpose of server routes in a Vue app using Nitro?
easy
A. To style the frontend components
B. To handle backend requests and send responses
C. To manage client-side state only
D. To create animations on the page

Solution

  1. Step 1: Understand server routes role

    Server routes act as backend endpoints that receive requests from the frontend.
  2. Step 2: Identify their function in Vue Nitro

    They process these requests and return data or responses, enabling communication between frontend and backend.
  3. Final Answer:

    To handle backend requests and send responses -> Option B
  4. Quick Check:

    Server routes = backend communication [OK]
Hint: Server routes handle backend requests, not frontend styling [OK]
Common Mistakes:
  • Confusing server routes with frontend styling
  • Thinking server routes manage only client state
  • Assuming server routes create animations
2. Which of the following is the correct way to define a server route in a Vue Nitro project?
easy
A. app.get('/api', () => 'Hello')
B. const route = () => { console.log('Hello') }
C. export default defineEventHandler(() => { return { message: 'Hello' } })
D. function serverRoute() { return 'Hello' }

Solution

  1. Step 1: Recognize Nitro server route syntax

    In Vue Nitro, server routes export a default function using defineEventHandler that returns data.
  2. Step 2: Check each option

    export default defineEventHandler(() => { return { message: 'Hello' } }) uses defineEventHandler and returns an object, which is correct. Others either lack export, use wrong syntax, or are not Nitro style.
  3. Final Answer:

    export default defineEventHandler(() => { return { message: 'Hello' } }) -> Option C
  4. Quick Check:

    Use defineEventHandler for Nitro routes [OK]
Hint: Look for export default with defineEventHandler [OK]
Common Mistakes:
  • Missing export default
  • Not using defineEventHandler
  • Using Express.js style instead of Nitro
3. Given this server route code in Vue Nitro:
export default defineEventHandler(() => { return { status: 'ok', count: 5 } })

What will the frontend receive when calling this API?
medium
A. Undefined
B. A string 'ok5'
C. An error because of missing await
D. { status: 'ok', count: 5 }

Solution

  1. Step 1: Analyze the returned object

    The route returns an object with keys status and count, so the response is JSON with those values.
  2. Step 2: Understand Nitro response behavior

    Nitro automatically serializes the returned object to JSON for the frontend.
  3. Final Answer:

    { status: 'ok', count: 5 } -> Option D
  4. Quick Check:

    Returned object = JSON response [OK]
Hint: Returned object becomes JSON response automatically [OK]
Common Mistakes:
  • Expecting string concatenation
  • Thinking await is needed for sync return
  • Assuming undefined if no explicit JSON
4. What is wrong with this Vue Nitro server route code?
export default () => { return { message: 'Hi' } }
medium
A. Missing defineEventHandler wrapper
B. Return value must be a string
C. Export default is not allowed
D. Arrow function syntax is invalid

Solution

  1. Step 1: Check Nitro route requirements

    Vue Nitro requires server routes to export a default function wrapped with defineEventHandler.
  2. Step 2: Identify missing part

    The code exports a function but does not use defineEventHandler, so it won't work as a proper Nitro route.
  3. Final Answer:

    Missing defineEventHandler wrapper -> Option A
  4. Quick Check:

    Always wrap route with defineEventHandler [OK]
Hint: Always use defineEventHandler for server routes [OK]
Common Mistakes:
  • Forgetting defineEventHandler
  • Thinking return must be string
  • Confusing export default rules
5. You want to create a server route in Vue Nitro that returns a list of users filtered by a query parameter `role`. Which code correctly accesses the query and returns filtered users?
hard
A. export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) })
B. export default defineEventHandler(() => { return users })
C. export default defineEventHandler(event => { const role = event.node.req.url.split('role=')[1]; return users.filter(u => u.role === role) })
D. export default defineEventHandler(event => { const role = event.query.role; return users.filter(u => u.role === role) })

Solution

  1. Step 1: Understand query access in Nitro

    Vue Nitro provides a helper getQuery(event) to safely get query parameters from the request.
  2. Step 2: Check each option for correct query usage

    export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) }) uses getQuery(event).role correctly. export default defineEventHandler(event => { const role = event.node.req.url.split('role=')[1]; return users.filter(u => u.role === role) }) manually parses URL which is error-prone. export default defineEventHandler(() => { return users }) ignores query. export default defineEventHandler(event => { const role = event.query.role; return users.filter(u => u.role === role) }) uses event.query which is not standard.
  3. Final Answer:

    export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) }) -> Option A
  4. Quick Check:

    Use getQuery(event) to read query params [OK]
Hint: Use getQuery(event) to access query parameters [OK]
Common Mistakes:
  • Parsing URL manually instead of getQuery
  • Using event.query which is undefined
  • Ignoring query parameters
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard