I85PREP
⌘ K
PL-600 study materials
PL-600 study resources

PL-600 practice questions

One question at a time. Build your PL-600 understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Perform solution envisioning and requirement analysis

During a discovery workshop, a customer lists several pain points but states no measurable outcomes. What should the architect do first?

  1. Turn each pain point into a measurable outcome Correct answer.
  2. Log the pain points as functional requirements
  3. Assign the pain points to the delivery team
  4. Document the pain points as-is and continue

Explanation

Solution envisioning translates stated problems into measurable outcomes so that success criteria, priorities, and scope can be agreed. Without a measurable outcome the team cannot demonstrate value after go-live.

Question 2Perform solution envisioning and requirement analysis

A project sponsor asks to skip discovery and start building immediately. What is the most appropriate response from the architect?

  1. Reduce the scope of the project so that no discovery is needed
  2. Explain the risks and propose a short envisioning phase Correct answer.
  3. Accept and begin building; requirements can be refined during sprints
  4. Escalate the request to the Microsoft account team

Explanation

Starting build with unvalidated scope, success criteria, and risks transfers rework risk into the delivery phase. The architect should articulate that risk and offer a time-boxed envisioning effort that fits the sponsor's timeline.

Question 3Perform solution envisioning and requirement analysis

A requirement states that the app must respond to user input within two seconds for 95 percent of requests. Which category does this requirement belong to?

  1. Regulatory
  2. Functional
  3. Non-functional Correct answer.
  4. Transitional

Explanation

Non-functional requirements describe quality attributes such as performance, availability, and usability rather than a specific behavior the system performs. A response-time target is a measurable quality attribute.

Question 4Perform solution envisioning and requirement analysis

In MoSCoW prioritization, what does the Should-have category represent?

  1. Should-have requirements that are not vital Correct answer.
  2. Stories delivered in a later phase
  3. Scope items that are optional but desirable
  4. Standards that must be met for compliance

Explanation

MoSCoW classifies requirements as Must have, Should have, Could have, and Won't have. Should-have items are important and painful to omit, but the solution can launch without them if schedule pressure demands a trade-off.

Question 5Perform solution envisioning and requirement analysis

Which artifact captures the agreed future state and the value the solution is expected to deliver?

  1. Risk register
  2. Work breakdown structure
  3. Vision statement Correct answer.
  4. Data dictionary

Explanation

The vision statement describes the desired future state, the users it serves, and the value the solution delivers, and it anchors later scope decisions. It is agreed with the sponsor before detailed design begins.

Question 6Perform solution envisioning and requirement analysis

Which activity belongs to requirement analysis rather than to solution build?

  1. Configuring model-driven forms for a new entity
  2. Writing plug-in code for order validation
  3. Creating a deployment pipeline
  4. Decomposing business processes into stories Correct answer.

Explanation

Requirement analysis produces an agreed understanding of what the business needs, expressed as processes, user stories, and acceptance criteria. Configuration, pipeline creation, and code are build activities that follow from that understanding.

Question 7Perform solution envisioning and requirement analysis

A customer's RFP lists several mandatory requirements. What should the architect confirm before committing to a solution approach?

  1. Whether the RFP was written by the IT department
  2. Whether each mandatory requirement is achievable Correct answer.
  3. Whether the competitors have responded to the RFP
  4. Whether the customer has purchased premium connectors

Explanation

Responding to an RFP requires separating requirements that standard capability satisfies from those needing extension, effort, or a written caveat. Misjudging feasibility creates contractual and delivery risk.

Question 8Perform solution envisioning and requirement analysis

Why are as-is process maps produced during envisioning?

  1. To replace the need for stakeholder interviews
  2. To identify which process steps add no value Correct answer.
  3. To serve as the design of the new solution
  4. To document the licensing costs of every current system

Explanation

Analyzing the current state exposes where processes lose time, quality, or control, so the future-state design can target those steps. The maps are an input to design, not the design itself.

Question 9Perform solution envisioning and requirement analysis

A fit-gap analysis shows that a requested approval routing cannot be met by standard configuration. How should this finding be classified?

  1. A gap needing a custom or alternative approach Correct answer.
  2. A non-functional requirement
  3. A licensing constraint
  4. A confirmed fit that calls for no design change

Explanation

Fit-gap analysis classifies each requirement as a fit, a partial fit, or a gap. A gap means standard configuration cannot satisfy the need, so an extension, process change, or scope decision is required.

Question 10Perform solution envisioning and requirement analysis

Why does the architect maintain a requirement traceability matrix?

  1. To record the hours each developer spends on a requirement
  2. To replace the risk register once build starts
  3. To estimate the number of environments needed
  4. To link each requirement to its design and test evidence Correct answer.

Explanation

Traceability links a requirement to its design, build, and test evidence so coverage can be demonstrated and the impact of change assessed. It complements other project artifacts rather than replacing them.

Question 11Perform solution envisioning and requirement analysis

A user story states only that a sales representative wants to view their accounts. What should the architect add to make the story testable?

  1. A named developer to own the work
  2. Acceptance criteria defining expected behavior Correct answer.
  3. A story point estimate agreed with the delivery team
  4. A link to the vendor's documentation

Explanation

A story becomes testable when its expected behavior is expressed as acceptance criteria covering normal and edge cases. Estimates and ownership are planning data and do not define correct behavior.

Question 12Perform solution envisioning and requirement analysis

During analysis, the team finds that a key business unit has no representative available for workshops. How should the architect handle this?

  1. Ignore it, because the business unit is not in scope
  2. Wait until the unit raises issues during user acceptance testing
  3. Add the risk to the issue log after go-live
  4. Log it in the risk register with an owner and mitigation plan Correct answer.

Explanation

Missing stakeholder engagement is a project risk that should be recorded with an owner, impact, and mitigation so it is actively managed. Deferring it to testing or go-live allows the impact to compound.

Question 13Perform solution envisioning and requirement analysis

A customer needs to test a new release while production users continue working. What should the architect recommend?

  1. A single environment with security roles to separate users
  2. Separate development, test, and production environments Correct answer.
  3. A trial environment that expires after 30 days
  4. A personal sandbox for each end user

Explanation

Isolating development and test from production lets releases be validated without disrupting live users, which is a core ALM requirement. Security roles inside one environment do not isolate solution deployments or schema changes.

Question 14Perform solution envisioning and requirement analysis

Which statement is a testable non-functional requirement?

  1. The dashboard must load in three seconds for 200 users Correct answer.
  2. The dashboard should feel fast to field technicians during peak season
  3. The app should perform well during the peak season
  4. Users expect the mobile app to be quick

Explanation

A testable non-functional requirement states a measurable target, the workload under which it applies, and therefore a verifiable pass condition. Qualitative descriptors such as fast or quick cannot be validated in testing.

Question 15Perform solution envisioning and requirement analysis

Which analysis activity determines whether legacy data can realistically be migrated to the new solution?

  1. Reviewing the vendor's release notes
  2. Configuring duplicate detection rules
  3. Enabling audit logging on the target environment
  4. Profiling source data quality and volume Correct answer.

Explanation

Migration feasibility depends on the volume, quality, structure, and completeness of the source data, which must be profiled before effort and scope are agreed. Duplicate detection and auditing are target-side configuration concerns.

Question 16Perform solution envisioning and requirement analysis

Why should the architect plan solution segmentation before build begins?

  1. To ensure every user has the System Administrator role
  2. To reduce the number of licenses the customer must buy
  3. To deliver and patch components independently Correct answer.
  4. To avoid the need for a test environment

Explanation

Segmenting a solution into smaller, independently deployable units reduces deployment risk and allows components to be versioned and patched separately. Licensing and environment requirements are unaffected by segmentation.

Question 17Perform solution envisioning and requirement analysis

A requirement involves reading data from an on-premises SQL database. What should the architect confirm during requirement analysis?

  1. That premium licensing and a data gateway are available Correct answer.
  2. That the database schema is normalized to third normal form
  3. That all users hold a Microsoft 365 E3 license
  4. That the app is built as a canvas app rather than model-driven

Explanation

Connecting Power Platform to on-premises data requires a data gateway and premium connectivity, so premium licensing for makers and users must be confirmed during analysis. Assuming base productivity licenses cover this produces an unusable design.

Question 18Perform solution envisioning and requirement analysis

Which evidence best demonstrates that a proposed solution has a positive business case?

  1. The delivery team has experience in the industry
  2. Quantified benefits exceed the projected cost Correct answer.
  3. The customer's leadership approves the project budget
  4. The solution uses the latest preview features

Explanation

A business case is credible when benefits, expressed in measurable terms, exceed total cost of ownership over a defined period. Technology novelty, approvals, and team experience do not by themselves demonstrate value.

Question 19Perform solution envisioning and requirement analysis

A stakeholder has high influence over the project but low interest in its detail. How should the architect engage them?

  1. Keep them satisfied with periodic summaries Correct answer.
  2. Invite them to every design workshop
  3. Send them the full daily status report
  4. Ignore them until they request an update in person

Explanation

High-influence, low-interest stakeholders need enough communication to stay supportive without being overwhelmed. Concise periodic summaries keep them satisfied and prevent them from becoming late-stage blockers.

Question 20Perform solution envisioning and requirement analysis

What distinguishes a pilot from a proof of concept?

  1. A pilot is always shorter than a proof of concept
  2. A proof of concept must show business value, while a pilot does not
  3. A pilot validates the solution with a limited set of real users Correct answer.
  4. A pilot is run only with IT staff, while a proof of concept uses real users

Explanation

A proof of concept tests technical feasibility outside production, while a pilot delivers a functioning slice of the solution to a limited group of real users to validate it before broad rollout. Pilots therefore produce operational and adoption feedback that proofs of concept do not.

Question 21Perform solution envisioning and requirement analysis

A customer needs inventory management that closely matches a standard capability but requires a country-specific tax rule that is not offered out of the box. What should the architect recommend first?

  1. Replace the inventory process with an Excel workbook managed by IT
  2. Use the standard capability and extend it for the tax rule Correct answer.
  3. Build a fully custom inventory app in Power Apps
  4. Defer the tax rule to a post-go-live enhancement

Explanation

Reusing standard capability lowers cost and long-term maintenance risk, and extensions should be limited to the identified gap. A full custom build recreates functionality that already exists and complicates future upgrades.

Question 22Perform solution envisioning and requirement analysis

Two business units require the same field to enforce different mandatory rules. What is the most appropriate action for the architect?

  1. Ask the Microsoft support team to decide the rule
  2. Choose the rule from the unit with the larger budget
  3. Facilitate a joint decision and document the rule Correct answer.
  4. Build both rules and let users select which one applies

Explanation

Conflicting requirements are resolved by a documented business decision owned by the accountable stakeholders. The architect's role is to make the trade-offs visible and record the agreed outcome as a single source of truth for build and test.

Question 23Perform solution envisioning and requirement analysis

A customer requires that customer data remain in its home country while also requesting a shared global dashboard. What should the architect do during requirement analysis?

  1. Exclude the global dashboard from the project scope
  2. Store the primary data in the cheapest available region
  3. Assume the default tenant region satisfies the requirement
  4. Confirm residency needs and identify compliant options Correct answer.

Explanation

Residency and compliance constraints determine where data may be stored and who may access it, so they must be confirmed early and reflected in the design. Assuming defaults or silently removing a requested capability both create compliance or business risk.

Question 24Perform solution envisioning and requirement analysis

The approved scope cannot be delivered within the fixed budget and timeline. What should the architect recommend?

  1. Deliver all requirements with reduced testing
  2. Deliver the requirements in the order developers prefer
  3. Request additional budget without reviewing scope
  4. Agree a minimum viable product and phase the rest Correct answer.

Explanation

When time and budget are fixed, scope is the variable that must be re-baselined with the stakeholders. Delivering a valuable core first preserves quality while deferring lower-priority requirements to a planned later phase.

Question 25Perform solution envisioning and requirement analysis

A customer states the goal of improving technician satisfaction. What should the architect define so the outcome can be validated after go-live?

  1. A baseline, a target metric, and a measurement method Correct answer.
  2. A statement in the project charter that satisfaction matters
  3. A list of the features the technicians requested
  4. A survey tool license for the support team

Explanation

A goal becomes measurable only when a baseline, a target, and the measurement method and timing are defined in advance. Without these, post-go-live benefits cannot be attributed to the solution.

Question 26Perform solution envisioning and requirement analysis

What is the primary purpose of a solution vision statement?

  1. To document the detailed technical design of each system component.
  2. To list every functional requirement the solution must satisfy.
  3. To record the project budget and resource assignments for approval.
  4. To align stakeholders on the intended outcome and direction. Correct answer.

Explanation

A vision statement communicates the desired business outcome and the overall direction of the solution. It provides a shared reference for later requirement and design decisions without replacing detailed requirements or design documents.

Question 27Perform solution envisioning and requirement analysis

Which statement is a business requirement rather than a functional requirement?

  1. The system must send an email when a case is closed.
  2. The organization must cut claim processing time by 20 percent. Correct answer.
  3. The application must display open cases sorted by priority.
  4. Users must be able to attach documents to a case record.

Explanation

Business requirements describe measurable organizational outcomes or goals. Functional requirements describe specific behavior the solution must perform, such as sending email or displaying records.

Question 28Perform solution envisioning and requirement analysis

Why does the architect create user personas during requirement analysis?

  1. To assign named individuals to each security role in the solution.
  2. To represent user groups' goals and behaviors when defining requirements. Correct answer.
  3. To document the database schema needed to store user profile records.
  4. To estimate the licensing cost for each department that uses the solution.

Explanation

Personas summarize the goals, tasks, and pain points of representative user groups. They help the team derive and validate requirements from the user's perspective.

Question 29Perform solution envisioning and requirement analysis

A customer states that single sign-on must use its existing identity provider. How should the architect record this?

  1. As a user story for the identity administration team.
  2. As an open risk to be resolved after the solution is built.
  3. As a constraint that limits the authentication design options. Correct answer.
  4. As a functional requirement for the sign-in page layout.

Explanation

A fixed organizational or technical condition that restricts design choices is a constraint. Recording it as a constraint ensures authentication options are evaluated against the existing identity provider.

Question 30Perform solution envisioning and requirement analysis

What is the purpose of a future-state process model in envisioning?

  1. To show how work will flow after the solution is implemented. Correct answer.
  2. To replace the need for documenting business requirements.
  3. To capture the exact configuration of the legacy applications.
  4. To record the historical reasons for earlier process changes.

Explanation

A future-state model describes the intended process after the solution is in place. It helps stakeholders validate the target way of working and identify the changes the solution must support.

Question 31Perform solution envisioning and requirement analysis

What is the primary responsibility of a business process owner during requirement analysis?

  1. Managing the project budget and vendor contracts.
  2. Approving the technical architecture of the integration layer.
  3. Deciding the target process and accepting its requirements. Correct answer.
  4. Writing the automated test scripts for the process.

Explanation

A process owner represents the business side of a process and has authority over how it should operate. This includes validating and accepting the requirements that describe the target process.

Question 32Perform solution envisioning and requirement analysis

When should the architect use interviews rather than a broad survey to elicit requirements?

  1. When the goal is to collect anonymous feedback at low cost.
  2. When the questions are fully closed and require numeric answers.
  3. When detailed insight is needed from a small number of experts. Correct answer.
  4. When thousands of users must provide input within one week.

Explanation

Interviews allow the architect to probe responses and explore complex or nuanced needs. They are most efficient with a small number of knowledgeable participants.

Question 33Perform solution envisioning and requirement analysis

What makes a project success criterion measurable?

  1. It is listed in the solution vision statement.
  2. It includes a target value and a time frame. Correct answer.
  3. It is approved by the project sponsor at kickoff.
  4. It is reviewed during every status meeting.

Explanation

A measurable success criterion defines a specific target and the period in which it must be achieved. Approval, visibility, and review frequency do not by themselves make a criterion measurable.

Question 34Perform solution envisioning and requirement analysis

In a RACI matrix for requirement workshops, what does the "A" role represent?

  1. The person who must be informed of the outcome afterward.
  2. The person accountable for the final decision or deliverable. Correct answer.
  3. The person who performs the workshop facilitation tasks.
  4. The person who provides optional advice during discussion.

Explanation

In RACI, the accountable role owns the final result and has authority to approve it. Only one person should normally be accountable for a given activity or deliverable.

Question 35Perform solution envisioning and requirement analysis

A project has users in four time zones who cannot meet in person. Which elicitation approach is most appropriate?

  1. Facilitated virtual sessions combined with asynchronous surveys. Correct answer.
  2. A single in-person workshop with only local users.
  3. A final walkthrough after the solution is deployed.
  4. Review of the legacy system source code by the architect.

Explanation

Virtual facilitated sessions allow discussion across time zones, while asynchronous surveys capture input from those unable to attend live. Combining methods improves coverage while respecting availability constraints.

Question 36Perform solution envisioning and requirement analysis

In MoSCoW prioritization, what does the "Could have" category mean?

  1. The requirement is mandatory for the release to be accepted.
  2. The requirement is desirable but not essential for this release. Correct answer.
  3. The requirement is not permitted in the current scope.
  4. The requirement must be included if any buffer remains.

Explanation

Could-have requirements are nice to include but are not essential for the release to be acceptable. They may be deferred if time or budget is constrained.

Question 37Perform solution envisioning and requirement analysis

Two stakeholders disagree on a requirement during a workshop. What should the architect do first?

  1. Escalate immediately to the project steering committee.
  2. Choose the requirement supported by the more senior stakeholder.
  3. Clarify each stakeholder's underlying need and decision authority. Correct answer.
  4. Remove the requirement from scope until after go-live.

Explanation

The architect should first understand the needs behind each position and identify who has decision authority for that area. This often resolves the conflict without unnecessary escalation.

Question 38Perform solution envisioning and requirement analysis

Why should the architect review licensing requirements during envisioning?

  1. Licensing is only relevant after the production deployment.
  2. Licensing determines the database normalization rules for the solution.
  3. Licensing can constrain which solution options are financially viable. Correct answer.
  4. Licensing replaces the need for a non-functional requirements workshop.

Explanation

License costs and entitlement models can eliminate otherwise valid solution options or change the business case. Early review prevents selecting a design that the customer cannot afford or legally operate.

Question 39Perform solution envisioning and requirement analysis

During requirement analysis for an integration, which detail should the architect confirm with the system owner?

  1. The physical location of the external system's support team.
  2. The color scheme used by the external system's user interface.
  3. The data format, frequency, and direction of the exchange. Correct answer.
  4. The number of developers who built the external system.

Explanation

Integration requirements depend on what data moves, how often, and in which direction. These details determine interface design, error handling, and testing needs.

Question 40Perform solution envisioning and requirement analysis

Which technique best identifies security and compliance requirements early?

  1. Asking only the IT operations team during the build phase.
  2. Copying the security section from a previous project document.
  3. Waiting for the penetration test results after deployment.
  4. Reviewing regulations and interviewing compliance officers. Correct answer.

Explanation

Security and compliance needs are often driven by external regulation and internal policy. Reviewing applicable rules and involving compliance specialists reveals obligations before design decisions are fixed.

Question 41Perform solution envisioning and requirement analysis

Which format expresses acceptance criteria for a user story clearly?

  1. The user wants the feature to work well at all times.
  2. Given a condition, when an action occurs, then an outcome results. Correct answer.
  3. The feature should be built using the latest technology stack.
  4. The developer will decide when the story is complete.

Explanation

Given-When-Then expresses a testable scenario with a precondition, an action, and an expected result. It gives the team and stakeholders a shared basis for verification.

Question 42Perform solution envisioning and requirement analysis

What is the main purpose of a definition of ready for requirements?

  1. To confirm that all project risks have been eliminated.
  2. To replace the need for stakeholder review meetings.
  3. To ensure a requirement is understood and actionable before work starts. Correct answer.
  4. To document the final acceptance sign-off after delivery.

Explanation

A definition of ready sets the criteria a requirement must meet before the team accepts it for design or build. This reduces rework caused by unclear, incomplete, or unvalidated requirements.

Question 43Perform solution envisioning and requirement analysis

A stakeholder requests a new report during the build phase. What should the architect do first?

  1. Ask the development team to build it without documenting the request.
  2. Evaluate the request against approved scope and follow change control. Correct answer.
  3. Add the report to the current sprint to keep the stakeholder satisfied.
  4. Reject the request because no changes are allowed after design.

Explanation

New requests should be assessed against the approved scope and handled through the agreed change control process. This protects budget, timeline, and traceability while allowing justified changes.

Question 44Perform solution envisioning and requirement analysis

When is a prototype most useful in requirement analysis?

  1. When the requirements are fully frozen and no feedback is expected.
  2. When the solution has already passed user acceptance testing.
  3. When users need to visualize a process before confirming requirements. Correct answer.
  4. When the team needs to stress-test production data volumes.

Explanation

A prototype helps users react to a concrete representation of a process or interface before requirements are finalized. This is valuable when needs are ambiguous or difficult to express in words.

Question 45Perform solution envisioning and requirement analysis

What should an architecture decision log record?

  1. The complete source code for custom components.
  2. The detailed task assignments for each developer.
  3. Each significant decision, its rationale, and its consequences. Correct answer.
  4. Every informal conversation held during the project.

Explanation

A decision log captures important choices, why they were made, and what trade-offs they create. This preserves context for future changes and helps new team members understand the solution.

Question 46Perform solution envisioning and requirement analysis

A solution will store both regulated personal data and public reference data. What should the architect define during requirement analysis?

  1. One access level for all users to reduce licensing costs.
  2. Separate handling and protection requirements for each data category. Correct answer.
  3. A single retention period for all data to simplify administration.
  4. The same encryption key for every environment and data type.

Explanation

Different data categories carry different sensitivity and regulatory obligations. Defining protection and handling requirements by category ensures controls match the risk and legal requirements.

Question 47Perform solution envisioning and requirement analysis

Which element is essential in a solution blueprint?

  1. The historical budget of the previous solution provider.
  2. The individual performance goals of project team members.
  3. The mapping of business capabilities to solution components. Correct answer.
  4. The daily stand-up schedule for the delivery team.

Explanation

A solution blueprint shows how business capabilities are supported by applications, data, integrations, and technology. This mapping keeps the solution aligned to the business outcomes defined during envisioning.

Question 48Perform solution envisioning and requirement analysis

An organization plans to operate the solution in a new country. What should the architect do during envisioning?

  1. Delegate the review to the implementation team after design.
  2. Delay regulatory review until the solution is deployed.
  3. Assume the existing country's requirements apply unchanged.
  4. Identify local legal, tax, and data protection obligations. Correct answer.

Explanation

Operating in a new country can introduce different legal, tax, privacy, and data residency obligations. Identifying them during envisioning allows the solution direction and business case to account for them.

Question 49Perform solution envisioning and requirement analysis

Which activity best assesses organizational readiness for a new solution?

  1. Estimating the number of servers needed for production.
  2. Reviewing the source code for coding standard violations.
  3. Assessing impacted roles, skills, and process changes. Correct answer.
  4. Comparing the new solution against competitor products.

Explanation

Organizational readiness depends on how people's roles, skills, and daily processes will change. Assessing those impacts helps plan training, communication, and adoption support.

Question 50Perform solution envisioning and requirement analysis

How should the architect link requirements to build and test artifacts?

  1. Store requirements only in email threads with the project sponsor.
  2. Give each requirement a unique ID used by related work items. Correct answer.
  3. Rename test cases to match the names of the developers.
  4. Wait until go-live to connect requirements to test results.

Explanation

A stable unique identifier allows requirements to be traced to design, build, and test artifacts throughout delivery. This supports impact analysis and evidence that each requirement was verified.