Proctor LEVE1_VIVA14

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.

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.

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.

SimpleHTTP verbs REST ke tools. Methods HTTP ke hain, REST unhe convention se use karta hai.

GET read cacheable. POST create payload. PUT replace. PATCH patch. DELETE remove.

GET exists bina REST ke bhi — browser address bar.

HTTP verbs + status REST ki zabaan. GET read, POST create, PUT replace, PATCH partial, DELETE remove. GET typically no body.

Status: 200 OK, 201 created, 202 accepted (Celery task), 400 bad input, 401 no/bad token, 403 role nahi, 404 missing, 409 conflict (double book), 500 server.

AJAX/fetch page reload nahi. SPA poori isi pe. Postman se bina Vue ke API prove karo — examiner pasand.

Example

GET /api/venues
POST /api/venues
PUT /api/venues/1
DELETE /api/venues/1

Project example: resources.py methods list. Postman 4-5 calls.

Viva tipGET typically no body (cacheable). POST/PUT/PATCH haan payload. PUT idempotent, POST nahi.

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.

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.

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

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

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

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

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

SimpleonMounted = Composition API ka mounted. setup() ke andar call.

Options API: mounted() method. Mix mat. Vue 3 dono chalte.

Lifecycle = component ki zindagi: created (instance, DOM nahi) → mounted/onMounted (DOM ready — fetch, Chart.js yahi) → updated → unmounted (clearInterval).

Dashboard API created mein isliye nahi ki $el/canvas missing ho sakta. Composition API: onMounted(() => {}) setup ke andar. Options: mounted() method. Mix mat.

Examiner 'konsa hook use kiya' — related .vue kholo, line padh ke bolo.

Example

import { onMounted, ref } from 'vue'
const items = ref([])
onMounted(async () => {
  items.value = await (await fetch('/api/items')).json()
})

Project example: script setup: onMounted(loadStats).

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.

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.

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))