Source-Code Management and Build Tools DSE Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A team builds a .NET application and uses MSBuild. They want to automate the build process so that it compiles the code, runs tests, and packages the application into a NuGet package. They also want to ensure that the package version is automatically incremented with each build. What should they configure?

   • AUse an MSBuild script with a versioning task that reads the current version and increments it, then package the output.
   • BUse a CI server to run the build, but keep the version static.
   • CUse a manual process where a developer updates the version in the project file before each build.
   • DUse a post-build script that copies the output to a shared folder without versioning.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A team uses Git with a `main` branch. They have a policy that all changes must be reviewed via pull requests. A developer creates a feature branch, but after a week, the main branch has advanced significantly. The developer's branch has merge conflicts. The team wants to integrate the feature with minimal disruption and maintain a clean history. What should the developer do?

   • AClose the feature branch and create a new branch from main, manually re-applying the changes.
   • BMerge main into the feature branch, resolve conflicts, and then create a pull request.
   • CRebase the feature branch onto the latest main, resolve conflicts, and then create a pull request.
   • DForce-push the feature branch to main to overwrite the conflicts.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A development team uses a build tool that compiles source code, runs unit tests, and packages the application into a deployable artifact. They want to ensure that the artifact is reproducible and that the build process is consistent across different environments. What should they configure in their build script?

   • AUse a build script that downloads dependencies from a public repository without version pinning.
   • BHard-code the build environment paths and use the latest versions of all dependencies.
   • CDefine the build steps in a script and use a dependency lock file to pin exact versions.
   • DRun the build manually on a developer's machine and share the resulting artifact.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A developer accidentally commits a database password to a Git repository. The password is now in the commit history. The team uses a build server that checks out the repository for every build. What is the most secure way to handle this incident?

   • AChange the password, remove the file from the working tree, and commit the deletion.
   • BUse `git filter-branch` or `git filter-repo` to purge the password from history, then force-push the rewritten history.
   • CAdd the file to `.gitignore` and commit the change.
   • DRotate the database password immediately, then rewrite history to remove the secret and force-push.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A team uses a Git repository hosted on a private server. They want to integrate with a CI/CD tool that needs to access the repository to fetch code. They want to avoid storing credentials in the CI/CD tool's configuration. What is the recommended approach?

   • AUse the admin's personal access token and store it in the CI/CD configuration.
   • BUse a read-only deploy key or a service account with minimal permissions.
   • CShare the repository password with the CI/CD tool.
   • DMake the repository public so the CI/CD tool can access it without credentials.
   Reveal Solution Discussion Select an answer first