Does the solution meet the goal?

Case Study 2 – Coho Winery

LabelMaker app

Coho Winery produces bottles, and distributes a variety of wines globally. You are developer implementing highly scalable and resilient applications to support online order processing by using Azure solutions.

Coho Winery has a LabelMaker application that prints labels for wine bottles. The application sends data to several printers. The application consists of five modules that run independently on virtual machines (VMs). Coho Winery plans to move the application to Azure and continue to support label creation.

External partners send data to the LabelMaker application to include artwork and text for custom label designs.

Data

You identify the following requirements for data management and manipulation:

– Order data is stored as nonrelational JSON and must be queried using Structured Query Language (SQL).

– Changes to the Order data must reflect immediately across all partitions. All reads to the Order data must fetch the most recent writes.

You have the following security requirements:

– Users of Coho Winery applications must be able to provide access to documents, resources, and applications to external partners.

– External partners must use their own credentials and authenticate with their organization’s identity management solution.

– External partner logins must be audited monthly for application use by a user account administrator to maintain company compliance.

– Storage of e-commerce application settings must be maintained in Azure Key Vault.

– E-commerce application sign-ins must be secured by using Azure App Service authentication and Azure Active Directory (AAD).

– Conditional access policies must be applied at the application level to protect company content

– The LabelMaker applications must be secured by using an AAD account that has full access to all namespaces of the Azure Kubernetes Service (AKS) cluster.

LabelMaker app

Azure Monitor Container Health must be used to monitor the performance of workloads that are deployed to Kubernetes environments and hosted on Azure Kubernetes Service (AKS).

You must use Azure Container Registry to publish images that support the AKS deployment.

Calls to the Printer API App fail periodically due to printer communication timeouts.

Printer communications timeouts occur after 10 seconds. The label printer must only receive up to 5 attempts within one minute.

The order workflow fails to run upon initial deployment to Azure.

Order json.

Relevant portions of the app files are shown below. Line numbers are included for reference only.

This JSON file contains a representation of the data for an order that includes a single item.

Order. json

Note: In this section you will see one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem, and you must determine whether the solution meets the stated goals. More than one solution might solve the problem. It is also possible that none of the solutions solve the problem.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.

You need to meet the LabelMaker application security requirement.

Solution: Place the Azure Active Directory account into an Azure AD group. Create a ClusterRoleBinding and assign it to the group.

Does the solution meet the goal?
A . Yes
B . No

View Answer

Answer: A

Explanation:

Scenario: The LabelMaker applications must be secured by using an AAD account that has full access to all namespaces of the Azure Kubernetes Service (AKS) cluster.

Permissions can be granted within a namespace with a RoleBinding, or cluster-wide with a ClusterRoleBinding.

References: https://kubernetes.io/docs/reference/access-authn-authz/rbac/