Search viva questions

SimpleLive Flask coding: chhota route likho, save, browser/curl se test. Syntax error terminal mein padho.

Example

@app.route('/ping')
def ping():
    return jsonify(ok=True)

@app.route('/even/<int:n>')
def even(n):
    return 'even' if n % 2 == 0 else 'odd'

SimpleRedis box hai, Celery us box se kaam uthane wala worker hai — same cheez nahi.

Redis: store (cache keys) + queue (broker lists).
Celery: Python library jo tasks define karti hai, .delay() se queue mein daalti hai, worker execute karta hai.

Dono localhost pe ho sakte hain. Alag Redis DB index use karo. Redis band = cache miss + Celery stuck.

Example

Celery: broker_url='redis://localhost:6379/0'
Cache:  CACHE_REDIS_URL='redis://localhost:6379/1'

Project example: export_csv.delay(user_id) Flask se. Worker Redis se task uthata hai, CSV+email. Cache alag keys venues.

Viva tipAgar possible ho to cache db=1, broker db=0 — keys mix nahi hoti.

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.

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.

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.

SimpleExaminer submitted ZIP chahta hai, local extra changes nahi.

Portal se ZIP download → extract → venv → pip install -r requirements.txt → flask run / python app.py.
Checksum maange to hash match karke dikhao. Camera/OPPE setup unke instructions.
Linux/Mac: paths, gunicorn; Windows paths alag ho to relative paths use karo.
Do browsers: admin + user parallel demo impressive lagta hai.

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.

SimpleJWT teen tukde ki signed chitthi: header.payload.signature. Padhi ja sakti hai, badli nahi ja sakti.

Encoded (Base64) + signed, encrypted nahi (JWE alag). Payload mein password mat daalo — koi jwt.io pe dekh lega.

Login pe server secret se HMAC (HS256). Har API Authorization: Bearer <token>.
Expiry exp. Change payload → signature fail → 401.

Session MAD1 server yaad rakhta. JWT MAD2 client rakhta, server stateless-ish.

Example

eyJhbGciOiJIUzI1NiJ9.{"sub":1,"role":"admin"}.signature
# Authorization: Bearer <token>

Project example: POST /login → token LS. fetch interceptor header. @jwt_required APIs.

Viva tipAlgo HS256. Secret env var. jwt.io pe payload dikhao, secret public site pe mat paste.

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.

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.

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)

Simplelazy loading: related objects kab load hon. lazy=True default (access pe query). joined/eager pehle se join.

SimpleMAD1 typical: Browser → Flask routes → validate/auth → SQLAlchemy → SQLite → Jinja response.

Suggested flowRequest → Route → Auth check → DB → render_template / redirect

SimpleEdge cases: duplicate booking, full capacity, wrong role URL, empty search, invalid id.

Example

if Spot.query.get_or_404(spot_id).status != 'available':
    flash('Already taken')
    return redirect(...)

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.

SimpleAuthentication: tu kaun hai? (login). Authorization: tujhe permission hai? (role check).

Example

# auth
if check_password_hash(user.password, pwd):
    session['user_id'] = user.id

# authz
if user.role != 'admin':
    abort(403)

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

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

SimpleLevel = viva difficulty band. Level 1 usually demo + basics; higher pe live coding + deeper theory.

Viva tipJo level assign hai uske hisaab se demo + theory ready rakho.

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.

SimpleGitHub repo open karo: commits, collaborators, README. Examiner check karta hai tumne khud kaam kiya.

Example

Settings → Collaborators
Commits: regular messages, last-day dump nahi.

Viva tipPrivate repo access pehle de do. Main branch submitted ZIP se match honi chahiye.

SimpleMAD1 mein usually session-based auth: login pe session['user_id'], har request pe verify.

Example

session['user_id'] = user.id
uid = session.get('user_id')
user = User.query.get(uid)

Viva tipSECRET_KEY set karo warna session insecure. logout pe session.clear().

SimpleJWT teen tukde ki signed chitthi: header.payload.signature. Padhi ja sakti hai, badli nahi ja sakti.

Encoded (Base64) + signed, encrypted nahi (JWE alag). Payload mein password mat daalo — koi jwt.io pe dekh lega.

Login pe server secret se HMAC (HS256). Har API Authorization: Bearer <token>.
Expiry exp. Change payload → signature fail → 401.

Session MAD1 server yaad rakhta. JWT MAD2 client rakhta, server stateless-ish.

Example

eyJhbGciOiJIUzI1NiJ9.{"sub":1,"role":"admin"}.signature
# Authorization: Bearer <token>

Project example: POST /login → token LS. fetch interceptor header. @jwt_required APIs.

Viva tipAlgo HS256. Secret env var. jwt.io pe payload dikhao, secret public site pe mat paste.

SimpleLifecycle = component ki zindagi ke stages. API call tab jab DOM ready ho — mounted.

created: instance bani, this data, DOM nahi. mounted/onMounted: page pe aa gaya — fetch, Chart.js, setInterval.
updated: data change ke baad. unmounted: cleanup (clearInterval) warna memory leak.

Dashboards onMounted isliye: canvas/API tab valid. created mein $el nahi.

Composition: onMounted(() => {}) setup ke andar.

Example

export default {
  async mounted() {
    const r = await fetch('/api/venues')
    this.venues = await r.json()
  }
}

Project example: Venues.vue mounted fetch list. Clock component unmounted pe interval clear.

Viva tipcreated: data setup, DOM nahi. mounted/onMounted: $el mil gaya — fetch yahi. Dashboards isliye onMounted use karti hain.

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.

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.

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.

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.

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: 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)

SimplePassword plain text mat store. werkzeug generate_password_hash / check_password_hash.

Example

from werkzeug.security import generate_password_hash, check_password_hash
user.password = generate_password_hash(raw)
check_password_hash(user.password, raw)

Simplejsonify Python dict/list ko JSON response + proper Content-Type deta hai.

Example

return jsonify(message='ok', count=3), 200

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.

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.

SimpleCelery = background naukri. HTTP request ko 10 second email bhejne ke liye mat rokna.

Distributed task queue: aap function ko abhi nahi, worker process mein later/retry/schedule pe chalaate ho.

MAD2 typical jobs: daily reminder mail, monthly HTML report, user-triggered CSV export.

Web request 200ms hona chahiye. 10,000 emails request thread mein = timeout. Worker alag CPU pe kaam kare.

Redis broker chahiye. Beat alag process schedule ke liye.

Example

@celery.task
def daily_reminder():
    for u in User.query.filter_by(active=True):
        send_mail(u.email, 'Book something today!')

Project example: User Export click → 202 Accepted. Worker CSV + email. Daily 6pm Beat reminder.

Viva tipWorker + Redis bina Beat ke user-triggered chalega. Scheduled jobs ke liye Beat bhi chahiye.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleLifecycle hooks = component stages (created/mounted/updated/unmounted). Data fetch usually mounted/onMounted.

SimpleVirtual DOM memory tree. Diff, sirf farq real DOM pe. Fayda kam DOM ops. Nuksaan chhote page overhead.

Vue/React. jQuery direct DOM. Lose reactivity Vue2 new property bina set.

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: v-for list patch, poora innerHTML nahi.

SimpleNaya Flask route: URL, method, auth if needed, query, jsonify. Postman pehle.

Examiner number/filter change easy rakhna. CORS. Frontend tabhi jab bole.

Status codes sahi. Password JSON mein nahi.

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.

Example

@app.route('/api/sum', methods=['POST'])
def sum_num():
    d = request.get_json()
    return jsonify(result=d['a'] + d['b'])

Project example: resources.py new Resource. Test Thunder. Optional Vue fetch.

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.

SimpleSearch: form/query param → ilike filter → results template.

Example

q = request.args.get('q', '').strip()
lots = Lot.query.filter(Lot.name.ilike(f'%{q}%')).all()

SimpleLIKE case-sensitive Postgres. ILIKE insensitive. SQLite LIKE often insensitive.

Search use ilike.

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: Venue.name.ilike(f'%{q}%').

Project example: Venue.name.ilike(f'%{q}%').

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

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).

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.

SimpleJOIN related tables ek result mein. Inner = match only; left = left side sab + match.

Example

db.session.query(Booking, User).join(User).filter(User.id == uid).all()

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

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.

SimpleMAD1 mein common: Werkzeug generate_password_hash — default usually pbkdf2:sha256. Apna code dikhao.

Example

from werkzeug.security import generate_password_hash
print(generate_password_hash('secret'))  # pbkdf2:sha256:...

SimpleIndex kitab ki suchi — search tez, write thoda mehnga.

B-tree typically. filter wale columns, FKs. Over-index mat.

joinedload N+1 alag.

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

db.Column(db.String(80), index=True)
db.Index('ix_name_city', User.name, User.city)

Project example: email index, venue.name search index.

SimpleMemoize = function(args) ka answer copy. Caching broader (HTTP, Redis, page).

Fibonacci textbook. Flask @cache.memoize. cached whole view.

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: get_user(id) memoize. venues list cached.

SimplePrimary key row ka unique identity — usually id Integer autoincrement.

Example

id = db.Column(db.Integer, primary_key=True)

SimpleLevel = viva difficulty band. Level 1 usually demo + basics; higher pe live coding + deeper theory.

Viva tipJo level assign hai uske hisaab se demo + theory ready rakho.

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.

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.

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.

SimpleAuthentication: tu kaun hai? (login). Authorization: tujhe permission hai? (role check).

Example

# auth
if check_password_hash(user.password, pwd):
    session['user_id'] = user.id

# authz
if user.role != 'admin':
    abort(403)

SimpleFlask lightweight Python web framework — routes, request/response, templates. MAD1 ka backend yahi hai.

Example

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return 'Hello'

Viva tipFlask micro hai: jo chahiye (DB, login, forms) khud jodte ho.

SimpleAuthentication: tu kaun hai? (login). Authorization: tujhe permission hai? (role check).

Example

# auth
if check_password_hash(user.password, pwd):
    session['user_id'] = user.id

# authz
if user.role != 'admin':
    abort(403)

SimpleJWT teen tukde ki signed chitthi: header.payload.signature. Padhi ja sakti hai, badli nahi ja sakti.

Encoded (Base64) + signed, encrypted nahi (JWE alag). Payload mein password mat daalo — koi jwt.io pe dekh lega.

Login pe server secret se HMAC (HS256). Har API Authorization: Bearer <token>.
Expiry exp. Change payload → signature fail → 401.

Session MAD1 server yaad rakhta. JWT MAD2 client rakhta, server stateless-ish.

Example

eyJhbGciOiJIUzI1NiJ9.{"sub":1,"role":"admin"}.signature
# Authorization: Bearer <token>

Project example: POST /login → token LS. fetch interceptor header. @jwt_required APIs.

Viva tipAlgo HS256. Secret env var. jwt.io pe payload dikhao, secret public site pe mat paste.

SimpleClick → Celery → worker CSV → email/download. Columns verify.

csv module. Auth required. Don't freeze UI — 202 + poll.

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.

Example

@celery.task
def export_venues_csv(user_id):
    rows = Venue.query.all()
    # csv.writer, mail.send
    return 'ok'

Project example: Admin export venues. MailHog attach ya file open.

Viva tipNetwork tab mein job trigger API dikhao, phir MailHog/file open karke columns verify karo.

SimpleCelery = background naukri. HTTP request ko 10 second email bhejne ke liye mat rokna.

Distributed task queue: aap function ko abhi nahi, worker process mein later/retry/schedule pe chalaate ho.

MAD2 typical jobs: daily reminder mail, monthly HTML report, user-triggered CSV export.

Web request 200ms hona chahiye. 10,000 emails request thread mein = timeout. Worker alag CPU pe kaam kare.

Redis broker chahiye. Beat alag process schedule ke liye.

Example

@celery.task
def daily_reminder():
    for u in User.query.filter_by(active=True):
        send_mail(u.email, 'Book something today!')

Project example: User Export click → 202 Accepted. Worker CSV + email. Daily 6pm Beat reminder.

Viva tipWorker + Redis bina Beat ke user-triggered chalega. Scheduled jobs ke liye Beat bhi chahiye.

SimpleMAD1 frontend usually Jinja templates + HTML/CSS/Bootstrap (+ thoda JS). MAD2 pe Vue ho to clearly bolo.

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.

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

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.

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.

SimpleDirectives Vue ke special attributes — HTML ko superpower.

v-if/else/show, v-for, v-bind (:), v-on (@), v-model, v-html (XSS), v-cloak, v-slot.

:src = v-bind:src. @click = v-on:click.

Custom directives bhi (v-focus) — course basics kaafi.

Example

<p v-if="ok">Yes</p>
<li v-for="u in users" :key="u.id">{{ u.name }}</li>
<input v-model="email">
<img :src="url">

Project example: List v-for :key. Form v-model. Admin v-if. Image :src.

Viva tip: src ke liye v-bind:src ka shorthand. @click = v-on:click.

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.