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

Questions 26–30

1. 26expert · hard

   A DevOps team uses a Jenkins pipeline to build a Java application. The build script needs to access a database password to run integration tests. The security team mandates that the password must not be stored in the Jenkinsfile or in the source repository. Which approach should the team use to securely provide the password to the build?

   • AAsk developers to enter the password manually when the build runs.
   • BHardcode the password in the Jenkinsfile with a comment saying it is a placeholder.
   • CStore the password as a plain text environment variable in the Jenkins global configuration.
   • DUse Jenkins Credentials Binding plugin to bind a secret text credential to an environment variable in the pipeline.
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   What is the purpose of an artifact repository in a DevSecOps pipeline?

   • ATo store and manage build artifacts in a centralized location for retrieval and deployment
   • BTo run automated security scans on the production environment
   • CTo compile source code into executable binaries
   • DTo store source code and manage version history
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   A company builds a Java application and produces a JAR file. They need to store the JAR files so that they can be retrieved later for a specific release, and they want to ensure that the artifact can be traced back to the exact source code version. What should they do?

   • AUse an artifact repository like Nexus or Artifactory and tag the artifact with the Git commit hash.
   • BStore the JAR files on a shared network drive with the date in the filename.
   • CEmail the JAR file to the team after each build.
   • DOverwrite the same JAR file in a shared folder after every build.
   Reveal Solution Discussion Select an answer first
5. 29application · medium

   A DevOps team uses a CI pipeline to build a .NET application. The build produces a NuGet package that is used by other teams. They need to ensure that the package version is unique and traceable to the source commit that produced it. Which versioning strategy should they implement in the build script?

   • AUse the current date and time as the package version.
   • BUse a fixed version number like 1.0.0 for every build.
   • CUse the build number from the CI server as the package version.
   • DUse a semantic version like 1.0.0-{git-short-sha} where {git-short-sha} is the short commit hash.
   Reveal Solution Discussion Select an answer first
6. 30foundation · easy

   In a build script, what is the purpose of declaring dependencies?

   • ATo specify external libraries or modules required to compile and package the application
   • BTo configure the network firewall for the build server
   • CTo define the order in which developers commit code
   • DTo set the version number of the application
   Reveal Solution Discussion Select an answer first