exam questions

Exam Certified Development Lifecycle and Deployment Architect All Questions

View all questions & answers for the Certified Development Lifecycle and Deployment Architect exam

Exam Certified Development Lifecycle and Deployment Architect topic 1 question 67 discussion

Cloud Kicks is considering using an automated testing tool to help manage deployments between environments.

When should the architect recommend the use of an automated testing tool?

  • A. Automated tests should be run only when merging into Full or Partial Copy sandboxes.
  • B. Automated tests should be run daily in all Developer Orgs, and when branches are merged.
  • C. Automated tests should be run daily in all Developer Orgs.
  • D. Automated tests should be run when branches are merged.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
rufusroffie
1 week ago
Selected Answer: B
Daily Testing in Developer Orgs: Running automated tests daily in Developer Orgs ensures that issues are identified as soon as they are introduced. This helps maintain code quality throughout the development lifecycle. Testing on Branch Merges: Running tests when branches are merged ensures that any new changes integrate seamlessly with existing code. This step is critical for catching integration issues before code progresses to higher environments like UAT or Production. Continuous Feedback: A daily testing schedule and merge-triggered testing provide continuous feedback to developers, enabling them to address issues quickly. DevOps Best Practices: Automated testing at regular intervals and key milestones (e.g., branch merges) aligns with best practices for CI/CD pipelines.
upvoted 1 times
...
SS1121
1 month, 4 weeks ago
Selected Answer: B
Daily Testing in Developer Orgs: Running automated tests daily helps catch issues early in the development process, ensuring that any new code changes do not introduce bugs or regressions. This practice supports continuous integration and promotes a stable development environment. Testing on Branch Merges: Running tests when branches are merged is crucial for validating that the integrated code works as expected and meets quality standards before it is deployed to higher environments. This step minimizes the risk of introducing errors into production.
upvoted 3 times
...
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.

SaveCancel
Loading ...