Proctor Level2_144

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleDemo script pehle se practice: 5–7 min, Admin + User roles, saare mandatory features.

Suggested flow1) Register/login user
2) Admin login — CRUD
3) Approval/blacklist
4) Booking/apply + edge case
5) Search
6) Logout

Viva tipBolte-bolte dikhao. Code tab kholna jab poochhein.

SimplePehle 1-line definition, phir apne MAD1 project mein file dikhao, phir chhota example.

Suggested flow1) Concept kya hai?
2) Mere code mein kahan?
3) Example / demo
4) Edge case

Example

# related file: models.py / routes / template
# formula: request → check/auth → DB → render/redirect

Viva tipExact line yaad nahi to honestly related part dikhao. Bluff mat karo.

SimpleGET data read/show karta hai (idempotent). POST create/submit karta hai (form).

Example

@app.route('/login', methods=['GET', 'POST'])
def login():
    if request.method == 'POST':
        # validate + session
        ...
    return render_template('login.html')

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleLive UI change: relevant CSS/HTML template kholo — color, margin, flex, bootstrap class. Save + hard refresh.

Example

/* button red */
.btn-primary { background: red; }

/* center navbar item */
.navbar { justify-content: center; }

Viva tipDevTools se pehle try, phir file mein permanent change.

SimplePehle 1-line definition, phir apne MAD1 project mein file dikhao, phir chhota example.

Suggested flow1) Concept kya hai?
2) Mere code mein kahan?
3) Example / demo
4) Edge case

Example

# related file: models.py / routes / template
# formula: request → check/auth → DB → render/redirect

Viva tipExact line yaad nahi to honestly related part dikhao. Bluff mat karo.

SimplePehle 1-line definition, phir apne MAD1 project mein file dikhao, phir chhota example.

Suggested flow1) Concept kya hai?
2) Mere code mein kahan?
3) Example / demo
4) Edge case

Example

# related file: models.py / routes / template
# formula: request → check/auth → DB → render/redirect

Viva tipExact line yaad nahi to honestly related part dikhao. Bluff mat karo.

SimplePehle 1-line definition, phir apne MAD1 project mein file dikhao, phir chhota example.

Suggested flow1) Concept kya hai?
2) Mere code mein kahan?
3) Example / demo
4) Edge case

Example

# related file: models.py / routes / template
# formula: request → check/auth → DB → render/redirect

Viva tipExact line yaad nahi to honestly related part dikhao. Bluff mat karo.

Simplemodels.py = har table ki class: columns, PK/FK, relationships. Yeh Model layer hai.

Suggested flow1) Classes list karo
2) Har table ka kaam 1 line
3) Relationships (1-M / M-M)
4) Constraints (unique, nullable)

Example

class Lot(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    name = db.Column(db.String(80), nullable=False)
    spots = db.relationship('Spot', backref='lot', lazy=True)

SimpleLive UI change: relevant CSS/HTML template kholo — color, margin, flex, bootstrap class. Save + hard refresh.

Example

/* button red */
.btn-primary { background: red; }

/* center navbar item */
.navbar { justify-content: center; }

Viva tipDevTools se pehle try, phir file mein permanent change.

Simpleurl_for endpoint name se URL banata hai — hardcode path mat likho.

Example

url_for('auth.login')
url_for('static', filename='css/style.css')

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimplePOST naya janam (har baar naya id). PUT poori photo replace. PATCH sticker chipkao.

POST create, not idempotent. PUT full update, idempotent. PATCH partial.

POST ki jagah PUT se REST semantics toot. GET typically no body.

CRUD map: POST create, GET read, PUT/PATCH update, DELETE delete.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Example

POST /api/venues
PUT  /api/venues/1   {all fields}
PATCH /api/venues/1 {only name}

Project example: POST /api/venues create. PUT /venues/1 saari fields. PATCH sirf name.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleCamera pe clearly college/IITM ID dikhao — naam aur photo match hone chahiye.

Viva tipPehle se ID haath mein rakho, glare mat aane do. Iske baad GitHub + project run.

SimpleExaminer portal wala submitted ZIP chahta hai. Local extra changes mat dikhana.

Suggested flow1) Portal ZIP download
2) Extract
3) venv + pip install -r requirements.txt
4) flask run / python app.py

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

Simple2 or 3 from package.json + 1 difference Composition/filters.

Which version are you using.

SPA = ek HTML, Vue Router se views, full reload nahi. MPA = MAD1 Jinja har URL naya HTML.

Vue Router: routes array, router-view, router-link, meta.auth + beforeEach guard. Dynamic /venues/:id → $route.params.id.

Vite/CLI SFC + npm build dist/. CDN script tag, no SFC. Jo tumne use kiya wahi justify. Flask send_from_directory('dist') production pattern.

Project example: package.json vue field.

Project example: package.json vue field.

SimpleCDN = Vue script tag se, jaise pen drive. CLI/Vite = poori factory (SFC, npm, bundle).

CDN: no build, chhote apps, exam PC pe Node nahi to bhi chal. Weak: no .vue compile, 3rd-party cache, scale/team.

CLI/Vite: Single File Components, env, code-split, production dist/. Scalable.

Examiner 'which + why' — jo use kiya wahi justify, doosra naam rato mat.

Example

<!-- CDN -->
<script src="https://unpkg.com/vue@3/dist/vue.global.js"></script>

# Vite
npm run dev
npm run build

Project example: CDN: index.html unpkg vue. CLI: package.json, npm run serve / vite.

Viva tipCDN scalable large teams ke liye weak (no SFC compile, caching 3rd party). Examiner 'which + why' poochta hai — jo use kiya wahi justify karo.

SimpleDemo script pehle se practice: 5–7 min, Admin + User roles, saare mandatory features.

Suggested flow1) Register/login user
2) Admin login — CRUD
3) Approval/blacklist
4) Booking/apply + edge case
5) Search
6) Logout

Viva tipBolte-bolte dikhao. Code tab kholna jab poochhein.

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

Simplemodels.py har table ki class hai — columns, PK/FK, relationships. Yeh Model layer hai.

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

Simplebackref reverse attribute auto banata hai. back_populates dono sides explicitly naam dete ho — clearer.

Example

# backref
spots = db.relationship('Spot', backref='lot')
# spot.lot available

# back_populates
spots = db.relationship('Spot', back_populates='lot')
# Spot.lot = db.relationship('Lot', back_populates='spots')

SimpleRBAC = Role Based Access Control. Roles (admin/user) se permissions milti hain, har user pe alag list nahi.

Example

if current_user.role != 'admin':
    flash('Not allowed')
    return redirect(url_for('user.home'))

Simplelogin_required jaisa decorator protected routes pe: session nahi to login redirect.

Example

def login_required(fn):
    @wraps(fn)
    def wrapper(*a, **k):
        if 'user_id' not in session:
            return redirect(url_for('auth.login'))
        return fn(*a, **k)
    return wrapper

SimpleCache = pehli baar hisaab karke copy rakh lo, doosri baar copy dikha do.

Baar-baar same expensive kaam (DB query, counting bookings) mat karo. Result Redis jaise store mein timeout ke saath rakh do.

Cache hit: key mil gayi, DB skip. Cache miss: DB se lao, SET karo, return karo.

Tradeoff: speed vs stale data. Admin naya venue add kare aur cache 50s ka ho to user purani list dekh sakta hai — isliye write pe invalidation zaroori hai.

Browser cache, Flask-Caching, Redis alag layers hain. MAD2 examiner Redis + @cache.cached code dekhta hai.

Example

@cache.cached(timeout=50, query_string=True)
@app.route('/api/shows')
def shows():
    return jsonify([s.serialize() for s in Show.query.all()])

Project example: Admin dashboard counts / venues list cache. Create/update/delete ke baad cache.delete('venues').

Viva tipprint('DB queried') function ke andar laga ke miss/hit demo karo — hit pe print nahi chalega.

SimpleLive jobs: Redis, worker, beat, crontab abhi, logs + email/CSV.

Scheduled vs user-triggered dono dikhao. Missing feature honestly.

Examiner 2 cheezein: simple desi line + tumhare project ki exact file.

Pehle ID, GitHub, portal ZIP. Phir run: Redis + Flask + worker + beat + Vue. Feature demo: login, RBAC, cache hit/miss, Celery mail, search.

Line pe ungli: input kahan, kaunsa check, query/cache/task, JSON/UI. Copilot band. Jo nahi kiya honestly bolo + kaise add karte.

Suggested flow1) redis
2) worker
3) beat
4) crontab now
5) logs + MailHog

Example

CELERY_BEAT_SCHEDULE = {
  'daily-reminder': {
    'task': 'jobs.daily_reminder',
    'schedule': crontab(hour=18, minute=0),
  },
}

Project example: Change schedule current time. MailHog. Export button 202.

Simplev-if ghar se nikaal deta hai (DOM se). v-show sirf light band karta hai (display:none).

v-if false → element exist hi nahi — costly create/destroy, lekin secret HTML DOM mein nahi.
v-show → hamesha DOM, CSS hide, toggle tez.

Rare / permission UI: v-if (admin panel). Dropdown bar-bar: v-show.

: shorthand v-bind ka, v-if ka nahi.

Example

<div v-if="isAdmin">Admin panel</div>
<div v-show="open">Dropdown</div>

Project example: Admin links v-if="role==='admin'". FAQ accordion v-show="open".

Viva tipSecurity ke liye sirf v-if kaafi nahi — API 403 bhi chahiye.

SimpleStatus code server ka result: 200 OK, 302 redirect, 400 bad input, 401/403 auth, 404 not found, 500 server error.

SimpleDemo script pehle se practice: 5–7 min, Admin + User roles, saare mandatory features.

Suggested flow1) Register/login user
2) Admin login — CRUD
3) Approval/blacklist
4) Booking/apply + edge case
5) Search
6) Logout

Viva tipBolte-bolte dikhao. Code tab kholna jab poochhein.

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleRedis fridge pe sticky note hai — poori kitchen (database) kholne ki zarurat nahi.

Redis in-memory key-value store hai. Data RAM mein rehta hai, isliye disk wale SQLite/Postgres se kai guna tez.

MAD2 mein Redis do kaam karta hai:
1) Cache — same venue/show/dashboard JSON baar-baar DB se mat nikaalo.
2) Celery message broker — Flask task queue mein daalta hai, worker uthata hai.

Source of truth database hi hai. Redis band ho to cache miss ho jaata hai aur Celery queue ruk sakti hai. Crash pe cache gayab ho sakta hai — isliye important data sirf Redis mein mat rakho.

Example

import redis
r = redis.Redis(host='localhost', port=6379, db=0)
r.set('venues', json.dumps(data), ex=30)
print(r.get('venues'))

Project example: GET /api/venues pehle Redis dekho. Miss pe SQLAlchemy query, phir SET with timeout. Celery worker Redis list se daily reminder uthata hai.

Viva tipCache ke liye db=1, broker ke liye db=0 rakhna smart hai taaki keys mix na hon. Viva mein redis-cli ping → PONG dikhana strong hai.

SimpleVue = UI ka smart assistant. Data badlo, screen khud update. MAD1 Jinja har click pe naya HTML.

Progressive frontend framework. Components, reactivity, directives.

MAD2 SPA: ek index.html, Vue Router pages, Flask sirf JSON.

Fayde: easy, SFC, docs. Vs React: templates HTML-like, course sikhata hai. Vs plain JS: baar-baar DOM mat chhedo.

Example

<!-- HelloWorld.vue -->
<template>
  <h1>{{ msg }}</h1>
</template>
<script>
export default { data() { return { msg: 'Hello' } } }
</script>

Project example: Navbar.vue + views (Login, Dashboard). data() / setup() reactive. fetch APIs.

Viva tipFayde: easy, SFC, reactivity. Vs React: chhota learning curve. Vs plain JS: UI state auto-update.

SimpleMutations sync diary entry. Actions async kaam phir diary.

Direct state mutate action se Vuex 4 discouraged. Devtools time-travel mutations.

Purpose of Actions: API, phir commit. Purpose of Mutations: state change one place.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: action fetchVenues → commit setVenues. Mutation sirf array replace.

SimpleState management (Vuex/Pinia): shared app state. Advantage: props drilling kam, auth/cart central.

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleLive UI change: relevant CSS/HTML template kholo — color, margin, flex, bootstrap class. Save + hard refresh.

Example

/* button red */
.btn-primary { background: red; }

/* center navbar item */
.navbar { justify-content: center; }

Viva tipDevTools se pehle try, phir file mein permanent change.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleTheory = concepts: ORM, MVC, auth vs authz, Jinja inheritance, sessions. 1-line def + project example.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

Simplebackend create_app models api jobs. frontend src router. config env. README.

Don't read every file. 6 roles.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: tree command or VSCode explorer.

SimpleDemo 5–7 min ki kahani: saari roles, koi milestone skip nahi, bolte-bolte dikhao.

Examiner list tick karta hai. Crash ho to panic nahi — terminal error padho.

Code tab kholna jab poochhein. Extra uncommitted features mat dikhana agar portal ZIP mein nahi.

Suggested flow1) Register/login user
2) Admin login — CRUD
3) Approval/blacklist
4) Booking/apply + edge case
5) Search + charts
6) CSV export / email job
7) Logout

Project example: Jo statement/parking/jobs/tickets hai uske user+admin journeys.

Viva tipBol: 'Yahan overbooking rokta hoon'. Mandatory features pehle, polish baad.

Simplemodels.py tables ki blueprint. Har class ek table, har Column ek field.

PK id, FK dusri table, relationship dono taraf, serialize() JSON (password mat).
app factory db.init. resources APIs use models.

Examiner random line: type, nullable, unique, ondelete.

Suggested flow1) Har table → class
2) PK id
3) FK
4) relationship()
5) serialize()

Example

class Booking(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'))
    user = db.relationship('User', back_populates='bookings')

Project example: User, Role, Venue/Show/Booking (ya Drive/Application). Draw 1-M.

Viva tipExaminer random line poochhe: column type, FK, constraint. Draw 1-M / M-M on paper mentally.

SimpleEk Vue file: template, data, mounted fetch, methods save. 2 min.

Open any component. fetch + lifecycle.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: Booking.vue tour.

Project example: Booking.vue tour.

SimpleVue 3 naya engine: Composition API, fragments, better TS, tree-shaking. Vue 2 Options + filters.

mounted vs onMounted. Filters Vue 3 mein hata — computed/methods.

Version package.json / Vue.version se dikhao. Jo use kiya uske hooks bolo.

SPA = ek HTML, Vue Router se views, full reload nahi. MPA = MAD1 Jinja har URL naya HTML.

Vue Router: routes array, router-view, router-link, meta.auth + beforeEach guard. Dynamic /venues/:id → $route.params.id.

Vite/CLI SFC + npm build dist/. CDN script tag, no SFC. Jo tumne use kiya wahi justify. Flask send_from_directory('dist') production pattern.

Project example: package.json vue ^3.x. setup() + onMounted fetch.

Viva tipVersion package.json / Vue.version se dikhao. MAD2 dono allowed usually — jo use kiya uske hooks bolo (mounted vs onMounted).

SimpleCDN = Vue script tag se, jaise pen drive. CLI/Vite = poori factory (SFC, npm, bundle).

CDN: no build, chhote apps, exam PC pe Node nahi to bhi chal. Weak: no .vue compile, 3rd-party cache, scale/team.

CLI/Vite: Single File Components, env, code-split, production dist/. Scalable.

Examiner 'which + why' — jo use kiya wahi justify, doosra naam rato mat.

Example

<!-- CDN -->
<script src="https://unpkg.com/vue@3/dist/vue.global.js"></script>

# Vite
npm run dev
npm run build

Project example: CDN: index.html unpkg vue. CLI: package.json, npm run serve / vite.

Viva tipCDN scalable large teams ke liye weak (no SFC compile, caching 3rd party). Examiner 'which + why' poochta hai — jo use kiya wahi justify karo.

SimpleCDN isliye simple deploy, kabhi Node nahi chahiye viva machine pe.

Show <script src=vue> index.html. Tradeoff: SFC nahi, ek bada JS file.

Agar CLI use kiya to yeh answer ulta: SFC + build isliye CLI.

SPA = ek HTML, Vue Router se views, full reload nahi. MPA = MAD1 Jinja har URL naya HTML.

Vue Router: routes array, router-view, router-link, meta.auth + beforeEach guard. Dynamic /venues/:id → $route.params.id.

Vite/CLI SFC + npm build dist/. CDN script tag, no SFC. Jo tumne use kiya wahi justify. Flask send_from_directory('dist') production pattern.

Project example: index.html bottom script tags Vue + vue-router + app.js.

Simplesrc/components + views count. routes.length. Exact from project.

How many Vue files/components.

SPA = ek HTML, Vue Router se views, full reload nahi. MPA = MAD1 Jinja har URL naya HTML.

Vue Router: routes array, router-view, router-link, meta.auth + beforeEach guard. Dynamic /venues/:id → $route.params.id.

Vite/CLI SFC + npm build dist/. CDN script tag, no SFC. Jo tumne use kiya wahi justify. Flask send_from_directory('dist') production pattern.

Project example: ls | wc.

Project example: ls | wc.

Simplev-if ghar se nikaal deta hai (DOM se). v-show sirf light band karta hai (display:none).

v-if false → element exist hi nahi — costly create/destroy, lekin secret HTML DOM mein nahi.
v-show → hamesha DOM, CSS hide, toggle tez.

Rare / permission UI: v-if (admin panel). Dropdown bar-bar: v-show.

: shorthand v-bind ka, v-if ka nahi.

Example

<div v-if="isAdmin">Admin panel</div>
<div v-show="open">Dropdown</div>

Project example: Admin links v-if="role==='admin'". FAQ accordion v-show="open".

Viva tipSecurity ke liye sirf v-if kaafi nahi — API 403 bhi chahiye.

SimpleAxios HTTP library: JSON auto, interceptors, timeout. fetch built-in alternative.

Na use kiya: 'fetch native, extra lib nahi' valid.
Use kiya: interceptor mein token. Why didn't: deps kam.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Example

axios.get('/api/venues', { headers: { Authorization: 'Bearer ' + token } })

Project example: axios.defaults.headers.common.Authorization. baseURL :5000.

Viva tipNa use kiya to bolo: fetch native hai, extra lib nahi. Use kiya to interceptor mein token set karna dikhao.

SimpleOne component mounted fetch headers error. Line by line. Show a Vue component fetch and lifecycle.

async await.

JS browser ki language. const rebind nahi, let block. Arrow () => this lexical.

Promise: pending/fulfill/reject. async/await usko seedha padhne jaisa. try/catch await pe. Yeh Celery nahi — Celery Python worker.

fetch native AJAX. array.filter/map computed lists. Vue data reactive; plain JS DOM querySelector se manual.

Project example: Home.vue.

Project example: Home.vue.

Simpleres.ok false → JSON message state/toast. try/catch network.

Don't ignore 400. Show 'Already booked'.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Example

if (!res.ok) {
  const e = await res.json()
  this.error = e.message
}

Project example: book() method if (!res.ok) this.error = ...

SimpleVuex/Pinia ghar ka notice board. Har room (component) same user/token dekhe.

State data, mutations sync change, actions async API phir commit.

Local data() sirf us component. Token/user global.

Pinia Vue 3 official, kam boilerplate. Vuex older MAD2 still common.

Example

state: { user: null }
mutations: { setUser(s, u) { s.user = u } }
actions: { async login({ commit }, form) {
  const u = await api.login(form); commit('setUser', u)
}}

Project example: store user + token login action. Navbar getters isAdmin. Logout clear LS+state.

Viva tipLocal/Session storage persist ke liye, reactive share ke liye store. Pinia Vue 3 official, Vuex older.

SimpleVuex/Pinia ghar ka notice board. Har room (component) same user/token dekhe.

State data, mutations sync change, actions async API phir commit.

Local data() sirf us component. Token/user global.

Pinia Vue 3 official, kam boilerplate. Vuex older MAD2 still common.

Example

state: { user: null }
mutations: { setUser(s, u) { s.user = u } }
actions: { async login({ commit }, form) {
  const u = await api.login(form); commit('setUser', u)
}}

Project example: store user + token login action. Navbar getters isAdmin. Logout clear LS+state.

Viva tipLocal/Session storage persist ke liye, reactive share ke liye store. Pinia Vue 3 official, Vuex older.

SimpleMutations sync diary entry. Actions async kaam phir diary.

Direct state mutate action se Vuex 4 discouraged. Devtools time-travel mutations.

Purpose of Actions: API, phir commit. Purpose of Mutations: state change one place.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: action fetchVenues → commit setVenues. Mutation sirf array replace.

SimpleUngli rakhe to 4-line formula — panic ki jagah structure.

1) File ka role: model / Flask route / Vue SFC / celery task / config
2) Input kahan: JSON, params, token, props, $route
3) Kya kaam: query, cache, validation, .delay()
4) Output: jsonify, this.items, email, redirect

Unknown keyword: import, decorator, if, commit — har ka reason. Bluff mat.

Suggested flow1) Kaunsi layer?
2) Input?
3) DB/cache/task?
4) Response/UI?

Project example: Booking POST: jwt, seats check, commit, 201, Vue list push.

Viva tipUnknown keyword: import, decorator, if, commit — har ka reason. Panic mat.

SimpleLooks current_user.roles. Abort 403. JWT claims sometimes.

How @role_required works.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: Open flask-security / your decorator.

Project example: Open flask-security / your decorator.

Simplebackref jaadu se reverse attribute. back_populates dono taraf likho — clear.

backref='author' Post.author auto. New code back_populates preferred.

Examiner difference almost guaranteed.

ORM objects ko tables se map karta hai — raw SQL kam. SQLAlchemy MAD2 default.

class User(db.Model) + Column + relationship. query.filter_by / db.session.get. Fayda: portable SQLite→Postgres, injection se safer. Nuksaan: N+1, complex SQL.

SQLite file, zero server — course friendly. Postgres scale. Relationships: FK, backref, lazy/joinedload, cascade on delete. Constraints unique/not null integrity.

Bookings source of truth DB, Redis cache copy.

Example

posts = db.relationship('Post', backref='author')
# vs
posts = db.relationship('Post', back_populates='author')
Post.author = relationship('User', back_populates='posts')

Project example: User.bookings / Booking.user dono explicit back_populates.

SimpleCache = pehli baar hisaab karke copy rakh lo, doosri baar copy dikha do.

Baar-baar same expensive kaam (DB query, counting bookings) mat karo. Result Redis jaise store mein timeout ke saath rakh do.

Cache hit: key mil gayi, DB skip. Cache miss: DB se lao, SET karo, return karo.

Tradeoff: speed vs stale data. Admin naya venue add kare aur cache 50s ka ho to user purani list dekh sakta hai — isliye write pe invalidation zaroori hai.

Browser cache, Flask-Caching, Redis alag layers hain. MAD2 examiner Redis + @cache.cached code dekhta hai.

Example

@cache.cached(timeout=50, query_string=True)
@app.route('/api/shows')
def shows():
    return jsonify([s.serialize() for s in Show.query.all()])

Project example: Admin dashboard counts / venues list cache. Create/update/delete ke baad cache.delete('venues').

Viva tipprint('DB queried') function ke andar laga ke miss/hit demo karo — hit pe print nahi chalega.

SimpleData Redis process ki RAM mein rehta hai, laptop ke browser mein nahi.

Optional RDB/AOF files disk pe dump. Viva default: memory. Server-side.

redis-cli ping, INFO memory. Browser Application tab alag cheez (JWT).

Redis in-memory key-value store hai — fridge pe sticky note, poori kitchen (SQL database) har baar mat kholo.

MAD2 mein Redis do kaam: (1) cache — same venues/shows/dashboard JSON baar-baar DB se nahi (2) Celery broker — Flask task queue mein daalta hai, worker uthata hai.

Flow: cache.get(key) → hit pe return, miss pe SQLAlchemy + SET with timeout. Admin write ke baad cache.delete, warna stale list.

Source of truth database hi hai. Redis crash/band = cache miss (app chalni chahiye) + queue ruk sakti hai. Important bookings sirf Redis mein mat rakho.

Alag: Redis ≠ Memcached (Celery broker nahi). Redis ≠ localStorage (woh browser). redis-cli ping → PONG viva proof.

Project example: Flask machine pe redis-server. Vue sirf API call — Redis client nahi.

SimpleDono crontab(hour=17, minute=20). Same time fire OK — do alag tasks.

Ek schedule do tasks. Worker dono uthayega. Demo ke liye theek.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: Beat log two 'Sending due task' around 5:20.

SimplelocalStorage sessionStorage cookies IndexedDB memory Cache API. Types browser storage. Client-side storage.

What types available. Other than LS.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: We used LS for JWT. Cookies empty.

SimpleAPI summary → Chart.js canvas mounted. Colors array.

Booking karke update — cache invalidate stats.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: GET /api/admin/summary. new Chart(ctx, ...).

Simpledatasets[0].backgroundColor = 2 colors only. Extra hatao.

Chart.js. After change refresh / destroy recreate.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Example

backgroundColor: ['#36a2eb', '#ff6384']

Project example: AdminSummary chart options.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Simplemodels.py har table ki class hai — columns, PK/FK, relationships. Yeh Model layer hai.

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleChart.js frontend library. Backend counts bhejta hai, JS graph banata hai.

stats = {'booked': 10, 'cancelled': 2}

render_template('summary.html', stats=stats)
new Chart(ctx, {type:'bar', data:{labels:[...], datasets:[{data:[...]}]}})

Dynamic: har load pe query. Pie vs bar: Chart type change. Colors: backgroundColor array.
Swap graphs: HTML do canvas ki jagah badlo.

Yeh list filter/sort/display task hai. Query badlo, template same rakh sakte ho.

rows = Model.query.filter_by(status='approved').order_by(Model.name.asc()).all()

Jinja: {% for r in rows %}<tr><td>{{ r.name|upper }}</td></tr>{% endfor %}

{{ rows|length }} count dikhane ke liye.

Alphabet sort: order_by(Model.name). Status filter: filter_by(status='pending').
Assigned staff column: relationship se {{ booking.staff.name }}.

Yeh project-specific feature add/modify hai. 4 layers touch karo: model, route, template, validation.

1) Data chahiye to models.py mein column/relationship + DB update (ALTER / migrate / create_all).
2) Route: GET pe form/page, POST pe request.form se save, flash + redirect.
3) Template: input name=... Jinja se {{ obj.field }} display.
4) Rule: duplicate, range, role check backend pe.

Example naya field 'city':

user.city = db.Column(db.String(50))
user.city = request.form.get('city')
<input name='city'>  ...  {{ user.city }}

Simpleurl_for Flask function/endpoint name se URL generate karta hai, hardcode path nahi.

url_for('home') → '/'
url_for('edit_user', id=5) → '/user/5/edit'
Templates: href="{{ url_for('login') }}"

Parameter: endpoint ka naam (function name), plus route variables.
Galat naam: BuildError. Route rename karo to url_for automatic naya path dega — yahi fayda hai.

Simpleurl_for Flask function/endpoint name se URL generate karta hai, hardcode path nahi.

url_for('home') → '/'
url_for('edit_user', id=5) → '/user/5/edit'
Templates: href="{{ url_for('login') }}"

Parameter: endpoint ka naam (function name), plus route variables.
Galat naam: BuildError. Route rename karo to url_for automatic naya path dega — yahi fayda hai.

Simpleexaminer UI tweak maangta hai — CSS class ya inline, instantly dikhao.

Button color: <button class='btn btn-success'> ya style='background:#22c55e;color:#fff'
Navbar: navbar-dark bg-success / style='background:yellow' / fixed-bottom se neeche.
Center: .wrap { display:flex; justify-content:center; align-items:center; min-height:100vh; }
text-align:center heading ke liye. Bootstrap: d-flex justify-content-center, mx-auto, text-center.
Hover: .btn:hover { opacity:0.8; transform:scale(1.02); }
Half width: class='col-6' ya width:50%. Row→column: flex-direction:column / col-12 stack.
Login card: card shadow p-4 mx-auto (max-width:400px).
Table header green: th { background:green; color:white; } Bold column: td:nth-child(2){font-weight:bold}
Box shadow: box-shadow: 4px 4px 12px rgba(0,0,0,.3);
Background image: body { background: url('/static/bg.jpg') center/cover; }
Reset button: <button type='reset'>Clear</button>
Move button: ms-auto / position / flex order.
Jinja dashboard heading: <h1>{{ user.name }}'s Dashboard</h1>

Simpleexaminer UI tweak maangta hai — CSS class ya inline, instantly dikhao.

Button color: <button class='btn btn-success'> ya style='background:#22c55e;color:#fff'
Navbar: navbar-dark bg-success / style='background:yellow' / fixed-bottom se neeche.
Center: .wrap { display:flex; justify-content:center; align-items:center; min-height:100vh; }
text-align:center heading ke liye. Bootstrap: d-flex justify-content-center, mx-auto, text-center.
Hover: .btn:hover { opacity:0.8; transform:scale(1.02); }
Half width: class='col-6' ya width:50%. Row→column: flex-direction:column / col-12 stack.
Login card: card shadow p-4 mx-auto (max-width:400px).
Table header green: th { background:green; color:white; } Bold column: td:nth-child(2){font-weight:bold}
Box shadow: box-shadow: 4px 4px 12px rgba(0,0,0,.3);
Background image: body { background: url('/static/bg.jpg') center/cover; }
Reset button: <button type='reset'>Clear</button>
Move button: ms-auto / position / flex order.
Jinja dashboard heading: <h1>{{ user.name }}'s Dashboard</h1>

SimpleFlask Python ka micro web framework hai — routes, templates, request/response handle karta hai.

from flask import Flask
app = Flask(__name__)
@app.route('/')
def home():
    return 'Hello'
app.run(debug=True)  # default port 5000

__name__ se Flask ko pata chalta hai templates/static kahan se load karni hai. Hataoge to resource paths toot sakte hain.

Faydesimple, flexible, MAD1 syllabus. Nuksaan: bade features (admin, auth) khud jodne padte hain.

app.run() development server start karta hai. Production mein gunicorn/waitress.

Simpleurl_for Flask function/endpoint name se URL generate karta hai, hardcode path nahi.

url_for('home') → '/'
url_for('edit_user', id=5) → '/user/5/edit'
Templates: href="{{ url_for('login') }}"

Parameter: endpoint ka naam (function name), plus route variables.
Galat naam: BuildError. Route rename karo to url_for automatic naya path dega — yahi fayda hai.

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

Simpleextends poora layout inherit karta hai, include chhota piece insert karta hai.

extends: child page base.html ka structure use karti hai, blocks override karti hai. Ek hi parent.
include: navbar.html / footer.html jahan chaho insert. Kai baar use ho sakta hai.

base.html:

{% block content %}{% endblock %}

home.html:
{% extends 'base.html' %}
{% block content %}<h1>Home</h1>{% endblock %}

{% include 'navbar.html' %}  → navbar har page pe

Fayda: header/footer ek jagah, change once — saari pages update. MAD1 mein almost har project use karta hai.

SimpleConstraints rules hain jo galat data rok te hain. Referential integrity FK valid parent ko point kare.

PK, FK, UNIQUE, NOT NULL, CHECK (age >= 18). ORM Column flags yahi map karte hain.
SQL = language tables se baat. Database organized data store.
SQL View: saved query, table jaisi dikhti hai, data copy nahi.
Cluster: kai DB servers together (HA/scale) — MAD1 SQLite single file.
Entity mapping: class User → table user, attributes → columns.

SimpleJSON = JavaScript Object Notation — data exchange ka text format.

{"name": "Ram", "age": 20}
APIs, localStorage, Chart.js data. Python dict ↔ JSON.
Structured data: tables, fixed schema (SQL). Unstructured: images, logs, free text. JSON semi-structured.
SQL structured relational. Mongo unstructured/document.

SimpleHTTP stateless hai — har request independent, server previous request yaad nahi rakhta.

Isliye login ke baad bhi har request pe kaun ho yeh prove karna padta hai: cookie/session/JWT.
State = yaad rakhna (user_id, cart). HTTP khud nahi rakhta; Flask session iske upar layer hai.
Fayda: scale aasan, koi bhi server next request handle kar sake (sticky session ke bina, token use karke).

SimpleHTTP methods batate hain request kya karna chahti hai. Common: GET POST PUT PATCH DELETE.

GETread/fetch. Safe, URL se. Page kholna, search.

POSTcreate/submit. Form, login.

PUTpoora replace/update. Idempotent.

PATCHpartial update.

DELETEhataana.

HEAD: sirf headers. OPTIONS: CORS preflight.

Flask: @app.route('/x', methods=['GET','POST'])
Agar methods na likho to default sirf GET.
HTML form native sirf GET/POST. PUT/DELETE JS/fetch ya hidden _method se.
GET se data fetch ho sakta hai, create nahi karna chahiye. POST se theoretically fetch ho sakta hai lekin cache/semantics galat.
DELETE fetch ke liye nahi. GET POST ka kaam officially nahi karta — side effects GET pe mat rakho.

SimpleGET data mangta hai (read), POST data bhejta hai (create/submit).

GETURL mein dikhta hai, bookmark ho sakta hai, browser back/refresh safe hai, data URL query mein jaata hai. Search, page open, login form dikhana.

POSTbody mein data jaata hai, URL mein password nahi dikhta, refresh pe dubara submit ho sakta hai. Login, register, form save.

Example

# page dikhana

@app.route('/login', methods=['GET', 'POST'])
def login():
    if request.method == 'GET':
        return render_template('login.html')
    # POST: form submit
    email = request.form.get('email')
    ...

GET se theoretically data bhej sakte ho (?q=flask), lekin create/update ke liye nahi use karna — data log/history mein save ho jaata hai, length limit hoti hai.
HTML form default GET hota hai; method='POST' likhna zaroori hai login/register pe.

SimplePUT poori resource replace karta hai, PATCH sirf kuch fields update karta hai.

PUTfull update. Jo fields nahi bheji, woh empty/default ho sakti hain. Idempotent — same request 5 baar bhejo, result same.

PATCHpartial update. Sirf name change karna hai to sirf name bhejo, baaki fields same rehti hain.

ExampleUser {name: Ram, city: Delhi, age: 20}

PUT /user/1 {name: Shyam} → city/age lose ho sakte hain agar poora object nahi bheja.
PATCH /user/1 {name: Shyam} → sirf name Shyam, city Delhi, age 20 same.

MAD1 Flask forms mein aksar POST se update karte hain kyunki HTML form PUT/PATCH native support nahi karta. Theory mein farq yeh hai.

SimpleGET data mangta hai (read), POST data bhejta hai (create/submit).

GETURL mein dikhta hai, bookmark ho sakta hai, browser back/refresh safe hai, data URL query mein jaata hai. Search, page open, login form dikhana.

POSTbody mein data jaata hai, URL mein password nahi dikhta, refresh pe dubara submit ho sakta hai. Login, register, form save.

Example

# page dikhana

@app.route('/login', methods=['GET', 'POST'])
def login():
    if request.method == 'GET':
        return render_template('login.html')
    # POST: form submit
    email = request.form.get('email')
    ...

GET se theoretically data bhej sakte ho (?q=flask), lekin create/update ke liye nahi use karna — data log/history mein save ho jaata hai, length limit hoti hai.
HTML form default GET hota hai; method='POST' likhna zaroori hai login/register pe.

SimpleAPI = Application Programming Interface — do systems predefined rules se baat karti hain. REST API HTTP + JSON use karti hai.

Controller/route HTML bhi return kar sakta hai. REST API generally JSON return karti hai, frontend alag ho (Vue/Postman).

Example

@app.route('/api/users/<int:id>')
def get_user(id):
    u = User.query.get_or_404(id)
    return jsonify(id=u.id, name=u.name)

MAD1 HTML apps mein 'API' kabhi-kabhi routes ko hi keh dete hain. Agar Vue nahi to bolo: server-rendered Flask, JSON APIs optional.
Boolean return: technically jsonify(True) ho sakta hai, lekin meaningful JSON object better. Flask view None return kare to error.
Test: Postman se GET/POST.
Parsing: request.get_json() body se, request.args query se.