Whizlabs bumped up their GitHub package and updated azure-pipelines.yml file. Currently, their web application is using version 1 of the package. 
Here is the part of the azure-pipelines.yml file- 

What does this package update mean for the application?

Answer options:

A.The new package version is fully compatible with the previous version.
B.The application needs to be modified to use this package.
C.There are no changes in the application required to use this package.
D.Because patch version set to "1" no application updates needed.

Correct Answer: B Option B is correct. According to Semantic Versioning, a change of the major version (in Whizlabs case to 2: majorVersion: `2` )indicates that the package is NOT backward compatible with version 1. It will require changes in the application to use a new version of the package.
Option A is incorrect. The statement is incorrect: the notion of "2" for the major version indicates incompatibility with version 1.
Option C is incorrect due to the explanations for Option
B.Option D is incorrect because it is an entirely wrong statement concerning the package major version change.
For more information about package versioning using Semantic Versioning, please visit the below URLs- 

https://semver.org/
https://docs.microsoft.com/en-us/learn/modules/manage-build-dependencies/7-push-a-change