Exam Ref Developing Microsoft Azure Solutions, 2nd About eBook formats Book ; eBook Prepare for Microsoft Exam —and help demonstrate your real-world mastery of Microsoft Azure solution development. Designed for experienced. The Exam Ref is the official study guide for Microsoft certification exams. Featuring concise, objective-by-objective reviews and strategic case scenarios and.
|Language:||English, Spanish, French|
|Genre:||Health & Fitness|
|Distribution:||Free* [*Registration needed]|
Editorial Reviews. About the Author. ZOINER TEJADA has more than 18 years of experience in the software industry as a software architect, CTO, and start-up. Exam Ref Developing Microsoft Azure Solutions, Second Edition. [ Michele Bustamante Edition/Format: eBook: Document. Rating: (not yet rated) 0. Prepare for Microsoft Exam —and help demonstrate your real-world mastery of the skills needed to develop Microsoft Azure solutions.
By creating a new website and then creating a new web hosting plan D. None of the above Objective 1. Conigure websites Azure Websites provides a comprehensive collection of settings that you can adjust to establish the environment in which your website runs, as well as tools to deine and manage the values of settings used by your web application code.
A fundamental pattern embraced by the coniguration model of Azure Websites is the separation of code from coniguration, and particularly the notion that the deployment environment can override coniguration.
This Objective 1. For example, code on your local machine can use a development coniguration that targets only development resources, a local development database for instance, but upon deployment to the production website, the production settings can transparently override the development settings so that the code uses the appropriate production coniguration, for instance to target an Azure SQL database, all without any explicit effort on your part.
Understanding website coniguration is critical to succeeding with Azure Websites. There is currently no information available on this topic in the context of Websites. Deining and using app settings App settings are represented as name-value pairs made available to your web application when it starts. The mechanism you use to access these values depends on the web platform in which your web application is programmed.
If your application is built using. NET, then you access the values of app settings just as you would access the AppSettings values stored in web. If your web application is built using another supported web platform, such as Node. Deining an app setting in the management portal existing portal To deine an app setting in the management portal, complete the following steps: Navigate to the Conigure tab of your website in the management portal accessed via https: Scroll down to App Settings.
In the list, type a name for the setting in the text box with the placeholder text KEY, and type a value for the setting in the text box with the placeholder text VALUE. Click Save on the command bar to persist and apply the new app setting. Deining an app setting in the management portal Preview portal To deine an app setting in the Preview portal, complete the following steps: Using an app setting from.
NET To retrieve an app setting, use the AppSettings property of the ConigurationManager class and access the setting by name, using it as the key to retrieve the value from the AppSettings collection. Listing shows an example of this in C.
AppSettings[key]; Objective 1. By convention, these are exposed as environment variables accessible via process.
Listing shows an example of how to retrieve a setting in Node. Connection strings are given special treatment within the portal, beyond that offered to app settings, in that you can specify a type for the connection string to identify it as a SQL server, MySQL, a SQL database, or a custom connection string. Additionally, the values for connection strings are not displayed by default, requiring an additional effort to display the values so that their sensitive data is not displayed or editable until speciically requested by the portal user.
Just as for app settings, the mechanism you use to access connection string values de- pends on the web platform in which your web application is programmed. NET, then you access the values of connection strings just as you would access the connectionStrings values stored in web. If your web application is built using an- other supported web platform, such as Node. Deining a connection string in the management portal existing portal To deine a connection string in the management portal, complete the following steps: Scroll down to Connection Strings.
Click Save on the command bar to persist and apply the new connection string. Deining a connection string in the management portal Preview portal To deine a connection string in the Preview portal, complete the following steps: Using a connection string from. NET To retrieve a connection string, use the ConnectionStrings property of the ConigurationMan- ager class, and access the setting by name as the index into ConnectionStrings.
ConnectionString; Objective 1. Changes made to these settings at run- time are not persisted and may be lost if your application or its VM host restarts. If you need to alter these settings, you can do so manually via the portal or you can use the Azure Management API, Windows PowerShell, or xplat-cli to change them at the website level.
Deining and using request handler mappings Request handler mappings, or handlers, instruct websites how to handle requests for iles with particular ile extensions by running a script that processes the request. These handlers are invoked instead of websites performing further processing on the request for example, if a handler is conigured, the request does not get to ASP.
Deining a handler mapping in the management portal existing portal To deine a handler mapping in the management portal, complete the following steps: Scroll down to Handler Mappings. Note that this value must be an absolute path. Click Save on the command bar to persist and apply the new handler. Deining a handler mapping in the management portal Preview portal To deine a handler mapping in the Preview portal, complete the following steps: Deining and using virtual directories and virtual applications You can use virtual directories to logically deine a hierarchy of web content that is potentially different from the physical directory structure of the web content as it appears on disk.
You can change how the hierarchy is exposed to the browser without altering the ile structure, and you can collapse deeply nested directory structures by representing them with a top- level virtual directory.
You can also isolate a virtual directory within its own w3wp. A common scenario is to expose a subdirectory of wwwroot as the root website while also exposing a peer to that subdirectory as a separate web application. For example, under wwwroot, you might have three separate web applications: You could conigure each of these to run as a separate web application within the same website by coniguring them as virtual applications.
Deining a virtual directory in the management portal existing portal To deine a virtual directory in the management portal, complete the following steps: Scroll down to Virtual Applications And Directories. Note that this value must be a path relative to the site root.
To make this virtual directory a virtual application, select the Application check box. Click Save on the command bar to persist and apply the new virtual directory or virtual application changes. Deining a virtual directory in the management portal Preview portal To deine a virtual directory in the Preview portal, complete the following steps: Click Save on the command bar to persist and apply the virtual directory or virtual application changes.
To map to a more user-friendly domain name such as www. Additionally, to enable your visitors to securely browse your website using HTTPS, consider using certiicates bound to the domain name you have selected.
This map- ping is captured in domain name system DNS records that are maintained by your domain registrar. Two types of DNS records effectively express this purpose: Table shows some common scenarios along with the type of record, the typical record name, and an example value based on the requirements of the mapping.
These are the high-level steps for creating a custom domain name for your website: Ensure that your website is in the correct web hosting plan mode. If using an A record, collect the IP address of your website from the management portal.
If using an A record to map your domain to Azure, add a CNAME record with a subdomain of awverify to prove to Azure that you own the domain name you want to point to your website. Associate the custom domain name with your website by editing its coniguration. You cannot map a custom name to your website if it is in Free mode.
Coniguring a custom domain existing portal To conigure a custom domain in the management portal, complete the following steps: Ensure your website is in the correct web hosting plan mode: Navigate to the Scale tab of your website in the management portal accessed via https: Verify that the mode is set to Shared, Basic, or Standard. If using an A record, collect the IP address of your website from the management portal: Scroll down to Domain Names.
Click Manage Domains. If using an A record to map your domain to Azure, add a CNAME record with a subdomain of awverify to prove to Azure that you own the domain name you want to point to your website: Following the instructions provided by your domain name regis- trar, add a new CNAME record with the name awverify and the value awverify. Save your DNS changes. Note that it may take some time for the changes to propagate across DNS.
In most cases, your changes will be visible within min- utes, but in some cases, it may take up to 48 hours. Associate the custom domain name with your website by editing its coniguration: When you stop typing, the dialog box will validate the value you entered by checking for the CNAME record you created previously. If the validation fails, you may have to wait a little longer for the DNS settings to propagate, or you may need to check the DNS coniguration you made in step 4.
Click the check mark to associate the custom domain name with your website. Coniguring a custom domain Preview portal To conigure a custom domain in the Preview portal, complete the following steps: Click the ellipses On the Web Hosting Plan blade, ensure that the selected web hosting plan is not in Free mode the mode appears directly below the plan name. You can check the status Objective 1. When you tab out of the text box, the dialog box will validate the value you entered by checking for the CNAME record you created previously.
Click Save on the command bar to associate the custom domain name with your website. This can also happen unintentionally if you reach your spending limit and the website is changed to the Free web hosting plan mode.
If the IP address changes and you are using an A record to map your custom domain to your website, you will need to update the value of the A record to use the new IP address. There are multiple types of SSL certiicates, but the one you choose primarily depends on the number of different custom domains or subdomains that the certiicate secures.
Some certiicates apply to only a single fully qualiied domain name sometimes referred to as basic certs , 26 CHAPTER 1 Design and implement websites www. This wildcard certiicate creates two possible though remote vulnerabilities: In this case, the certiicate cannot be trusted to help users identify that the website they are accessing is truly yours. Using certiicates with your custom domain Custom domain names and SSL certiicates are inextricably linked. In fact, to create a certii- cate, you need a custom domain name.
The following are the high-level steps for obtaining a certiicate: Complete the steps for enabling a custom domain for your website. Create a certiicate signing request CSR on a local machine using one of the tools listed in Table Request a certiicate from a certiicate authority, and submit your CSR as a part of that request.
After obtaining the certiicate, download the IIS-compatible certiicate to the same local machine you used to generate the CSR. Bind your domain name to the uploaded certiicate using the portal. Table lists the tools commonly used to request the CSR step 2 and to export the certiicate step 5 and provides selection guidance. Makecert Windows with Visual Studio Use if you are developing with Visual installed Studios on Windows and want to create a self-signed certiicate.
Assuming you already have a website properly conigured with a custom domain name, you can explore the steps for getting and using a certiicate in greater detail. For the purposes of this chapter, the following discussion focuses on using Certreq.
Complete the following steps to ensure your certiicate meets the requirements: Use Certreq. You can create this ile in the text editor of your choice.
Save this ile with any name you choose, although naming it with the subject name can be helpful if you need to regenerate the CSR later. For example, name it yourwebsitename. After you create the. From the Start menu or Start screen, run Cmd. The exact approach will vary by certiicate authority, but you will typically either upload the CSR or be directed to open the CSR in a text editor, copy the contents, and paste them into a ield in a form on the webpage. Download this ile to the same local machine that you used to generate the CSR.
When you make a request to create such a certiicate, the certiicate authority will contact the owner of the domain to conirm that the requestor of the certiicate in fact owns the domain. Since Microsoft owns the azurewebsite. Next, install the certiicate from the. To do this, complete these steps: Navigate to the ile in Windows Explorer, right-click it, and select Install Certiicate.
The Certiicate Import Wizard appears—you can leave the default values on each page and click Next until the import is inished. To export the certiicate as a.
In the navigation pane, expand the Personal folder, and then click the Certiicates folder see Figure In the details pane, click the Issued To column header to sort the listing by the subject name.
In the listing, locate the item that matches the subject name you entered, right-click the certiicate, select All Tasks, and then select Export. Click Next. On the Security screen, select the Password check box and enter and conirm a pass- word. Remember this password; you will need it later when uploading your certiicate to Azure. Finally, on the File To Export screen, select a ile name path for where to export your. A good practice is to export it to the same direc- tory as your.
Uploading your certiicate to Websites existing portal To upload your certiicate to Azure Websites in the management portal, complete the following steps: Scroll down to Certiicates and click Upload A Certiicate. In the dialog box, browse to and click your. Click the check mark to upload the certiicate. In the Upload Certiicate blade, browse to and click your. Click Save on the command bar to upload the certiicate.
Coniguring SSL bindings With the certiicate uploaded to Azure Websites, the only remaining step is to bind the certiicate for use with a custom domain. Binding is what enables Websites to map a request from a client to the appropriate certiicate to use for securing communication. Binding your SSL certiicate to a custom domain existing portal To bind your SSL certiicate to a custom domain in the management portal, complete the following steps: In the dialog box, browse to your.
Click Save on the command bar to apply the binding. Essentially, its function is very practi- cal; it enables a client to indicate the host name of the server it is trying to access during the TLS handshake that sets up the secure connection, and then the web server is able to use this name to select the appropriate certiicate from its certiicate store to use in securing the communication with the client.
This enables greater website density per web server because it allows a single web server host to provide HTTPS across different websites, where each is accessed using a different domain and using its own certiicate for securing communication.
Contrast this with the IP-based approach, which is limited to one certiicate per IP address. To host multiple websites each with different certiicates, you would typically need multiple hosts each with a different IP address. In the context of Azure, SNI frees Websites from hav- ing to dedicate an IP address which are a limited resource to a single website—leading to greater hosting eficiency and, ultimately, cost savings.
The primary obstacle to using SNI is browser support—legacy browsers do not support it and will display certiicate warnings. However, the list of modern browsers supporting SNI is not insigniicant, and it includes the most common browsers in use today: Managing websites by using the API, Windows PowerShell, and the Cross-Platform Command Line Interface xplat-cli In addition to coniguring and managing Websites via the management portal, programmatic or script-based access is available for much of this functionality and can satisfy many develop- ment requirements.
The options for this include the following: These are the APIs the man- agement portal utilizes behind the scenes. The best place to start learning about these is the blog http: For details on using the Azure cmdlets, visit http: For details on using the xplat-cli, visit https: Your new website is almost ready for a production launch, and you are tasked with determining the order of steps to take in preparing the deployment with regards to setting up SSL and coniguring the custom domain name. Which should you acquire and set up irst: If you are developing a Node.
Windows PowerShell B. Management portal D. None of the above 3. Which of the following changes require you to update your DNS settings if you are using an A record to map your custom domain to your website? Deleting and re-adding the SSL certiicate B. Deleting the website and re-deploying C. Switching your web hosting plan to Free tier and then back to Standard Objective 1.
Conigure diagnostics, monitoring, and analytics Operating a website without suitably coniguring and leveraging diagnostics, monitoring, and analytics is like relying exclusively on your users calling to tell you about their experiences, what is working, and what is not.
Without diagnostics, monitoring, and analytics, you cannot reac- tively investigate the cause of a failure, nor can you proactively prevent potential problems before your users experience them. Azure Websites provides multiple forms of logs, features for monitoring availability and automatically sending email alerts when the availability crosses a threshold, features for monitoring your website resource usage, and support for remotely debugging web application code.
The following list describes each of these logs: Only one XML ile is created per website. One error message is captured per HTML ile. One failed request trace is captured per XML ile. For ASP. NET applications, these are created by invoking the logging methods in the System.
Trace class. Java, Node. The Log Files folder is physically located at D: Application diagnostic logs. Launch Visual Studio. From the View menu, select Server Explorer. Expand the node labeled Azure. If you are prompted to log in, log in with your organizational account or the Microsoft account that is associated with the website you want to manage.
Expand Websites. Expand the website you want to manage. Expand the Log Files folder to reveal the subfolders listed in Table , which contain the various diagnostic log iles. Expand any of the subfolders until you get to the desired ile listing, and then double- click the ile to download and open it within Visual Studio.
Alternately, to download the entire Log Files folder, complete the following steps: In Server Explorer, right-click the website whose log iles you want to download. Select View Settings. Click the Logs tab. There are always two such folders because one is for your website and one is for the Site Control Manager also known as Kudu that runs in parallel to your website. In addition to being able to download and view your application diagnostic logs, you can view them line by line as they are generated in real time in response to activity on the website.
The Output window appears and updates to indicate it has connected to the log streaming service. When the window is connected, any requests that generate application diagnostic trace output should cause the trace to appear in the output window. Retrieving diagnostic data using Site Control Manager Kudu Site Control Manager SCM also known as Kudu is a parallel website that is available with every deployed website, providing various management functions.
In particular, it can be used to access and view diagnostic log data using only the browser. To access SCM, you must have administrator rights to the website. If you can access the website via the portal, then you will be able to access SCM. To retrieve data using SCM, complete the following steps: Open your browser, and navigate to https: If you are not currently logged in with your organizational account or Microsoft ac- count, you will be prompted to log in.
Be sure to use the credentials you would use to manage the website in the portal. When you are logged in, click the Debug console menu, and select CMD. In the screen that appears, you can explore the local ile system of your website using a tabular view top part of the screen and a command line view bottom part of the screen. In the tabular view, click the LogFiles folder. A screen showing the root of all your log iles appears. To view any of the iles, click the download button the left-most icon next to any ile.
To download a complete subdi- rectory such as the entire DetailedErrors folder , click the download button to the far left of any subdirectory. To do this, log in to the SCM website for your website, and complete the following steps: From the Tools menu, select Log Stream. When the page loads, you are connected to the log streaming service and can view the log entries as they are created in real time. Ensure the cmdlets are installed and conigured to connect to your subscription, and then use the command shown in Listing to stream your diagnostic logs.
When the xplat-cli is installed, make sure that the default account is set to the subscrip- tion containing the website you are interested in, and then you can retrieve diagnostic data. To download your diagnostic logs, from the command prompt, type the command shown in Listing When prompted for the website slot, press Enter to accept the default, or type the name of the slot and then press Enter.
The diagnostic logs will download to your current directory as a ile named Diagnostic. To connect your command window to the log-streaming service, enter the command shown in Listing You will be connected to the log-streaming service and able to view the log records as they come in. To do so, you must irst set your deployment credentials for your website these are different than your organizational or Microsoft account credentials used to access the portal.
When those credentials are set, using the FTP client your choice, connect to the FTP host and enter your credentials to log in. From the folder you connect to, drill down to the LogFiles folder where you can download your diagnostic logs. In the dialog box that appears, enter a username and password, and then conirm that password. Click the check mark to save the deployment credentials, which are your FTP credentials. This is your username for FTP.
Collect the FTP endpoint to connect to. When prompted, enter your credentials.
Scroll down to Deployment and click Set Deployment Credentials. On the blade that appears, enter a username and password, and then conirm that password. Click Save on the command bar.
Return to the blade of your website, click Settings, and then click Properties. Coniguring diagnostics The portal makes the coniguration of diagnostic data a straightforward process, but you can also use the Azure PowerShell cmdlets and the xplat-cli to achieve the same results.
Coniguring diagnostic data collection existing portal To conigure diagnostic data in the management portal, complete the following steps: Scroll down to Application Diagnostics. Application diagnostic logs are conigured using the controls in this section. To enable collection of application diagnostic logs to the local ile system of the web- site, change the Application Logging File System option to On, and select a logging level.
To enable collection of application diagnostic logs to Table storage, change the Application Logging Table Storage option to On, and select a logging level.
Click Manage Table Storage to choose a storage account from within your active subscrip- tion, as well as to create a new table or to write the log data to an existing table. Click the check mark to close the dialog box.
To enable writing the diagnostic logs to iles in Blob storage, change the Application Logging Blob Storage option to On, and select a logging level. Optionally, select the Set Retention check box and enter a number of days to keep the log iles.
Click Man- age Blob Storage to choose a storage account from within your active subscription, as well as to create a new blob container or to write the log data to an existing blob container. NET applica- tions. While the portal may let you enable it for any website, log data will be collected to Azure Storage only from a.
NET application. To conigure web server logs, detailed error message logs, and failed request tracing logs, on the Conigure tab, scroll down to Site Diagnostics. To enable writing the diagnostic logs to the local ile system of the website, change the Web Server Logging option to File System and set a quota for the space consumed by these logs to between 25 and MB.
To enable writing the diagnostic logs to Blob storage, change the Web Server Log- ging option to Storage. Click Manage Blob Storage to choose a storage account from within your active subscription, as well as to create a new blob container or to write the log data to an existing blob container.
To enable writing of detailed error message logs to the local ile system of the website, change the Detailed Error Messages option to On. To enable writing of failed request logs to the local ile system of the website, change the Failed Request Tracing option to On.
After completing your application and site diagnostic coniguration, be sure to click Save on the command bar to apply the changes to your website. Coniguring diagnostic data collection Preview portal To conigure diagnostic data collection in the Preview portal, complete the following steps: Under Summary, click Settings, and then click Diagnostic Logs.
On the Logs blade, switch the desired logs to the On position. Click Save. This log is always enabled. NET application running in Websites. When you are remote debugging, you can use Visual Studio to set breakpoints, examine variable values, and step through code. To debug a deployed website, you must ensure that it is a debug build for example, it has the debug symbols. After you have deployed a debug build, complete the following steps to start a debug session within Visual Studio.
Ensure the project you are debugging is built and that you have made no changes to it since you deployed it to Websites. If prompted to log in, login with your organizational account or the Microsoft account that is associated with the website you want to manage. Right-click the website to debug and select Attach Debugger. If you have never attached the remote debugger before, this process might take up to 30 seconds as it automatically conigures the website for debugging. Also, if you spend more than a few minutes stopped at any one breakpoint, Azure will treat your Websites worker pro- cess as having become unresponsive and try to restart it, so be prepared to move quickly when attached with the remote debugger to a website.
Coniguring endpoint monitoring You can use endpoint monitoring to leverage Azure to provide outside-in monitoring of your website.
That is, you leverage a service remote to your website, possibly in multiple regions around the world, to periodically ping your website to assess its health.
To enable endpoint monitoring, provide the URL of the endpoint on your website that it should ping, and choose where you want to ping from. The results of these pings appear in the status dashboards for your website and can also be used to create alerts that send out an email when the results fall outside of thresholds you conigure. Scroll down to Monitoring. Provide a short name for the endpoint and the URL you want Azure to ping. Also pick from one to three locations from which to ping.
To add another, different URL to ping, ill in the row that was added as soon you started typing in the irst row. Click Save on the command bar to apply the changes. Coniguring endpoint monitoring Preview portal To conigure endpoint monitoring in the Preview portal, complete the following steps: Scroll down to Monitoring and click Webtests. On the Create Test blade that appears, specify a name for this test endpoint, the URL, and the test locations.
Click Create. Coniguring alerts You can conigure rules for your website to evaluate metrics you specify and, when the values of those metrics exceeds your designated threshold, to send an email to a service administra- tor, a co-administrator, or to an email address you specify. Coniguring alerts existing portal To conigure alerts in the management portal, complete the following steps: In the main navigation pane, click Management Services.
On the Alert tab that appears, click Add Rule on the command bar. In the Deine Alert dialog box, provide a short name for your alert, as well as a descrip- tion to help you understand the alert in the future. From the Service Type drop-down list, select Web Site, and from the Service Name drop-down list, select the website for which you are coniguring an alert. Click the right arrow to move to the next step.
In the Deine A Condition For Notiications dialog box, choose the metric to deine your threshold condition. If you have enabled endpoint monitoring for the selected website, in addition to the standard set of metrics memory, CPU, data and HTTP status counts, and so on , there are also entries for response time and uptime as measured from each of the conigured monitoring locations. Select a window of time over which to compute the rule. Set the desired email actions by selecting the appropriate check boxes.
Click the check mark to create the new rule, automatically enabled. Coniguring alerts Preview portal To conigure alerts in the Preview portal, complete the following steps: Scroll down to Operations and click Alert Rules. On the Alert Rules blade, click Add Alert. On the Add An Alert Rule blade, choose the metric to deine your threshold condition. If you have enabled endpoint monitoring for the selected website, in addition to the standard set of metrics memory, CPU, data and HTTP status counts, and so on , there are entries for response time and uptime as measured from each of the conigured monitoring locations.
From the Period drop-down list, select a period of time over which to compute the rule. Additionally, if desired, enter an email address in the Additional Administrator Email text box. Click OK to create the new rule. Monitoring website resources existing portal To monitor website resources in the management portal, complete the following steps: To examine resource usage against your web hosting plan quota, navigate to the dashboard of your website in the management portal accessed via https: Depending on the web hosting plan mode, you will see the quotas that are in effect and how your consumption compares to the cap.
For example, a website in the Free web hosting plan mode will show resource consumption for CPU Time, data transfer out, usage of the local ile system, and memory usage. However, a website in the Stan- dard mode will show only ile system storage. On the dashboard, you can also view the status of your monitored web endpoints. To view detailed metrics for your website, navigate to the Monitor tab.
A chart of the collected metrics is displayed above a table of the same metrics. To add additional metrics, click Add Metrics on the command bar, and select the desired metrics or endpoint statistics. To view the status of conigured alert rules, in the main navigation pane, click Manage- ment Services.
This screen will provide you with a list of all the alerts you have conig- ured, along with their status. To view the audit log of management events that have occurred, on the Management Services page, click Operation Logs.
To examine resource usage against your web hosting plan quota, navigate to the blade of your website in the portal accessed via https: Scroll down to Usage and click Quotas. For example, a website in the Free web hosting plan mode will show resource consumption for CPU Time, data trans- fer out, usage of the local ile system, and memory usage.
However, a website in the Standard mode will show only memory and CPU usage. On the Website blade of your website, click Webtests to view the status of your monitored web endpoints. To view detailed metrics and alert status for your website, return to the Website blade of your website and scroll down to Monitoring.
Click Requests And Errors. To view the audit log of management events that have occurred, return to the Website blade of your website and scroll down to Operations. Your website has gone live and you are planning what strategies you might employ for monitoring and diagnostics. What features would give you early warning of problems with the website so you can respond to them proactively?
What features could you use to diagnose an issue retroactively so that you can perform root cause analysis and ix the problem? Which of the following tools would you not use to diagnose a problem on a produc- tion site to avoid disturbing visitors while diagnosing?
Log streaming B. Remote debugger C. Event log D. With endpoint monitoring, you can perform all of the following except what? Conigure alerts to send automated emails B. Auto-scale C. Perform outside-in monitoring D. Monitor from multiple geographic locations 3. Organizes its coverage by exam objectives Features strategic, what-if scenarios to challenge you Assumes you have experience designing, programming, implementing, automating, and monitoring Microsoft Azure solutions, and are proficient with tools, techniques, and approaches for building scalable, resilient solutions About the Exam Exam focuses on skills and knowledge for building highly available solutions in the Microsoft Azure cloud.
About Microsoft Certification This exam is for candidates who are experienced in designing, programming, implementing, automating, and monitoring Microsoft Azure solutions. See full details at: January 18, Categories: English Publisher: Retail Price:. BookShout Price:. Print books are available for download with a minimum order of 50 books.
Readers Also Liked New York Times Best Sellers: Configure websites for scale and resilience Configuring auto-scale using built-in and custom schedules Configuring auto-scale by metric Changing the size of an instance Configuring Traffic Manager Objective summary Objective review Objective 1.
Design and implement applications for scale and resilience Selecting a pattern Implementing transient fault handling for services and responding to throttling Disabling Application Request Routing ARR affinity Objective summary Objective review Answers Objective 1. Thought experiment Objective 1. Objective review Objective 1. Objective review Chapter 2. Create and manage virtual machines Objective 2. Configure VM networking Configuring DNS at the cloud service level Configuring endpoints with instance-level public IP addresses Configuring endpoints with reserved IP addresses Configuring access control lists Load balancing endpoints and configuring health probes Configuring Direct Server Return and keep-alive Leveraging name resolution within a cloud service Configuring firewall rules Objective summary Objective review Objective 2.
Design and implement VM storage Planning for storage capacity Configuring storage pools Configuring disk caching Configuring geo-replication Configuring shared storage using Azure File storage Objective summary Objective review Objective 2. Thought experiment Objective 2. Objective review Objective 2. Objective review Chapter 3. Design and implement cloud services Objective 3. Design and develop a cloud service Installing SDKs and emulators Developing a web or worker role Design and implement resiliency Developing startup tasks Objective summary Objective review Objective 3.
Configure cloud services and roles Configuring instance size and count Configuring auto-scale Configuring cloud service networking Configuring local storage Configuring multiple websites in a web role Configuring custom domains Configuring caching Objective summary Objective review Objective 3. Deploy a cloud service Packaging a deployment Upgrading a deployment VIP swapping a deployment Implementing continuous delivery from Visual Studio Online Implementing runtime configuration changes using the management portal Configuring regions and affinity groups Objective summary Objective review Objective 3.
Monitor and debug a cloud service Configuring diagnostics Profiling resource consumption Enabling remote debugging Enabling and using Remote Desktop Protocol Debugging using IntelliTrace Debugging using the emulator Objective summary Objective review Answers Objective 3.
Thought experiment Objective 3.