Information Security

Single Sign-on (SSO) stores and maps user credentials across multiple systems, allowing users to authenticate once and access various applications without repeated logins. This is not about limiting concurrent users (A) - it's about convenience and centralized credential management.

Security principals are AD objects that can authenticate and receive permissions: Users, Security Groups, and Computers. Distribution Groups are NOT security principals - they're used only for email distribution in Exchange and cannot be assigned permissions or authenticate.

McAfee is the antivirus vendor that releases signature updates for their own product. ePO is McAfee's management console, not the signature source. Microsoft creates signatures for Windows Defender, not McAfee.

ePO (ePolicy Orchestrator) is McAfee's centralized management console. It manages antivirus signatures, product updates, and firewall policies across endpoints. GPO and data encryption are Windows features, not ePO-managed.

The McAfee Agent is client software that must be installed on all managed PCs and endpoints. It acts as the communication bridge between endpoint systems and the ePO server. Options A, B, and C are incorrect - the agent is not a definition, not specifically for encryption, and not merely a service.

SharePoint's default permission levels are Reader (read-only), Contributor (add/edit items), Web Designer (design permissions), and Administrator (full control). Option C incorrectly says 'Web Administrator' instead of 'Web Designer'. Option A lists 'Manager' which isn't a standard permission level.

To supply Windows credentials to the Web application, Anonymous access must be disabled so that IIS prompts the user for credentials. Enabling Integrated Windows authentication allows the browser to securely negotiate and send these credentials automatically without prompting the user in a domain environment.

In web farm scenarios with multiple servers, RSA encryption is suitable because RSA keys can be exported and shared across servers. DPAPI (Data Protection API) is machine-specific and cannot share keys across servers in a farm, making it inappropriate for distributed environments.

The -pe (Protect Encrypt) option of aspnet_regiis is specifically designed to encrypt configuration sections like connectionStrings or appSettings in Web.config. The -e option is for export, -enc is not a valid aspnet_regiis command, and 'All of the Above' is incorrect since only -pe works for encryption.

In ASP.NET configuration, ? represents anonymous users, and * represents all users. The element explicitly prevents anonymous users from accessing the application, while allowing authenticated users. Distractors like explicitly allow anonymous access, and `` denies everyone.

All three mechanisms - cookies, hidden form fields, and SSL sessions - are valid methods for session tracking in web applications. Cookies are the most common, hidden fields provide a fallback, and SSL sessions leverage the secure session identifier. Different applications may use one or multiple of these approaches.

Windows Authentication integrates with Active Directory and is ideal for intranets where all users are domain members. It provides seamless authentication without prompting for credentials. Forms Authentication is for internet applications, Passport is deprecated, and Windows is the correct intranet choice.

In Web Farm scenarios with multiple servers, RSA encryption is suitable because it uses machine-independent key containers that can be shared across servers. DPAPI relies on machine-specific keys and cannot work in a web farm environment. The question asks specifically about web farm scenarios, making RSA the correct choice.

A Single User ID application provides centralized user authentication (verifying identity) and authorization (controlling access permissions) across multiple systems.

Phishing is a social engineering attack where attackers send fraudulent emails pretending to be legitimate organizations. These emails often create urgency or threaten consequences to trick users into revealing sensitive information like passwords or financial details. Option D correctly describes this.