If time is set in the authorization element of Agile Controller, what is the purpose of configuring time in authentication and authorization rules?

Question

Options

• ASpecify the total duration of user access
• BSpecify the time point of user access
• CSpecify the deadline for users to go offline
• DSpecify the time frame for user access

• A
  3% (1)
• B
  5% (2)
• C
  13% (5)
• D
  80% (32)

Explanation

Configuring time in authentication and authorization rules within Agile Controller's authorization element defines a time frame - a bounded window (e.g., Monday–Friday, 08:00–18:00) during which a user is permitted access, making D correct.

Option A is wrong because the time setting does not measure a duration or accumulate how long a user has been connected - it has no counter or quota. Option B is wrong because a single "time point" implies a one-time moment (like a timestamp), whereas the rule defines a recurring range, not an instant. Option C is wrong because enforcing a deadline to go offline is a session-termination mechanism, not what authorization time rules govern.

Memory tip: Think of it like office hours - you don't get told how long you can stay or exactly when to leave; you're told the building is accessible only between certain hours. That bounded window = time frame = D.

No community discussion yet for this question.