Identifying Functional Requirements for Microsoft Power Pages
A company plans to use Microsoft Power Pages. The company gathers business requirements. You need to identify the functional requirements. Which two requirements should you gather? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Community Votes
72% of anonymous learners picked answer CE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the ability to differentiate between functional needs (user actions) and non-functional constraints (performance, security, compliance). A common trap is selecting performance metrics or privacy controls as functional features.
This question distinguishes between functional requirements (what the system does) and non-functional requirements (how well it performs or complies). The correct options identify specific user capabilities enabled by Power Pages.
Many learners select Option B because data control is critical, but it is a privacy/compliance requirement, not a functional one. Others choose A, confusing scalability targets with feature definitions.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Functional requirements define what the system must do to satisfy business needs, typically focusing on user interactions and core capabilities. Option C describes Single Sign-On (SSO), which is a functional capability allowing users to authenticate seamlessly. Option E describes submitting a service request, which is a direct user action and core functionality of the site. Together, they represent complete solutions for how users interact with the platform.Why the Other Options Are Wrong
Option A specifies handling 100 concurrent visitors, which is a performance metric or scalability constraint, classified as a non-functional requirement. Option B addresses personal data control, which falls under privacy, security, and regulatory compliance (non-functional). Option D proposes using Azure Front Door for caching, which is a technical implementation detail or architectural decision rather than a high-level functional requirement gathered during the initial phase.Community Comment Notes
Community consensus strongly supports CE, with many noting that 'All other answers are non-functional.' One commenter clarified that privacy concerns like Option B are regulatory compliance issues, not functional ones. Another emphasized that SSO is a functional access method, reinforcing why C is correct alongside the actionable E.Official Reference
Exam Strategy
When asked for 'functional' requirements, look for verbs describing user actions or system behaviors (e.g., 'log in', 'submit', 'view'). Avoid options that describe metrics (speed, capacity), standards (privacy, security), or specific technology stacks unless they directly enable a user function.
Frequently Asked Questions
Why is data control not a functional requirement?
Data control relates to privacy policies and regulatory compliance (GDPR/CCPA), which are non-functional constraints defining how the system handles data securely, not what the user does.
Is concurrency a functional requirement?
No. Handling a specific number of concurrent users is a performance or scalability metric, which is a non-functional requirement describing system quality attributes.