Bird
Raised Fist0
Denoframework~20 mins

Environment variables on Deploy in Deno - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
Deno Deploy Env Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ component_behavior
intermediate
2:00remaining
How does Deno access environment variables during runtime?
Consider this Deno code snippet that tries to read an environment variable named API_KEY. What will be the output if API_KEY is not set in the environment?
Deno
console.log(Deno.env.get('API_KEY'))
AThrows a runtime error
Bnull
CEmpty string
Dundefined
Attempts:
2 left
💡 Hint
Think about what Deno.env.get returns when the variable is missing.
📝 Syntax
intermediate
2:00remaining
Which code correctly sets environment variables for a Deno deploy script?
You want to set environment variables for your Deno deploy script using a deno.json configuration file. Which snippet correctly defines an environment variable API_SECRET with value mysecret?
A{ "env": { "API_SECRET": "mysecret" } }
B{ "environment": { "API_SECRET": "mysecret" } }
C{ "env_vars": { "API_SECRET": "mysecret" } }
D{ "variables": { "API_SECRET": "mysecret" } }
Attempts:
2 left
💡 Hint
Check the official Deno deploy configuration keys for environment variables.
🔧 Debug
advanced
2:00remaining
Why does this Deno deploy script fail to read environment variables?
Given this Deno deploy script snippet, why does console.log(Deno.env.get('TOKEN')) print undefined even though you set TOKEN in your deploy dashboard environment variables?
Deno
export default {
  async fetch(request) {
    console.log(Deno.env.get('TOKEN'));
    return new Response('Hello');
  }
};
ADeno.env.get cannot access environment variables in deploy edge functions
BYou must explicitly allow environment variable access in the deploy permissions
CThe environment variable was not set in the deploy dashboard correctly
DThe environment variable name is case-sensitive and TOKEN was set as token
Attempts:
2 left
💡 Hint
Double-check the dashboard: correct project, name, value, and redeploy after changes.
🧠 Conceptual
advanced
2:00remaining
How are environment variables securely managed in Deno Deploy?
Which statement best describes how environment variables are handled securely in Deno Deploy?
AEnvironment variables are stored encrypted and injected only into server-side code with explicit permissions
BEnvironment variables are injected at build time and cannot be changed at runtime
CEnvironment variables are accessible to all client-side code for flexibility
DEnvironment variables are passed as query parameters to the deployed script
Attempts:
2 left
💡 Hint
Consider security best practices for secrets in cloud deployments.
❓ state_output
expert
2:00remaining
What is the output of this Deno deploy script when environment variable GREETING is set to Hello?
Analyze this Deno deploy script. It reads an environment variable GREETING and returns it in the response. What will the response body be if GREETING is set to Hello in the deploy environment?
Deno
export default {
  async fetch(request) {
    const greeting = Deno.env.get('GREETING') ?? 'Hi';
    return new Response(greeting);
  }
};
AHi
BHello
Cundefined
DThrows a runtime error
Attempts:
2 left
💡 Hint
Deno Deploy supports Deno.env.get for environment variables set in the dashboard.

Practice

(1/5)
1. What is the main purpose of environment variables when deploying a Deno application?
easy
A. To keep secrets and settings outside the code for security and flexibility
B. To write all configuration directly inside the source code
C. To make the application run faster by hardcoding values
D. To store user data permanently on the server

Solution

  1. Step 1: Understand environment variables role

    Environment variables store secrets and settings outside the code to avoid exposing sensitive data.
  2. Step 2: Recognize deployment best practices

    Keeping secrets outside code allows changing settings without modifying the app, improving security and flexibility.
  3. Final Answer:

    To keep secrets and settings outside the code for security and flexibility -> Option A
  4. Quick Check:

    Environment variables = external secrets/settings [OK]
Hint: Environment variables hold secrets outside code [OK]
Common Mistakes:
  • Thinking environment variables are for storing user data
  • Hardcoding secrets inside source code
  • Believing environment variables speed up code execution
2. Which of the following is the correct way to read an environment variable named API_KEY in a Deno script?
easy
A. const key = getenv("API_KEY");
B. const key = process.env.API_KEY;
C. const key = Deno.env.get("API_KEY");
D. const key = env.API_KEY;

Solution

  1. Step 1: Recall Deno environment variable syntax

    Deno uses Deno.env.get("NAME") to access environment variables.
  2. Step 2: Compare options

    const key = Deno.env.get("API_KEY"); matches Deno syntax; others are from Node.js or incorrect.
  3. Final Answer:

    const key = Deno.env.get("API_KEY"); -> Option C
  4. Quick Check:

    Deno.env.get("API_KEY") = correct syntax [OK]
Hint: Use Deno.env.get("VAR_NAME") to read env variables [OK]
Common Mistakes:
  • Using Node.js syntax like process.env in Deno
  • Calling undefined functions like getenv
  • Accessing env variables without Deno.env.get
3. Given the following Deno code snippet deployed with environment variable PORT=8080, what will be the output?
const port = Deno.env.get("PORT") || "3000";
console.log(`Server running on port ${port}`);
medium
A. Server running on port 3000
B. Server running on port 8080
C. Server running on port undefined
D. Error: PORT is not defined

Solution

  1. Step 1: Check environment variable value

    The environment variable PORT is set to "8080" in deployment.
  2. Step 2: Evaluate fallback logic

    The code uses Deno.env.get("PORT") || "3000", so it uses "8080" because PORT exists.
  3. Final Answer:

    Server running on port 8080 -> Option B
  4. Quick Check:

    PORT=8080 overrides default 3000 [OK]
Hint: Env var set? Use it; else fallback value [OK]
Common Mistakes:
  • Assuming fallback value always prints
  • Expecting error if env var exists
  • Confusing undefined with fallback
4. You deployed a Deno app but reading environment variables returns undefined. Which fix will solve this problem?
medium
A. Restart the app without setting variables
B. Change Deno.env.get to process.env
C. Hardcode variables inside the source code
D. Set environment variables in the deployment platform settings

Solution

  1. Step 1: Identify cause of undefined env variables

    Undefined means variables are not set in the deployment environment.
  2. Step 2: Apply correct fix

    Setting environment variables in deployment platform ensures Deno.env.get can read them.
  3. Final Answer:

    Set environment variables in the deployment platform settings -> Option D
  4. Quick Check:

    Env vars must be set in deploy settings [OK]
Hint: Always set env vars in deployment platform [OK]
Common Mistakes:
  • Using Node.js syntax in Deno
  • Hardcoding secrets instead of setting env vars
  • Restarting app without setting variables
5. You want to deploy a Deno app that uses an environment variable MODE to switch between 'development' and 'production'. Which approach correctly uses environment variables to change app behavior safely?
hard
A. Set MODE in deployment settings and use Deno.env.get("MODE") in code to conditionally run features
B. Hardcode const MODE = "production" in source code and redeploy to change
C. Use a config file checked into source with MODE value
D. Ask users to input MODE at runtime every time

Solution

  1. Step 1: Understand environment variable usage for modes

    Environment variables allow switching modes without changing code.
  2. Step 2: Choose safe and flexible method

    Setting MODE in deployment and reading it with Deno.env.get enables safe conditional logic.
  3. Final Answer:

    Set MODE in deployment settings and use Deno.env.get("MODE") in code to conditionally run features -> Option A
  4. Quick Check:

    Env vars control modes safely without code changes [OK]
Hint: Use env vars to toggle modes, not hardcoding [OK]
Common Mistakes:
  • Hardcoding mode and redeploying for changes
  • Storing secrets or modes in config files checked into source
  • Asking users to input mode every run
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