Issacc.com

Platform Lifecycle and Deployment Architect Exam Prep - Operating

7 min read

Operating consists of 10% of total score in Salesforce Platform Lifecycle and Deployment Architect Exam. The topic covers risks, strategies, direct changes and managing common release artifacts.

NOTE

Most of the content in this work was generated with the assistance of AI and carefully reviewed, edited, and curated by the author. If you have found any issues with the content on this page, please do not hesitate to contact me at support@issacc.com.

⚙️ OPERATING

Making Direct Changes in Production + Managing Common Release Artifacts

⚡ Making Direct Changes in Production

🧩 Topic💡 Key Points
💻 SandboxesSafe risk-free environments to test high-impact changes (code, workflows, global features)
🏭 ProductionOnly for low-impact changes (fields, picklists, reports); needs caution & validation
⚠️ ImplicationsRisk of errors, conflicts with concurrent changes, compliance issues, data loss
🛡️ PrecautionsDouble-check → Communicate → Phased release → Training users
🧠 CodingCannot be done directly in production, must be done in sandboxes

What are best practices for direct prod changes?

  • Do it only for minor, low-risk updates

  • Review & approve by stakeholders

  • Use a hotfix process if urgent

  • Document everything

  • Update sandboxes & VCS after making change

⚠️ Risks, Strategies, and Tools

⚠️ Risks🧠 Strategies🛠️ Tools
Bypass testing → ErrorsEmergency hotfix workflowDeployment tools (Salesforce CLI, Change Sets)
Conflict with other changesThorough review & authorizationSandbox refresh cycles
Compliance & data securityCommunication & trainingVersion control (Git)

💼 Business Scenarios (Direct Changes)

ScenarioSituationSolution
⚡Urgent data field bugReplace a defective field directly in prodDo so with close review & oversight to minimize brand damage
🐞Apex bug in prodBug from old Apex class, strict compliance rulesCreate hotfix branch, get stakeholder approval, deploy safely
⚙️Minor change policyRegulated prod, no CI/CDRequire documentation, security review, stakeholder approval, then update sandboxes
⚡Unit tests failingConsultant added field only in prodDo daily metadata backups to VCS, refresh sandboxes, use Change Sets to sync

🏗️ Multi-Org: Managing Common Release Artifacts

ApproachKey Idea
📁 Source-Driven DevUse Git as source of truth, branch & merge across orgs (CI/CD)
📦 PackagesUse Managed/Unlocked for modular delivery, or Unmanaged for backup
🧩 Metadata APIUse retrieve() / deploy() with project manifest (package.xml)
📨 Change SetsGood for small connected org deployments (sandbox → prod)
🧠 Other Tools.zip bundles, Salesforce CLI, RTM, and 3rd-party backup/rollback tools

When to use each method?

  • Source-driven → many orgs, complex collaboration

  • Metadata API → direct control over specific components

  • Packages → versioning, modular reuse, backups

  • Change Sets → simple admin-friendly small moves

💼 Business Scenarios (Multi-Org)

ScenarioSolution
📨 Consultant can’t access prodUse Metadata API retrieve() → send .zip + package.xml → team does validate → quick deploy with CLI
📜 Unknown old Apex classUse Requirements Traceability Matrix (RTM) to find its purpose
🛡️ Regulated rollback & backupsEvaluate 3rd-party or AppExchange tools (since unmanaged pkg backup is limited)

🧠 Quick Decision Guide

NeedBest Approach
Urgent fixEmergency hotfix + stakeholder review
Low-risk config changeDirect in prod + documentation + sandbox sync
New feature devSandbox → ALM pipeline (Git, CLI, CI/CD)
Multi-org artifact syncSource-driven + Metadata API
Metadata rollback & backupUnmanaged pkg + 3rd-party tool

📈 Flow Charts

1) Decide where to make the change

flowchart TD
    A[New request] --> B[Assess impact and risk]
    B --> C[High impact or any code]
    B --> D[Low impact config]
    C --> E[Use sandbox]
    D --> F[Consider direct change in production]

2) Safe direct change in production checklist

flowchart TD
    A[Plan change] --> B[Review dependencies]
    B --> C[Get stakeholder approval]
    C --> D[Communicate to users]
    D --> E[Create quick backup or export]
    E --> F[Implement change in production]
    F --> G[Validate with super users]
    G --> H[Monitor and roll back if needed]
    H --> I[Document change]
    I --> J[Sync to sandboxes and version control]

3) Emergency hotfix path

flowchart TD
    A[Detect critical issue] --> B[Open hotfix ticket]
    B --> C[Create hotfix branch]
    C --> D[Develop fix in developer sandbox]
    D --> E[Test in partial or full sandbox]
    E --> F[Approval and change window]
    F --> G[Deploy to production]
    G --> H[Monitor and verify]
    H --> I[Propagate to other environments]
    I --> J[Close hotfix and update documentation]

4) Integrate a production change into alm

flowchart TD
    A[Change made in production] --> B[Capture metadata]
    B --> C[Commit to version control]
    C --> D[Replicate in sandbox]
    D --> E[Run tests and validation]
    E --> F[Update pipelines and scripts]
    F --> G[Train users if needed]
    G --> H[Track in release notes]

5) Multi org artifact management choices

flowchart TD
    A[Need to share artifacts across orgs] --> B[Source driven with git]
    A --> C[Metadata api retrieve and deploy]
    A --> D[Package based deployment]
    A --> E[Change sets]
    B --> F[Automate with ci cd]
    C --> G[Use package xml and zip]
    D --> H[Use unlocked or managed or unmanaged]
    E --> I[Use for small connected org moves]

6) Compliance and risk gate before production change

flowchart TD
    A[Proposed production change] --> B[Classify risk and data sensitivity]
    B --> C[Security and privacy review]
    C --> D[Select change window]
    D --> E[Notify support and business]
    E --> F[Prepare rollback plan]
    F --> G[Proceed or defer to sandbox]

7) Low risk config change in production

flowchart TD
    A[Request new field or picklist value] --> B[Check page layouts and reports]
    B --> C[Confirm no automation impact]
    C --> D[Apply change in production]
    D --> E[Smoke test with sample users]
    E --> F[Announce and update help text]
    F --> G[Sync change to sandboxes]

8) Daily metadata drift control

flowchart TD
    A[Schedule metadata export] --> B[Commit to version control]
    B --> C[Diff against main branch]
    C --> D[Publish changes to team]
    D --> E[Refresh affected sandboxes]
    E --> F[Align tests and pipelines]

📚 Flashcards

Recent Notes

Graph View