Scribd
Upload
74 views3 pages

Week 4 - Delivering Continuously

No need for increased complexity The need for service discovery The need for distributed transactions The need for independent deployability Correct Microservices are independently deployable which means each service can be updated without affecting other services. This is a key advantage of microservices over monoliths.

Uploaded by

shafe SP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
74 views3 pages

Week 4 - Delivering Continuously

No need for increased complexity The need for service discovery The need for distributed transactions The need for independent deployability Correct Microservices are independently deployable which means each service can be updated without affecting other services. This is a key advantage of microservices over monoliths.

Uploaded by

shafe SP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Week 4- Delivering Continuously

LATEST SUBMISSION GRADE


100%

the one with the dots is the correct answer

1.
Question 1
Which of the following are conventional reasons to use pull requests? Select all that apply.
1 / 1 point
To make sure only team leads commit code
• Encourage discussion for shared understanding

Correct
Yes, it's common for teams to use PR's to trigger informal discussions to drive shared
understanding.
• Trigger the CI/CD system to run tests first

Correct
Yes, it's common to configure PR's to trigger the CI/CD system.
• Trigger code reviews

Correct
Yes, it's common for teams to use PR's to trigger code reviews.
2.
Question 2
Why is it important to get management approval for CI/CD initiatives before starting?
1 / 1 point
To facilitate planning
To get resources
To get buy-in
• It isn't

Correct
If management requires approval for everything you do, then you may need it but really the
important thing is the work of the individual team(s).
3.
Question 3
An individual developer is thinking of starting to write unit tests. What will they need from the rest
of the team or pipeline to make this investment make sense?
1 / 1 point
Strong integration test coverage
A test infrastructure to run their tests
• Not much

An artifact repository
Correct
Most of the leading tools are open source and the developer will probably start seeing rewards right
away.
4.
Question 4
Are automated tests best run before or after a commit to the main branch?
1 / 1 point
It varies a lot
• Before

After
It doesn't matter
Correct
The idea is to make sure the changes don't break stuff before you merge them with everyone else's
work.
5.
Question 5
Your team is feeling like CI/CD is a big undertaking and best left until next year. What might you
do to help?
1 / 1 point
Bring in a speaker
Turn up a Kubernetes instance
Install Jenkins
• Break the project up into smaller pieces

Correct
Everyone gets to CD in increments! And the nice thing is that if you break the work into test-driven
pieces, you can be sure you'll steadily reap rewards all along the way.
6.
Question 6
You are considering moving from a monolithic architecture to a microservices architecture. What
key thing do you need to consider in making this transition?
1 / 1 point
The need for increased manual testing

You might also like