I think C makes most sense. Dependencies are not "staggered" between releases, since each release can include new dependency version which would require a new installation.
A and B make no sense.
Option B, dependencies are tested after the release is deployed, is not a good way to manage dependencies. If there are any issues with the dependencies, the release will already be deployed and it will be difficult to roll back the deployment.
Option C, designed to prevent any dependencies between release units, is not possible in most cases. There are always going to be dependencies between release units, even if they are not explicitly stated.
Option D, dependencies are staggered between multiple releases, is not a good way to manage dependencies. This can lead to deployments that are not consistent and can make it difficult to track down problems
I asked ChatGPT and it gave this answer:
D. dependencies are staggered between multiple releases
How confident are you in your answer?
I am highly confident in my answer. Release packaging is a technique that allows for dependencies to be effectively managed during deployments by staggering them between multiple releases. This means that different components of a software system can be released at different times, rather than all at once, which allows for more control over the dependencies between those components. This approach allows the development team to test, validate and deploy each release unit separately, therefore, reducing the risk of failure and allowing for a more controlled and efficient deployment process.
If the goal is to ensure strict isolation and minimize any interdependencies between release units, option C would be preferable. This approach promotes cleaner boundaries between units and simplifies the management and troubleshooting of the system.
If the deployment scenario requires a more flexible approach, with the ability to independently manage and test dependencies while allowing for gradual rollouts, option D could be a better choice. This approach acknowledges that dependencies may exist but seeks to control their introduction and impact.
Ultimately, the decision between option C and D should be based on factors such as the complexity of dependencies, the desired level of isolation, the deployment strategy, and the specific trade-offs and priorities of the project.
upvoted 2 times
...
...
...
This section is not available anymore. Please use the main Exam Page.350-901 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Amycert
7 months, 2 weeks agodoble_h
1 year, 5 months agojohntermlen
1 year, 9 months agoThePokemonNuzlockingMaster
1 year, 10 months agoit0
2 years, 3 months ago[Removed]
2 years, 3 months agoi9t6
1 year, 10 months agoi9t6
1 year, 10 months ago