How well do you know the Salesforce DevOps process?
30 Questions
1 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to Lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the tool used to migrate code from the developer sandbox to QA?

  • Gearset (correct)
  • Jenkins
  • GitLab
  • Bitbucket

What is the first step to connect a development sandbox to Gearset?

  • Enter the username for the sandbox and select "Sandbox organization" as the sandbox type (correct)
  • Enter the password for the sandbox and select "Production organization" as the sandbox type
  • Enter the username for the sandbox and select "Production organization" as the sandbox type
  • Enter the password for the sandbox and select "Sandbox organization" as the sandbox type

What is the purpose of Gearset?

  • To compare and deploy metadata changes (correct)
  • To review code for merge conflicts
  • To create pull requests
  • To validate deployment to production

Who reviews the details before promoting work to UAT?

<p>DevOps team (C)</p> Signup and view all the answers

How can you commit development work in Gearset?

<p>Select the development sandbox as the source metadata location and a feature branch as the target metadata location. (B)</p> Signup and view all the answers

What is the role of the testing team in the DevOps process?

<p>They interact with the developer until the work passes QA (C)</p> Signup and view all the answers

What is the format for naming a feature branch in Gearset?

<p>A specific format (C)</p> Signup and view all the answers

What must the developer ensure before deploying to QA?

<p>The manifest file is updated (A)</p> Signup and view all the answers

What must be updated with necessary details before deployment?

<p>Manifest file (B)</p> Signup and view all the answers

How can you adjust the metadata comparison filter for faster comparison of results in Gearset?

<p>By decreasing the number of components to be compared (C)</p> Signup and view all the answers

What should the developer do to optimize metadata filters for faster comparison?

<p>Adjust the metadata comparison filter (A)</p> Signup and view all the answers

What is the first step a developer must take to promote work to QA?

<p>Authorize sandbox to be accessed from Gearset (C)</p> Signup and view all the answers

What should the developer do to promote their work to QA using Gearset?

<p>Authorize the sandbox to be accessed from Gearset and create a feature branch (A)</p> Signup and view all the answers

How can components be selected and filtered in the comparison results?

<p>By selecting a filter and choosing a metadata type or API name (D)</p> Signup and view all the answers

What should be reviewed before committing changes in Gearset?

<p>The pre-deployment summary (B)</p> Signup and view all the answers

What is shown in the Problem Analysis and Environment Variables screen?

<p>Potential issues in deployment (A)</p> Signup and view all the answers

What should the developer do before merging the feature branch into the QA branch?

<p>Resolve merge conflicts (B)</p> Signup and view all the answers

What is the target branch for a pull request in Gearset?

<p>QA (D)</p> Signup and view all the answers

What should the developer do to resolve merge conflicts?

<p>Click &quot;View and resolve conflicts&quot; button (A)</p> Signup and view all the answers

What should be done to resolve merge conflicts in Gearset?

<p>Select a mix of both (C)</p> Signup and view all the answers

How can merge conflicts be resolved?

<p>All of the above (D)</p> Signup and view all the answers

What triggers validation and deployment to the QA sandbox?

<p>Creating a pull request (B)</p> Signup and view all the answers

What are the three options available to resolve merge conflicts?

<p>a) Source as truth, b) Target as truth, c) Mix and match (A)</p> Signup and view all the answers

What happens after merge conflict resolution in Gearset?

<p>Validation and deployment to the QA sandbox occur (B)</p> Signup and view all the answers

What happens after successful validation in the deployment process?

<p>Changes are promoted to the QA sandbox (B)</p> Signup and view all the answers

What happens after the Pull Request is merged with the QA branch?

<p>Validation is triggered (A)</p> Signup and view all the answers

What happens when resubmitting a work item for QA testing in Gearset?

<p>The same feature branch is used (C)</p> Signup and view all the answers

What should be clicked to deploy changes to the QA sandbox?

<p>&quot;Promote Changes&quot; button (A)</p> Signup and view all the answers

How can reviewers be notified of a pending pull request in Gearset?

<p>By sending an email reminder (B)</p> Signup and view all the answers

What must be added for commits to the feature branch?

<p>Comments (C)</p> Signup and view all the answers

Study Notes

  • The document describes the Salesforce DevOps process for promoting work to QA and UAT sandboxes.
  • Developers complete sprint development work in their sandbox and migrate it to QA using Gearset.
  • The testing team interacts with the developer until the WI passes QA.
  • The developer ensures the manifest file is updated before deployment to QA.
  • DevOps team reviews the manifest file and feature branch before promoting to UAT.
  • The developer must follow specific steps to promote their work to QA using Gearset.
  • The steps include authorizing the sandbox to be accessed from Gearset and creating a feature branch.
  • The metadata comparison filter should be adjusted for faster comparison of results.
  • Merge conflicts may occur and must be resolved.
  • WI in the Gearset pipeline at UAT are ready to be promoted to production.
  • The text provides steps for optimizing metadata filters for faster comparison.
  • The developer can commit changes to the feature branch after selecting components from the comparison results.
  • The pull request must be created and reviewers added before merging the feature branch into the QA branch.
  • Resubmitting the WI should follow the same process as the first time submission.
  • Merge conflicts may occur when merging the feature branch into the QA branch.
  • Merge conflicts can be identified in the Pipeline or when the Pull Request is opened in the version control.
  • Merge conflicts must be resolved before proceeding with the merge.
  • The text provides instructions for adding reviewers to the pull request.
  • The pull request description must be added before creating the pull request.
  • The text includes screenshots of the graphical user interface for reference.
  • To resolve merge conflicts, click "View and resolve conflicts" button.
  • This opens the Source (sandbox version) and Target (feature branch).
  • Three options available: a) source as truth, b) target as truth, c) mix and match.
  • Click "Accept these changes" button to select resolution.
  • Click "Commit merge with selected resolution" button to proceed.
  • Pull Request will be merged with QA branch and trigger validation.
  • Validation may take a few minutes to complete.
  • Click "Promote Changes" button to deploy changes to QA sandbox.
  • This completes merge conflict resolution and deployment to QA sandbox.
  • Overall process involves resolving conflicts, merging to QA branch, and deploying to QA sandbox.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Quiz Team

Description

Think you know the ins and outs of the Salesforce DevOps process for promoting work to QA and UAT sandboxes? Test your knowledge with our quiz! From authorizing sandboxes to resolving merge conflicts, this quiz covers the steps and best practices for successful deployment. Keywords: Salesforce, DevOps, QA, UAT, sandboxes, Gearset, merge conflicts, metadata comparison.

More Like This

Use Quizgecko on...
Browser
Open
Browser
Browser