Interview Questions

Agile is an iterative development methodology. Work is broken into Sprints (typically 2 weeks). Process: Sprint Planning (select items from backlog, estimate using story points) → Daily Standups → Development → Sprint Review/Demo → Sprint Retrospective. Tools: Jira, Azure DevOps. Ceremonies: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, Backlog Grooming.

Lookup: Loosely coupled — child can exist without parent. Parent deletion doesn't cascade. OWD is independent. No rollup summary fields. Lookup field is not required. Master-Detail: Tightly coupled — child cannot exist without parent. Parent deletion cascades to children. Child inherits parent's OWD. Supports Rollup Summary fields on master. MD field is required and locked after data exists.

Lookup → MD: Possible IF all existing records have a value in the lookup field (no nulls) and the relationship doesn't already have data that violates MD rules. The 'Change Field Type' button appears when conditions are met. MD → Lookup: Possible, but you lose rollup summary fields and cascade delete behavior. OWD becomes independent.

A junction object implements a many-to-many relationship using two Master-Detail relationships. The primary master (first MD relationship created) determines OWD inheritance. Standard examples: CampaignMember (Campaign + Lead/Contact), OpportunityContactRole. For custom objects, the junction record is deleted when either parent is deleted.

Record Types allow different picklist values, page layouts, and business processes for different records of the same object. Assigned to profiles — each profile can have a default record type per object. Use cases: Different sales processes, different case types (IT vs HR), different opportunity stages per division.

Custom Permissions are feature-level permissions (not object/field level) that you define. Used to control access to features: buttons, functionality, UI elements. Assigned via Permission Sets. Check in Apex: FeatureManagement.checkPermission('My_Permission'). Check in LWC: import hasPermission from '@salesforce/customPermission/My_Permission'.

Workflow Rules: Legacy — simple field updates, email alerts, outbound messages, tasks. Single object only, no complex logic. Salesforce has announced no new features for workflow rules. Flow: Modern replacement — supports complex logic, multiple objects, user input (Screen Flow), scheduled paths, subflows, Apex calls. Salesforce is retiring Process Builder — migrate to Flows.

Field Sets are groupings of fields on an object that can be referenced dynamically in Apex or Visualforce/LWC. They allow admins to add/remove/reorder fields without code changes. In Apex: Schema.FieldSet fs = Schema.SObjectType.Account.fieldSets.My_Field_Set; List<Schema.FieldSetMember> members = fs.getFields();

Field definition: Check 'Required' checkbox on the field Page Layout: Mark field as 'Required' on a specific page layout Validation Rule: Add a formula that returns true when field is empty Apex Trigger: Use addError() to prevent save when field is empty Flow: Before Save record-triggered flow — check and throw fault NOTE: Making a field required via trigger — yes it's possible using addError() in a before insert/update trigger.

Approval Processes automate multi-step record approvals. Components: Entry Criteria → Approval Steps (approver, criteria) → Approval/Rejection Actions. Features: Delegated approvers, queues as approvers, escalation, email templates. Can be triggered from a button, Apex (Process.ProcessWorkitemRequest), or Flow.

Email-to-Case automatically creates Case records from incoming customer emails. Setup: Enable Email-to-Case → Create routing address → Add email to your support mailbox. On-demand Email-to-Case uses Salesforce email relay. Each email thread links to the case. Can set default values (Status, Priority, Queue assignment).