Inter Tests Site

Question 1

According to Part 2, what is the 'backend'?

The part that runs inside your web browser The part of the application that runs on the company's servers, not on your computer or phone The visual design of the website A type of database

Question 2

What is the 'frontend'?

The part that runs inside your web browser and is what you see and click on The database server The company's internal network A programming language

Question 3

How is Ruby on Rails described in Part 2?

A database engine A framework written in Ruby that makes it faster to build a web application's backend A JavaScript testing tool A type of API

Question 4

According to Part 2, what does REST mean as an API style?

One single address describing exactly what data is wanted An older, common API style with many different addresses, one for each type of information A style used only for WebSockets A database query language

Question 5

What is GraphQL, as defined in Part 2?

The same thing as REST, just renamed A style of API with exactly one address, where the frontend describes precisely what information it wants A JavaScript bundler A database management tool

Question 6

What is a 'Component' in the context of React, per Part 2?

A database table A reusable, self-contained chunk of a webpage built with React A single GraphQL address A backend testing file

Question 7

What does a 'Session' allow the server to do, according to Part 2?

Store project budgets Remember that your specific browser has already logged in, so you don't have to log in on every page Automatically calculate project status Bundle JavaScript files together

Question 8

What is CSRF, as explained in Part 2?

A tool for bundling JavaScript A type of security attack where a bad website tricks your browser into secretly sending a request to a site you're logged into A method for testing frontend components The company's login page

Question 9

What is an ADR (Architecture Decision Record)?

A database backup file A short written record explaining one specific technical decision, why it was made, alternatives considered, and downsides accepted A type of automated test A GraphQL query

Question 10

How many ADRs (Architecture Decision Records) does this project have, per Part 2?

7 10 14 20

Question 11

What version of Ruby (the programming language) does this project use?

3.2 4.0.2 2.7 5.1

Question 12

What version of Ruby on Rails is used as the backend framework?

7.0 6.1 8.1.3 9.0

Question 13

What version of PostgreSQL is used as the database?

14 15 16 17

Question 14

What version of React is used to build the visual interface?

17 18 19 20

Question 15

What tool makes styling the visual design faster in this project, and what version is used?

Bootstrap 5 Tailwind CSS, version 4.0 Sass, version 1.0 Bulma, version 3.0

Question 16

What is Kamal, as listed in Part 3?

A frontend testing library Rails' own tool for pushing the packaged application onto real production servers The database engine The GraphQL gem

Question 17

What version of Jest, and what companion tool, are used for frontend testing?

Jest version 29, together with Testing Library version 16 Jest version 20, together with Enzyme Jest version 30, together with Cypress Jest version 15, together with Mocha

Question 18

According to Part 4, what is the one address ('doorway') that all information passing between browser and server goes through?

A GET request to /api/data A POST request to /graphql A PUT request to /projects A GET request to /dashboard

Question 19

What is the fourth, smaller connection running alongside the main GraphQL doorway, per Part 4?

A second REST API A WebSocket connection that stays open constantly for live updates An email server connection A backup database connection

Question 20

What does every page Rails sends to the browser actually contain?

A fully-formed webpage with text and layout already filled in One empty div and nothing else Only CSS styling A JSON file of project data

Question 21

What is Rails' actual job on this project, per Part 4?

Rendering the entire visible interface Sending the nearly empty starting page, answering GraphQL requests, owning the database, tracking sessions, and pushing live updates Only handling styling with Tailwind Bundling JavaScript files

Question 22

Where does the main GraphQL schema file (the 'rulebook') live in the code?

app/graphql/mega_app_schema.rb app/models/schema.rb config/graphql_schema.rb app/controllers/schema.rb

Question 23

In GraphQL terms, what is a 'query'?

An action that changes information A question that only reads information and changes nothing A database migration A WebSocket message

Question 24

What does the code line 'policy_scope(Project)' do?

Deletes all projects Uses Pundit to filter the list of projects down to only what this user is allowed to see Creates a new project Logs the user out

Question 25

What is the single JavaScript file that is the starting point for everything React does?

index.js main.jsx application.js bundle.js

Question 26

What does the 'react-dashboard-root' box on the page get filled with?

LoginForm ProjectDashboard ProjectDetail MockSessionSelector

Question 27

In the Apollo Client setup code, what does the csrfLink do before every request leaves the browser?

Encrypts the entire request body Reads the current CSRF token off the page and attaches it as a header Deletes the Apollo cache Logs the user out automatically

Question 28

According to Part 9, why was esbuild chosen as the bundler over other tools?

It is free and open-source only It is extremely fast and requires no complicated setup file It supports Hot Module Replacement out of the box It was the only tool compatible with Rails

Question 29

What accepted downside comes from using esbuild, per Part 9?

It is very slow to bundle files There is no Hot Module Replacement, so the browser tab must be manually reloaded after every change It cannot bundle React code It requires a paid license

Question 30

What caused the 'caches' naming collision bug described in Part 9?

A typo in the Rails routes file A variable inside an Apollo Client dependency named 'caches' overlapping with the browser's own built-in 'caches' feature Two database tables having the same name A missing CSRF token

Question 31

What specific conflict caused the team to remove Turbo Drive, per Part 9?

It slowed down database queries It intercepted form submissions (like the login form) before React could handle them properly It broke the WebSocket connection It conflicted with Tailwind CSS

Question 32

Why did the team keep the default behavior of wrapping mutation information inside one container object, per Part 9?

Because it made the app run faster Because changing it would require extra, unnecessary configuration work for no real benefit Because Pundit required it Because React cannot handle multiple separate arguments

Question 33

According to Part 10, what efficient technique do many RSpec backend tests use?

They always send a real web request They skip the slower step of sending an actual web request and call the core logic directly They run only once a week They only test the frontend

Question 34

What do frontend (Jest) tests deliberately avoid checking, per Part 10?

Visible button text Internal implementation details, instead checking things the way a real person would interact with the page Whether the component renders at all The GraphQL schema

Question 35

What is the 'subtle trap' with the frontend testing tool described in Part 10?

It automatically fixes mismatches A mismatch between the test's fake data and what the component actually asks for causes it to silently skip that part rather than error It requires a live database connection It only runs in production

Question 36

According to Part 10, what honest testing gap exists in the project?

There is no backend testing at all A tool for full, browser-level, start-to-finish testing is installed but no actual tests using it currently exist Frontend tests are never run There is no way to test GraphQL mutations

Question 37

What else is worth knowing when switching between backend and frontend testing work, per Part 10?

Both tools use identical syntax for everything The two testing tools use slightly different wording for making comparisons in code, making it easy to use the wrong one Only one tool can be used per day Frontend tests must be run before backend tests

Question 38

Per Part 12, what are the very first two commands you run to get the project onto your computer?

Installing Docker and starting Rails Copying the project's code from wherever it is stored, then moving into that project's folder Creating a database and running migrations Logging into GitLab and creating a branch

Question 39

What three things run at once when starting the project on a normal day (after the first-ever setup)?

The database, the email server, and Docker The web server, a tool watching for JavaScript changes, and a tool watching for styling changes RSpec, Jest, and GitLab CI React, Apollo Client, and Pundit

Question 40

Where must every single command related to this project be run, per Part 12?

Directly on your own computer Inside the contained Docker environment Only on the production server Inside a virtual machine unrelated to Docker

Question 41

What are the three things you should always do, in order, before starting any actual coding task?

Write the code, test it, then document it Read existing similar code, check for an existing decision record, and check the architecture explanation document if still unsure Ask a manager, write tests, then deploy Restart Docker, clear the cache, and rebuild JavaScript

Question 42

When making a change to the database structure itself, what happens automatically after you run the structural change file?

Nothing happens automatically A separate summary file updates itself automatically, and you must remember to save that update too All tests are deleted The application restarts in production mode

Question 43

If your JavaScript changes aren't showing up in the browser, what should you remember, per Part 12?

The app has Hot Module Replacement so it should update instantly There is no automatic instant refresh feature — you must manually trigger a rebuild and reload the browser tab You must restart your entire computer JavaScript changes are applied automatically on save

Question 44

According to Part 14, how is a database best thought of, simply?

As a single giant file As a set of organized spreadsheets that are connected to each other As a type of API As a WebSocket connection

Question 45

How many main databases ('spreadsheets') does this project have, per Part 14?

Two Three Four Five

Question 46

What does the third main database do, per Part 14?

Stores every project's budget Connects people and projects together, recording who is assigned to which project and in what role Stores every person's salary only Stores client organization information

Question 47

What does the first main database store, per Part 14?

Client organization details Every person's account information: login details, access tier, department, and salary Project statuses only Just WebSocket messages

Question 48

In Part 4's step-by-step sequence, what happens if Rails checks and finds you are not already logged in?

It sends you to the login page instead of the homepage It shows the dashboard anyway It crashes the application It automatically logs you in as a guest

Question 49

Which folder in the GraphQL code contains one file per action, such as sign_in.rb and update_project_status.rb?

The types folder The mutations folder The resolvers folder The policies folder

Question 50

What tool, per Part 3, handles authorization (deciding who is allowed to see or edit what)?

Devise Pundit CanCanCan Warden

INTRANET TEST 1: Vocabulary, Tech Stack, Architecture, Build/Test/Workflow