Why production Deno needs careful architecture - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Deno require explicit permissions in production?

Deno runs scripts with explicit permissions for file, network, and environment access. What is the main reason this permission system is crucial in production environments?

A To enable scripts to access all system resources without restrictions

B To make scripts run faster by disabling unused features

C To allow scripts to automatically update without user approval

D To prevent unauthorized access and improve security by limiting what scripts can do

💡 Hint

Think about how limiting access can protect your system from harmful actions.

Deno's permission system is designed to improve security by explicitly controlling what scripts can access. This is especially important in production to avoid accidental or malicious resource access.

❓ component_behavior

intermediate

How does Deno's single executable design affect production deployment?

Deno ships as a single executable that includes the runtime and standard library. How does this design impact deploying Deno applications in production?

A It forces developers to compile their code into native binaries before deployment

B It requires installing multiple dependencies manually before running scripts

C It simplifies deployment by avoiding separate runtime installations and version mismatches

D It limits the ability to update parts of the runtime independently

💡 Hint

Consider how having everything in one package affects setup.

Deno's single executable design means you only need to deploy one file, reducing complexity and avoiding issues with mismatched runtime versions.

❓ lifecycle

advanced

What is a key architectural consideration for managing Deno script lifecycle in production?

In production, managing the lifecycle of Deno scripts (start, stop, restart) is important. Which architectural approach best supports this management?

A Using a process manager or container orchestration to monitor and restart scripts automatically

B Running scripts manually from the command line without supervision

C Embedding scripts directly into HTML files for browser execution

D Disabling all permissions to prevent scripts from running

💡 Hint

Think about how servers keep apps running smoothly without manual restarts.

Using process managers or container orchestration tools helps keep Deno scripts running reliably by automatically restarting them if they crash or stop.

🔧 Debug

advanced

What error occurs if a Deno script tries to access the network without permission?

Consider this Deno script run with no network permissions: ```ts const response = await fetch('https://example.com'); console.log(await response.text()); ``` What error will this code produce when run in production without network access permission?

A TypeError: response.text is not a function

B PermissionDenied: network access to 'https://example.com' is not allowed

C ReferenceError: fetch is not defined

D SyntaxError: Unexpected token 'await'

💡 Hint

Think about Deno's permission system blocking unauthorized actions.

Deno enforces permissions strictly. Without network permission, trying to fetch a URL causes a PermissionDenied error.

📝 Syntax

expert

Which Deno permission flag is required to read environment variables in production?

You want your Deno script to read environment variables safely in production. Which command line flag grants this permission?

A --allow-env

B --allow-read

C --allow-net

D --allow-run

💡 Hint

Environment variables are not files or network resources.

The --allow-env flag grants permission to access environment variables in Deno.

Practice

1. Why is it important to plan permissions carefully when deploying a Deno app to production?

easy

A. Because Deno restricts access to files, network, and environment by default for security.

B. Because Deno automatically grants all permissions to any script.

C. Because permissions do not affect Deno apps in production.

D. Because permissions only matter during development, not in production.

Solution

1. Step 1: Understand Deno's default security model

   Deno runs scripts with no permissions by default to protect your system.

2. Step 2: Recognize the need for explicit permission granting in production

   In production, you must carefully grant only needed permissions to avoid security risks.

3. Final Answer:

   Because Deno restricts access to files, network, and environment by default for security. -> Option A

4. Quick Check:

   Default security = careful permission planning [OK]

Hint: Remember: Deno locks down permissions by default [OK]

Common Mistakes:

• Assuming Deno grants all permissions automatically
• Ignoring permissions in production
• Thinking permissions only matter during development

2. Which of the following is the correct way to run a Deno script with network access permission?

easy

A. deno run --allownetwork script.ts

B. deno run --net-allow script.ts

C. deno run --enable-network script.ts

D. deno run --allow-net script.ts

Solution

1. Step 1: Recall Deno's permission flags syntax

   Deno uses flags like --allow-net to grant network access.

2. Step 2: Identify the correct flag from options

   Only --allow-net matches Deno's official permission flag syntax.

3. Final Answer:

   deno run --allow-net script.ts -> Option D

4. Quick Check:

   Correct flag syntax = --allow-net [OK]

Hint: Look for exact permission flag syntax with dashes [OK]

Common Mistakes:

• Using incorrect flag names like --net-allow
• Combining words without dashes
• Assuming permission flags are optional

3. Consider this Deno code snippet:

try {
  const data = await Deno.readTextFile('config.json');
  console.log('Config loaded:', data);
} catch (error) {
  console.error('Failed to load config:', error.message);
}

What will happen if the file config.json does not exist and the script is run with deno run --allow-read script.ts?

medium

A. The catch block will run and print an error message.

B. The script will crash with an uncaught error.

C. The script will print 'Config loaded:' with empty data.

D. The script will silently ignore the error and continue.

Solution

1. Step 1: Understand try-catch behavior in async file reading

   If the file is missing, Deno.readTextFile throws an error caught by catch.

2. Step 2: Analyze the catch block's effect

   The catch block logs 'Failed to load config:' plus the error message.

3. Final Answer:

   The catch block will run and print an error message. -> Option A

4. Quick Check:

   Missing file triggers catch block [OK]

Hint: Missing file triggers catch block error handling [OK]

Common Mistakes:

• Expecting the script to crash without catch
• Assuming empty string is returned for missing file
• Thinking error is ignored silently

4. You have this Deno script:

const data = await Deno.readTextFile('data.txt');
console.log(data);

When running deno run script.ts without any flags, what error will you get?

medium

A. SyntaxError: Unexpected token

B. PermissionDenied: read access to "data.txt" is not allowed

C. ReferenceError: Deno is not defined

D. No error, script runs fine

Solution

1. Step 1: Recall Deno's default permission restrictions

   Deno denies file read access unless --allow-read is given.

2. Step 2: Identify the error from missing permission

   Running without --allow-read causes a PermissionDenied error.

3. Final Answer:

   PermissionDenied: read access to "data.txt" is not allowed -> Option B

4. Quick Check:

   Missing --allow-read causes PermissionDenied [OK]

Hint: No --allow-read means PermissionDenied error [OK]

Common Mistakes:

• Expecting syntax or reference errors
• Assuming script runs without permissions
• Confusing permission errors with runtime errors

5. You want to build a Deno app that reads a config file, fetches data from an API, and writes logs to a file. Which architecture approach best ensures security and maintainability in production?

hard

A. Grant all permissions globally and write all code in one file.

B. Run the app without permissions and rely on user input for data.

C. Use modular code, grant only needed permissions per module, and handle errors properly.

D. Avoid error handling to keep code simple and grant all permissions at runtime.

Solution

1. Step 1: Consider security by limiting permissions

   Grant only the permissions each module needs to reduce risk.

2. Step 2: Organize code modularly and handle errors

   Modular code improves maintainability; error handling improves reliability.

3. Final Answer:

   Use modular code, grant only needed permissions per module, and handle errors properly. -> Option C

4. Quick Check:

   Modular + limited permissions + error handling = best practice [OK]

Hint: Modular code + least permissions + error handling wins [OK]

Common Mistakes:

• Granting all permissions globally
• Ignoring error handling
• Putting all code in one file