Free Salesforce Platform Development Lifecycle and Deployment Architect Practice Test Questions

Explanation

The correct answer is A. Scrum defines five core values: Commitment, Courage, Focus, Openness, and Respect. In this scenario, the development team is not updating the status of their work in progress, meaning the team is hiding the real state of the work from the rest of the Scrum team and stakeholders. This lack of transparency requires Courage — the courage to be honest about progress, to admit when work is stalled or behind, and to speak up when help is needed. When team members avoid updating status because they are worried about appearances or difficult conversations, it is precisely the Scrum value of Courage that is compromised. Transparency is essential to Scrum, and courage is what enables that transparency.

Why the Other Options Are Incorrect

B. Openness, because the team is not open to a new methodology.
– The issue is not that the team is unwilling to adopt Scrum — the issue is that they are not updating their work status. Openness is about being transparent with each other and stakeholders about the work, but the specific behavior described (avoiding status updates out of discomfort or concern) is more directly tied to Courage — speaking up honestly about progress and problems. This option misframes the problem as resistance to the methodology.

C. Focus, because the teams are not focusing in the agile process expected activities.
– Focus refers to concentrating on the Sprint Goal and the Sprint Backlog and limiting work in progress. The scenario is not about a lack of focus on the sprint work — the team is doing the work but not reporting its status. That is a transparency issue, which maps to Courage, not Focus.

D. Commitment, because the team is not committed to follow the Agile methodology.
– Commitment is about the team dedicating itself to achieving the Sprint Goal and supporting each other. The problem here is not a lack of commitment to the work or the methodology — it is a lack of honest reporting about in-progress work. This maps to Courage (transparency and speaking up), not Commitment.

Reference

The Scrum Guide (Scrum Values: Commitment, Courage, Focus, Openness, Respect); Salesforce Architect documentation on Agile Delivery, Scrum Adoption, and Team Transparency Practices.

Explanation

The correct answer is D. The CTO's claim is that the team cannot deliver the work it commits to. The best evidence for this is a burndown chart that shows the team consistently missing its sprint forecast — meaning the work committed at the start of each sprint is not completed by the end of the sprint, sprint after sprint. This is a measurable, objective pattern that directly supports the claim about delivery capability. A burndown chart tracks remaining work versus time, so a repeated pattern of unfinished work at sprint end is exactly the kind of evidence that supports the CTO's statement.

Why the Other Options Are Incorrect

A. The definition of done (DoD).
– The Definition of Done is a shared quality standard that describes what it means for work to be considered complete. It is not evidence about delivery capacity or missed commitments. It defines criteria, not performance. So it does not support or refute the CTO's claim about the team's ability to deliver committed work.

B. A burndown chart showing team finishes early sprint after sprint.
– If the team were finishing early every sprint, that would suggest the team is under-committing (a planning issue) or has capacity to spare — the opposite of the CTO's claim. Finishing early does not demonstrate that the team is unable to meet its commitments; it demonstrates the team is completing its work ahead of schedule.

C. A Kanban board showing there's always the maximum allowed amount of work in progress (WIP).
– A Kanban board showing maximum WIP indicates the team is always at its WIP limit, which is actually a healthy Kanban signal and could indicate the team is working at capacity, not failing to deliver. It reflects workflow behavior, not missed sprint commitments. It does not directly provide evidence about the team's ability to meet its sprint forecasts, so it does not support the CTO's claim as directly as a burndown chart does.

Reference

Salesforce Architect documentation on Agile Delivery, Scrum Metrics, and Team Performance Evidence; The Scrum Guide (Sprint commitment, Sprint Backlog, and Sprint Review outcomes); industry agile metrics guidance on burndown charts and velocity as indicators of delivery reliability.

Explanation

The correct answer is D. In Salesforce, the Unlimited Edition permits one full sandbox by default (additional full sandboxes must be purchased separately). In this scenario, UC has two full sandboxes — one for UAT (actively used) and one for performance testing (no longer used). Having two full sandboxes on an entitlement of one exceeds the sandbox limit, which is a common cause of refresh failures across the org. Since the performance-testing full sandbox is no longer actively used, the correct and most probable fix is to delete it, which brings the org back within its sandbox entitlement and allows the remaining sandboxes to be refreshed. This is a direct, actionable solution the architect can recommend to the system administrator.

Why the Other Options Are Incorrect

A. Contact the Salesforce Account Team to do a sandbox License Count.
– This is not a productive first step. The architect can already determine from the scenario that the org has more full sandboxes than the entitlement allows. Contacting the Account Team to "do a sandbox license count" would delay the fix and is unnecessary — the issue is evident from the configuration described.

B. It appears the org is using more sandboxes than the license permits. The Partial Copy sandbox shouldn't be used.
– The Partial Copy sandbox is a permitted sandbox type and is being used for training — a legitimate purpose. Pointing at the Partial Copy sandbox is a misdiagnosis. The actual overage is caused by the extra full sandbox (the unused performance-testing one), not the Partial Copy sandbox. Recommending removal of the Partial Copy sandbox would be incorrect and would unnecessarily disrupt training.

C. Create a Salesforce support case, someone should know what is wrong.
– Raising a support case without first addressing the obvious root cause (too many full sandboxes) is inefficient and unhelpful. It escalates the issue without taking the straightforward corrective action that is clearly available (deleting the unused full sandbox). Support cases are appropriate when the root cause is unclear or the fix is not within the customer's control, but here the fix is straightforward.

Reference

Salesforce Sandbox documentation (Sandbox types and entitlements per Edition, including Unlimited Edition's default of one full sandbox); Salesforce Help on Sandbox Refresh failures and Sandbox Limits; Salesforce Architect documentation on Environment Strategy and Sandbox Planning.

Explanation

The correct answer is B. The root cause of unused features is that the solutions being built are not aligned with what users actually need. User-centered design (UCD) addresses this directly by involving users throughout the design and delivery process — conducting user research, gathering feedback, prototyping, and validating solutions before full build. This ensures that features solve real problems, fit real workflows, and are more likely to be adopted. It is a proactive, architectural and delivery-process solution that fixes the underlying issue rather than treating the symptoms. Steering committees typically support UCD because it increases return on investment, reduces wasted effort, and improves user satisfaction.

Why the Other Options Are Incorrect

A. Using Lightning Web Components for every user interface.
– The technology choice (LWC) has nothing to do with adoption. A poorly designed feature will remain unused regardless of whether it is built with LWC, Aura, or Visualforce. LWC is a development framework, not a solution to low user adoption. Changing UI technology without understanding user needs would waste effort and miss the actual problem.

C. Stop development until current features start being used.
– This is a counterproductive and unrealistic recommendation. Halting development would stall business value, frustrate stakeholders, and would not explain why the features are unused or how to fix them. It punishes the whole organization instead of correcting the root cause (misalignment with user needs).

D. Sending weekly communication emails reporting on least engaged users.
– This targets users rather than the design problem. Reporting on low-engagement users can feel punitive, creates noise, and does not address why the features aren't being used. Adoption improves when features meet user needs, not when users are publicly flagged for not using tools that don't serve them.

Reference

Salesforce Architect documentation on User-Centered Design and Adoption Strategy; Salesforce Well-Architected Framework (User Experience, Design, and Operational Excellence); Salesforce recommended practices for improving adoption through user research, design thinking, and iterative delivery.