nerdexam
Microsoft

AZ-500 · Question #281

Case Study 3 - Fabrikam, Inc General Overview Fabrikam, Inc. is a consulting company that has a main office in Montreal and branch offices in Seattle and New York. Fabrikam has IT, human resources…

The correct answer is D. Session. Explanation Option D (Session) is correct because the requirement to force reauthentication after three hours for SharePoint Online is controlled through the Session settings in a Conditional Access policy, specifically using the Sign-in frequency control, which allows…

Submitted by rachelw· Mar 6, 2026Secure identity and access

Question

Case Study 3 - Fabrikam, Inc General Overview Fabrikam, Inc. is a consulting company that has a main office in Montreal and branch offices in Seattle and New York. Fabrikam has IT, human resources (HR), and finance departments. Existing Environment Network Environment Fabrikam has a Microsoft 365 subscription and an Azure subscription named subscription1. The network contains an on-premises Active Directory domain named Fabrikam.com. The domain contains two organizational units (OUs) named OU1 and OU2. Azure AD Connect cloud sync syncs only OU1. The Azure resources hierarchy is shown in the following exhibit. The Azure Active Directory (Azure AD) tenant contains the users shown in the following table. Azure AD contains the resources shown in the following table. Subscription1 Resources Subscription1 contains the virtual networks shown in the following table. Subscription1 contains the network security groups (NSGs) shown in the following table. Subscription1 contains the virtual machines shown in the following table. Subscription1 contains the Azure key vaults shown in the following table. Subscription1 contains a storage account named storage1 in the West US Azure region. Planned Changes and Requirements Planned Changes Fabrikam plans to implement the following changes: Create two application security groups as shown in the following table. Associate the network interface of VM1 to ASG1. Deploy SecPol1 by using Azure Security Center. Deploy a third-party app named App1. A version of App1 exists for all available operating systems. Create a resource group named RG2. Sync OU2 to Azure AD. Add User1 to Group1. Technical Requirements Fabrikam identifies the following technical requirements: The finance department users must reauthenticate after three hours when they access SharePoint Online. Storage1 must be encrypted by using customer-managed keys and automatic key rotation. From Sentinel1, you must ensure that the following notebooks can be launched: - Entity Explorer - Account - Entity Explorer - Windows Host - Guided Investigation Process Alerts VM1, VM2, and VM3 must be encrypted by using Azure Disk Encryption. Just in time (JIT) VM access for VM1, VM2, and VM3 must be enabled. App1 must use a secure connection string stored in KeyVault1. KeyVault1 traffic must NOT travel over the internet. You need to meet the technical requirements for the finance department users. Which CAPolicy1 settings should you modify?

Options

  • ACloud apps or actions
  • BConditions
  • CGrant
  • DSession

How the community answered

(34 responses)
  • A
    3% (1)
  • B
    15% (5)
  • C
    9% (3)
  • D
    74% (25)

Explanation

Explanation

Option D (Session) is correct because the requirement to force reauthentication after three hours for SharePoint Online is controlled through the Session settings in a Conditional Access policy, specifically using the Sign-in frequency control, which allows administrators to define how often users must re-authenticate when accessing specific cloud apps.

Option A (Cloud apps or actions) is wrong because this setting only determines which applications the policy applies to (e.g., SharePoint Online) - it doesn't control authentication behavior or session duration.

Option B (Conditions) is wrong because Conditions define who or what triggers the policy (e.g., user risk, device platform, location), not what happens during an active session in terms of reauthentication timing.

Option C (Grant) is wrong because Grant controls access decisions such as requiring MFA or a compliant device before granting access - it does not manage how long a session remains valid before requiring reauthentication.

Memory Tip

Think of it this way: "Session = how long you stay logged in." If the requirement mentions time limits or reauthentication frequency, always look to Session controls in Conditional Access - the Sign-in frequency setting lives there and is the go-to tool for time-based authentication requirements.

Topics

#Conditional Access#Azure AD#Authentication#Session Control

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-500 Practice