Correct Answer:

1 - Create a service namespace.
2 - Register the application as the relying party.
3 - Add a Security Token Service (STS) reference in Visual Studio 2012.
4 - Add the third-party as the identity provider.
5 - Generate provider rules for claims.
Explanation:
Box 1: Create a service namespace
The first step is to create an ACS Namespace. This is your Security Token Services (STS) that will generate Signed Identity tokens to be consumed by WAP. This will also be the only STS that WAP will trust.
Box 2: Register the application as a relaying partner.
Now that the Namespace is created, you will have to tell it about the WAP Portals that is expecting tokens from it. We add the WAP Tenant Portal as a Relying Party to ACS (Access Control Services).
Box 3: Add a Security Token Service (STS) reference in Visual Studio 2012.
Now that the Namespace is created, you will have to tell it about the WAP Portals that is expecting tokens from it.
1. Click on Relying Party Applications and click on Add to add the Windows Azure Pack tenant Portal as a Relying Party to this namespace. This essentially tells the ACS namespace that the Tenant Portal is expecting it to provide user identities.
2. You will now go to the Add Relying Party Application page where you can enter details about the WAP tenant Portal.
3. The easier option is to provide the federation Metadata from the tenant portal. Save the XML file locally on your computer
4. Now back in the ACS management portal, Upload the federation metadata file and provide a Display Name for the Relying Party.
5. Scroll Down to the Token Format section and choose the token format to be 'JWT'. By Default, the Windows Live Identity Provider will be selected. Deselect it if you do not want to allow users to sign in using their Live id. Under the Token Signing Settings section, select X.509 Certificate as the Type. Click on Save.
Box 4: Add the third-party as the identity provider.
We have our ACS and WAP portals setup. We now have to find a source of Identities that can be flown in to the WAP Portals through ACS. We configure external services to act as Identity Providers Box 5: Generate provider rules for claims We now have our Relying Party and our Identity Providers set up. We should now tell ACS how to transform the incoming Claims from these Identity providers so that the Relying Party can understand it. We do that using Rule Groups which are a set of rules that govern Claim Transformation. Since, we have two identity Providers, we will have to create a rule for each of these.
References: https://blogs.technet.microsoft.com/privatecloud/2014/01/17/setting-up-windows-azure-active-directory-acs-to-provide-identities-to-windows-azure-pack/

Correct Answer: A  🗳️

Correct Answer:

1 - Use the FROM instruction to define the base image.
2 - Use the WORKDIR instruction to define the working directory.
3 - Use the COPY instruction to copy the source code into the image and then use the RUN instruction to restore NuGet packages.
4 - Use the ENTRYPOINT instruction to use the container as an executable.
5 - Use the EXPOSE instruction to specify the listen port and build and run the application.
Explanation:
Step 1: Use the FROM instruction to define the base image.
FROM creates a layer from the ubuntu Docker image.
The first FROM command is an important Docker command, allowing you to pull dependencies from other images.
Step 2: Use the WORKDIR instruction to define the working directory
The WORKDIR instruction sets the working directory for any RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile.
Step 3: Use the COPY instructions to copy the source code into the image and then use the RUN instruction to restore NuGet packages.
Step 4: Use the ENTRYPOINT instruction to use the container as an executable Step 5: Use the EXPOSE instruction to specify the listen port and build and run the application.
References:
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/

Correct Answer:

Explanation:
Example:
This class implements IRouteHandler and has only one method "GetHttpHandler". The main purpose of this class is to return the instance of CustomHandler class. In the constructor, we are passing the RequestContext to the handler.
{
public class CustomRouteHandler : IRouteHandler
{
public IHttpHandler GetHttpHandler(RequestContext requestContext)
{
return new CustomHandler(requestContext);
}
}
References: http://msdn.microsoft.com/en-us/library/system.web.routing.iroutehandler.gethttphandler.aspx

Correct Answer:

Explanation:
ApplicationDetailCodeBase: Identifies the offset for the application detail event codes. This field is constant.
WebRequestEvent.Raise()
Raises an event by notifying any configured provider that the event has occurred. (Inherited from WebBaseEvent.)
https://msdn.microsoft.com/en-us/library/system.web.management.webrequestevent(v=vs.110).aspx