Skip to content

Commit

Permalink
general/drills: Add "Database Application" written task as exam
Browse files Browse the repository at this point in the history
- Add Markdown file storing the question scenario and the questions
- Modify `config.yaml` to render the new task

Signed-off-by: Petru-Vlad Ionescu <[email protected]>
  • Loading branch information
vladiouz authored and teodutu committed Mar 17, 2024
1 parent a9f776c commit ae4a05d
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 0 deletions.
45 changes: 45 additions & 0 deletions chapters/general/drills/tasks/database-application.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Database Application

## Scenario

We aim to run a database application in a containerized solution (Docker, Podman) for ease of deployment and isolation.
Running in a container involves isolating the filesystem (and necessary files), necessary processes, computing resources (CPU, memory, disk), and the network portion.
The database application will be accessible from outside the container through a virtual network.

Answer the following questions with "True" or "False" and justify the answer.
Justification should be simple, 2-3 sentences for each answer.

## Questions

1. The database application can only be implemented as a static executable, not a dynamic one.
Answer: False

1. Within the container, the application will use virtual memory mechanisms.
Answer: True

1. Within the container, the application can use the `fork()` system call.
Answer: True

1. The database application can use pipes to communicate outside the container.
Answer: False

1. Information from the application's filesystem is lost when the container terminates.
Answer: False

1. The application can be multi-threaded.
Answer: True

1. For synchronization, the application can only use mutexes, not spinlocks.
Answer: False

1. Processes within the container do have PIDs.
Answer: False

1. The application in the container can have buffer overflow vulnerabilities.
Answer: True

1. Memory within the container cannot be visible from outside the container, even by a privileged account.
Answer: False

1. The application exclusively spends time in user mode, not in kernel mode.
Answer: False
1 change: 1 addition & 0 deletions config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -263,6 +263,7 @@ docusaurus:
- Distributed System/: distributed-system.md
- Aggregator Application/: aggregator-application.md
- Benchmarking Application/: benchmarking-application.md
- Database Application/: database-application.md
- Hackathons:
path: content/assignments
subsections:
Expand Down

0 comments on commit ae4a05d

Please sign in to comment.