Exam PL-600 topic 1 question 38 discussion

• Retail employees must use the application on a company-provided tablet device. = NON-FUNCTIONAL No requirement here to build anything out • The app must store data offline. = FUNCTIONAL Requirement to implement offline capabilities • Environment capacity must be monitored to ensure usage stays within 80 percent of available capacity = NON-FUNCTIONAL Regarding the performance / usability of the system so is therefore nonfunctional • Apps are shared with security group teams for users to access. = FUNCTIONAL Bit of a trick question as security is mainly non-functional; but there is a requirement here to share the apps with certain teams which means its functional.

Functional requirements describe what the solution needs to do or its behaviours. Non-functional requirements describe non-behaviour aspects of the solution such as performance requirements. Hence: * Retail employees must use the application on a company-provided tablet device - NF - This has nothing to do with its behaviours. This is about how users will access it * The app must store data offline - F - This is functionality that the app provides * Environment capacity must be monitored to ensure usage stays within 80 percent of available capacity - NF - A performance requirement * Apps are shared with security group teams for users to access - NF - Nothing to do with how it works or its behaviours. That's just the security model. Source: https://learn.microsoft.com/en-us/training/modules/work-with-requirements/4-non-functional-requirements. To conclude: NF F NF NF

Functional, Functional, Non Functional, Non Functional. Functional Requirements These define what the system should do—the core features and behaviors. Device-Specific Access Offline Data Storage User Access Management NF Monitoring & Capacity Management Data access must be restricted based on roles and security groups

NF, F, NF, F is the Answer

Based on the definition of Functional requirement : Describes what a solution needs to do. I can say that NF, F, NF, NF.

Retail employees must use the application on a company-provided tablet device. Functional Requirement: This specifies a functional aspect of the solution, focusing on the device that will be used to access the application. The app must store data offline. Functional Requirement: This requirement outlines a specific feature of the application, namely its ability to store data offline. Environment capacity must be monitored to ensure usage stays within 80 percent of available capacity. Non-Functional Requirement: This is related to system performance and capacity management, focusing on operational and performance criteria rather than a specific feature. Apps are shared with security group teams for users to access. Functional Requirement: This describes how the application will be distributed and accessed, outlining a specific feature related to user permissions and access.

All are non functional

As architect, I believe the last 3 are Non Functional because they define the solution implementation requirements other than user stories. i.e. Data must store offline, it is absolutely functional. Security Group - Must be non functional. The first one is questionably Functional. But can be a NF as well tbh. This is about implementation consideration so the solution design need to meet it. Other than user stories a feature to be designed.

Functional Non Functional Non Functional Functional

It's Non-Functional for all 4.

Functional Requirements: Retail employees must use the application on a company-provided tablet device. The app must store data offline. Apps are shared with security group teams for users to access. Non-Functional Requirements: Environment capacity must be monitored to ensure usage stays within 80 percent of available capacity.

The last 3 are clearly non-functional, I believe the first one is too from the format but can't quite justify why as it doesn't neatly fall into any category. Retail employees must use a device - Questionable but Functional. The app must store data offline - Non-Functional (Data retention/residency) Environment capacity must be monitored - Non-Functional (Scalability) Apps are shared with security group members - Non-Functional (Security) https://learn.microsoft.com/en-us/training/modules/work-with-requirements/4-non-functional-requirements

• Retail employees must use the application on a company-provided tablet device. (power App is available on mobile, so F) • The app must store data offline. (F to, it's a setting you can enable) • Environment capacity must be monitored to ensure usage stays within 80 percent of available capacity. (n-F, need programming or coding) • Apps are shared with security group teams for users to access. (F, out of the boxe security feature) F, F, NF,F

according to Chat AI the answers are functional, NF, NF,NF

A Power Platform application can be configured for either mobile or tablet screens so there is control on that functionality requirement from a Power Platform architect's perspective

Non-functional requirements capture the elements that users might not directly care about but are important to support the proposed architecture and operational viability of the solution. Examples of common non-functional requirement types include: Data retention/residency https://learn.microsoft.com/en-us/training/modules/work-with-requirements/4-non-functional-requirements * The app must store data offline = Non-Functional

4. Is Functional. You can reformulate this requirement like The App should allow users from only certain groups