Module: Heroku Flow -Trailhead salesforce answers

#1.Learn About Continuous Integration, Deployment, and Delivery

Q.1)What characterizes continuous integration as a development process?

I)Keeping bugs hidden until the product is ready to be released.
II)Allowing only one developer at a time to make changes to the source code.
III)Including and integrating every code change on every commit.
IV)Making changes to the source code directly to save development time and resources.


III)Including and integrating every code change on every commit.

Q.2)What’s the difference between continuous delivery and continuous deployment?

I)Continuous delivery happens in production while continuous deployment is part of staging.
II)Continuous delivery is managed by developers while continuous deployment is managed by product owners.
III)Continuous delivery is the next step of continuous deployment, during which changes are manually added to a release.
IV)In continuous deployment, every change that passes the automated tests is deployed to production automatically while in continuous delivery this is a manual step.


IV)In continuous deployment, every change that passes the automated tests is deployed to production automatically while in continuous delivery this is a manual step.

Q.3)What are some of the benefits of continuous delivery?

I)Shorter release cycles.
II)Discovering issues close to the release time.
III)Finding bugs earlier in the development process.
IV)A and C


IV)A and C

#2.Learn About Heroku Flow and Its Features

Q.1)Which process is part of a common continuous delivery workflow on Heroku?

I)A review app spins up when creating a pull request in GitHub.
II)Heroku CI runs tests upon merging code changes back to the master branch.
III)A developer transfers code from Bitbucket to GitHub.
IV)A and B
V)A and C


IV)A and B

Q.2)What’s one thing you can do with Release Phase?

I)Run integration tests when code is merged to master.
II)Leave comments on a pull request.
III)Upload assets to CDN or invalidate a cache.
IV)Promote apps from staging to production.


III)Upload assets to CDN or invalidate a cache.

#.3)Create a Heroku Pipeline and Run Review Apps

Q.1)Which of the following is a valid Heroku Pipeline name?

I)Demo-Pipeline
II)testdemo
III)test/demo-pipeline
IV)1st-pipeline-test


II)testdemo

Q.2)Review apps are created when?

I)A new branch is created for a new feature or code changes in GitHub.
II)The “Propose file change” option is selected in GitHub.
III)The index.html file is edited.
IV)You create a pull request in GitHub.


IV)You create a pull request in GitHub.

Q.3)What is the best way to preview code changes in a browser window?

I)Select “Promote to Production” from under the staging app in your pipeline.
II)Click Open under Update index.html file in GitHub.
III)Select “Open app in browser” next to the review app.
IV)A and B


III)Select “Open app in browser” next to the review app.

#4.Run Tasks with Release Phase

Q.1)How do you set up Release Phase?

I)Open Procfile and add a release process type and command.
ii)Move Procfile to the public folder at the root of the GitHub repository.
iii)Select “Enable automatic deploys” next to the staging app.
iv)Add release: echo “You created a new release on Heroku.” to the index.html file under the public folder.


I)Open Procfile and add a release process type and command.

Q.2)Which feature provides one of the fastest solutions to bad deploys on Heroku?

i)Heroku CI
ii)Heroku Rollback
iii)Heroku ChatOps
iv)A and B


ii)Heroku Rollback

Spread the love

Leave a Reply

%d bloggers like this: