Proctor LEVEL3_VIVA35

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.

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

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)

Simpledb.relationship se object graph: lot.spots, booking.user. backref reverse side auto deta hai.

Example

spots = db.relationship('Spot', backref='lot', cascade='all, delete-orphan')

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

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.

SimpleMVC: Model=data (SQLAlchemy), View=Jinja HTML, Controller=Flask routes/business logic.

Flask loosely MVC follow karta hai — routes controllers, templates views, models.py models.

SimpleORM = Object Relational Mapping. Tables → Python classes. Raw SQL kam likhte ho.

Example

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True)

User.query.get(5)  # SELECT ... WHERE id=5

SimpleValidation = input rules: required, email format, length, unique. Frontend UX, backend security — dono.

Example

if not email or '@' not in email:
    flash('Invalid email')
    return redirect(request.url)
if User.query.filter_by(email=email).first():
    flash('Email taken')

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

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

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

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.