Which one of the following is a benefit of creating an Application Properties page for each application you develop?

Question

Options

• AAn Application Properties page is a common landing page for an application.
• BApplication users know to go to the Application Properties page to change the appearance of an
• CApplication Properties allow a developer to override the application properties inherited from
• DApplication Properties allow a developer or admin to make changes to an application's behavior

• B
  5% (1)
• C
  9% (2)
• D
  86% (19)

Explanation

Option D is correct because an Application Properties page gives developers and admins a centralized, no-code interface to adjust configurable settings - such as toggles, thresholds, or integration endpoints - without touching the underlying code. This is a core best practice: separating configuration from logic so behavior can be changed safely at runtime.

Why the distractors are wrong:

• A is incorrect because a landing/home page is a UI concept for navigation, not what an Application Properties page provides - it's a configuration interface, not a welcome screen.
• B is incorrect because end users typically don't have access to Application Properties; it's an admin/developer tool, not a self-service appearance customizer for general users.
• C is incorrect because Application Properties don't override inherited properties by default - that describes scope/inheritance overriding, which is a different mechanism.

Memory tip: Think of Application Properties as the app's "settings panel" - just like a phone's Settings app lets you change behavior without reinstalling anything, an Application Properties page lets admins tune the app without touching code.

No community discussion yet for this question.