[&] INE industrial engineering is moving their on premises partner management application written in ASP.NET core to Azure. INE will use Azure AD for authentication. INE has the following requirements:

* -All user accounts will be managed on premises through an Active Directory domain
* -Any user whose account is disabled must immediately be denied logins
* -On-premises users must have a single sign-on experience
*  -The system will support on-premises and internet based logins
* -This needs to be configured with the least administrative effort and least cost

What is the recommended authentication architecture for the INE application once it is in Azure?
- Configure Azure AD connect to use ADFS federation. Install ADFS on a member server with a stand-alone server running ADFS Web Application Proxy. Configure the INE application to use Azure AD for authentication.
- Configure Azure AD connect to use ADFS federation. Install ADFS on a stand-alone server and configure the INE application to use Azure AD for authentication.
- Configure Azure AD connect to use pass-through authentication with the SSO option. Configure the INE application to use Azure AD for authentication. -- Correct
- Install Active Directory Federated Service on a stand-alone server in the INE data center. Configure the application to use ADFS for authentication.

[&] Your company hosts a web application in Azure that uses Azure AD with ADFS for authentication. On-premises users can log in to an Azure hosted web app, but remote users cannot. What is the most likely cause?
- The ADFS server is unavailable
- The WAP server cannot access a domain controller
- The NSG associated with the WAP server does not allow incoming traffic on port 1433
- The public DNS setting is not correct -- Correct