Git Product home page Git Product logo

asa's People

Contributors

benperk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

asa's Issues

various typos

I've identified typos by preceding the incorrect text with a quote including the correctly spelled word:


  1. pg. 275 2nd para., beneath fig. 4.24. : alteration | ...VM is a significant altercation. ...
  2. pg. 283 1st para. 2nd line : drop-down | ... The managed disk types in the table should be familiar to you; they were the options in the drop-drop list for the OS disk type on the Disk tab when creating an Azure VM in the portal. ...
  3. pg. 339 1st para. : deprecated | .. There was a product before AKS named Azure Container Service (ACS) that is being depreciated and replaced by AKS. ...
  4. pg. 546 1st para. : Lift and shift | Life and shift can go directly to PaaS in many cases, and there are real benefits to doing so, such as autoscaling no longer being required for load balancing and delegating the responsibility for the management of operating systems and software libraries.
  5. pg. 547 1st para. : Cloudyn | ... The other way to optimize is by using Azure Cost Management and Cloudy, both of which were introduced in Chapter 1. ... (additionally: the Cloudyn product is deprecated at the end of 2020, so there ought not to have been any mention of it in this document. It's also mentioned in Chapter 1. To reduce confusion, IMO, it should be removed.
  6. pg. 549 3rd para. : BCDR | ... The configuration of a BDCR is relatively complicated ... (additionally: the typo error is repeated twice more in the 1st para.)
  7. pg. 550 1st para. : Azure Migrate | Also, you can recognize the complexities behind the logic that would help very much in scenarios where Azure Monitor doesn’t provide a migration path for you. (additionally: I'm sure that Azure Monitor should read as Azure Migrate. The same error appears in the last para. on pg. 550).
  8. pg. 615, 2nd para. : Mitch Radcliffe | Mitch Radcliff is spelled incorrectly, it's actually Mitch Radcliffe with an "e". The quote is incomplete as well, the quote is actually: "A computer lets you make more mistakes faster than any other invention in human history -- with the possible exceptions of handguns and Tequila."
  9. pg. 640, last para. : enhancements | Some of those enchantments cannot be added to Azure VM metrics due to compatibilities, which is the reason for the differences.

Azure study guide - Chapter 7 issues

As a generalisation, I wonder how much of Chapter 7 is directly relevant to the exam? There is so much to absorb in prep for the exam, I wonder if it's beneficial to cut out some of the "fat"? It remains interesting reading, but nevertheless.

Azure study guide - Chapter 1 issues

Issues such as typos/errors relating to Chapter 1 - Gaining the Azure Solutions Architect Expert Certification

p.13 - Should be "Shared Access Signature (SAS)", you have "Storage Access Signature (SAS)
p.23 - Does the VNET service endpoints for Azure SQL referenceing "still in preview" need updating?
p.683 - answer 20 - contradiction on availability of GPU

pg. 430,431: FIFO Azure Queues/Service Bus compared-contrasted

Confusing language:
Pages 430 & 431, the topic is Azure Queues --the content is ambiguous. Two individual paragraphs discuss FIFO processing but the paragraph on pg. 430 states that Azure Queues does not support FIFO usage. On pg. 431 we find: "... is used to enforce FIFO processing of Azure Queue messages." So a contradiction. I believe "does not guarantee FIFO usage" might be better terminology. Mentioning that Service Bus Queues do guarantee FIFO might be useful as well.
Reference: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted#additional-information.

Azure study guide - Chapter 3 issues

p.122 - having followed instructions to run an availability report, I get the error message "Long running operation failed with status 'InternalServerError'". Same issue for the "ProvidersList" command example. Still work for you?

P.136 - Answer "site-to-site" at bottom of page is wrong and contradicted by ExpressRoute in same sentence.

p.171 table 3.13 where/how is use Inboud or Outbound determined. For example, you have a VM with ElasticSearch deployed. You also have an App Service ruuning the web front end for search queries. You might want to have an NSG associated with the VNET subnet for the Elastic VM that restricts inbound HTTPS requests to the App Service app. This is an inbound scenario.
EDIT: Service tag definition here, could add this link to yoru page. I see App Service set as Outbound. Still, question remains, how to restrict inbound requests from App Services using service tags
https://docs.microsoft.com/en-us/azure/virtual-network/service-tags-overview

p.188 Azure privae DNS - you make 2 points re: differences. The first point you make could have more clarity, indiciating that its the PUBLIC DNS (exercise 3.11) that is piblicaly accessible, not the private DNS. Confusing as you go on to make the second point which speciifcally talks about the privae with azure.com.

AKS

etcd referred to as etdc. Reading via O’Reilly online

Azure study guide - Chapter 2 issues

p.57 "any issue can start" doers not make sense, perhaps rewrite as "any issue resolution can start..."

p.77 "The most important aspect to recognize is that Azure AD has a scope greater than that of Azure, while RBAC is specifically focused on the resources accessible via the Azure Portal" could be better written with more clarity

p.79 Simple example of each would go a long way to clarifying "note on difference between AAD and the RBAC model", which in itself could be better written.

p.88 table 2.9 - repeat of operation "write" for both update and delete/create custom role. EDIT - have the names of these actions actually changed to something like microsoft.directory/roleDefinitions..... ?

p.89 Update cmdlet names e.g. Get-AzureRmRoleDefinition > GetAzRoleDefinition

p.93 - Azure Security Center now called Microsoft Defender for Cloud
https://docs.microsoft.com/en-us/azure/defender-for-cloud/defender-for-cloud-introduction

p.684 - question 8. Correct answer is A (not B)

Azure study guide - Chapter 4 issues

p.280 - grammer - "use it remotely, that same as with Powershell"
p.339 - exercise 4.17 step 1 - typo - should be AKS in place of ASK
p.347 - "when you want to move an on-premise workload to an Azure VM, the tool of choice is Azure Migrate" contradicts earlier recommendation for Azure Site Recovery for doing the movinf, wheras Azure Migrate helps with the planning of the move.
p.686 - Q17 - correct answers should be A, C (not A, B)

Azure study guide - Chapter 5 issues

p.371 - It threw me that whilst discussing ADLS end of p.370, p.371 jumped back to ADF and HD. This paragraph woudl seem better placed within ADF.

p.376 - table 5.2 - table indicates Document DB cannot do aggregation, this is incorrect.

p.397 - needs a comma after "SQL injection attempts"

p.421 - Azure Cache for Redis - grammer - "There are five Azure Cache for patterns" - lose the "for"

p.427 - Typo in Azure blobs first sentence - "object otorage"

p.428 - Expand on page blobs, defining what is is in addition to typical use case (VHD) ?

p.430 - Azure queues - You say "first in, first out (FIFO), something that Azure Queues does not support" yet on p.431 say "which is what is used to enforce the FIFO processing of Azure Queue messages". This is contradictory, and the second parft incorrect. The MS documentation indicates storage queues do not provide an ordering guarantee:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted

p.436 - GRS - grammatical - "... the twin region provides compliance to the data restrictions would allow". Perhaps "that allows" or "that permits"

pg. 297 "Azure Site Recovery"

pg. 297 "Azure Site Recovery" is given as the answer to the question: "What is the best tool for moving an on-premise server or VM to an Azure Virtual Machine?", yet on pg. 347, 1st para. we find: "when you want to move an on-premise workload to an Azure VM, the tool of choice is Azure Migrate." ---seemingly a contradiction.
"So I would say that we should all start looking at ASR as being a disaster-recovery-as-a-service solution, and look at Azure Migrate, as the place to go if you want to migrate anything from anywhere in to Azure." ---> citations: what is difference between azure migrate and azure site recovery for migration
Azure Site Recovery v Azure Migrate: Server Migration

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.