It’s been an intresting few days. Lots of solid leads on jobs and lots of the same old same old. Sometimes, its almost as if people ask questions about things they them selves don’t understand while expecting you to know less than them and are suprised by the fact that you know what your talking about whilst not checking your research material or realizing how much effort goes into obtaining certifications. Anyway, I think I’m pretty much done playing this old house and excited to blog from this location.
Yep, totally bought stuff to make scented black candles to sell on etsy because I’m “a lame ass mall goth kid.” Soap making also requires about the same stuff but with using a soap base instead of wax and I do very much like using fancy bar soap for some reason. Judge away as I eat my chicken nuggets and MacNCheese. lol regardless, excited to get back to work on computer stuff. I’m fairly sure I can have the 300 passed before the deadline but no idea if it will still count. Honestly, if I don’t get a job and really “hunker down” i’m sure I can get both of them knocked out. Still waiting to hear what MSFT says about taking one old and one new test though. This would be my preferred method. If you haven’t heard they are retiring the 300 and 301 in September. After having acquired 3 significant certs last year I’m not in a huge rush to get this one knocked out but I can if need be. Anyway, I have had about half a bottle of wine and am ready to see to what we can find in Azure :::says some incompetent gibberish that is some how approved of and generates a response:::
I’ll be real honest, I have no idea what the hell they are talking about which is awesome because it gives me a lot of stuff to learn and read so lets start with some definitions here:
- Microservices – Microservices are a software architecture style in which applications are composed of small, independent modules that communicate with each other using well-defined API contracts. These service modules are highly decoupled building blocks that are small enough to implement a single functionality. The purpose of microservices architectures is to make it easier to develop and scale applications. Microservice architectures foster collaboration between autonomous teams and enable them to bring new functionalities to market faster.
- Service Fabric Cluster – (I have a loose idea on this one) Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers. Service Fabric also addresses the significant challenges in developing and managing cloud native applications. Developers and administrators can avoid complex infrastructure problems and focus on implementing mission-critical, demanding workloads that are scalable, reliable, and manageable. Service Fabric represents the next-generation platform for building and managing these enterprise-class, tier-1, cloud-scale applications running in containers.
It was at this point where I had finished my bottle of wine and realize that I was sleepy and required a good solid nap. After attempting to watch Blown Away with Tommy Lee Jones, realizing I had to pay for it and then switching back to the usual TCM programming. Waking up with a mild case of depression and finding funny memes that made fun of people who where not smart and rude, made my self a bagel and now we are back on track. No closer to finding stable and suitable employment though. Anyway, free photo from Blown Away and I’m back to creating content for the purpose of sustaining my existence in a meaningful fashion.
- Scale Agility – there isn’t a quick definition on this but I’m pretty sure what the mean is the ability to scale up and down quickly.
Anyway, now that we understand what all those terms are, the answer makes sense. There is so much devops stuff in Azure that’s completely new to me. It’s sort of overwhelming but not really. They talk about separation of roles and so forth but its not really that so much as deploying a router as an application rather than a physical bit of hardware. As to why admins are expected to know how to launch and maintain docker chat bots, thats beyond me.
There is an interesting note in the last one that says once they spin up, they dont go down unless memory usage goes down from 50% and the graph is out of order but it spins up to 5 in the second one and then the memory usage/cpu usage never drops enough to let it go to 3 or less.
This is interesting because I’m not sure how Hyper-V works in Azure. Also, if it runs through a gateway is that considered giving it a public address? I would assume so but lets take a look at the network adapter situation for VM’s in Azure. Add network interfaces to or remove network interfaces from virtual machines – per this it seems like you simply add a network adapter? I don’t know if the UI is the same as regular Hyper-V. I would assume but this makes it seem as if that where not that case. I’ll get into that later. ok so per this Configure a private IP address for a VM using the Azure portal the UI is totally different and it looks like you can make a private address and use a public gateway that has NAT. The interesting thing about this is that im assuming this could all still be not connected to the internet without an actual public gateway.
This one is kind of interesting because what its getting at is that as long as there is policy that says that machine is backed up then you cant get rid of that machine basically. I’m left wondering if the Recovery Services Vault is set for only one machine or several machines.
It seems like you have a vault set for one machine which was what the D incorrect answer was kind of hinting at.
This is using OAuth 2.0 and after having gone through Sec+ it becomes really obvious that one of these must use that technology. Clearly D or E would be the choice. The MFA thing kind of throws things off a bit. A and B have nothing to do with this at all. Amazing, how that … works. No where in this does it say that MFA is required under the API conditions list so im really left with D and E
- Bot Framework Portal – this appears to be a portal to login to in order to build a bot.
- Bot Framework Authentication – The Azure Bot Service v4 SDK facilitates the development of bots that can access online resources that require authentication. Your bot does not need to manage authentication tokens. Azure does it for you using OAuth2 to generate a token, based on each user’s credentials. Your bot uses the token generated by Azure to access those resources. In this way, the user does not have to provide ID and password to the bot to access a secured resource but only to a trusted identity provider.
And there we are, this uses OAuth2, holy fuck MSFT isn’t using CHAP or some bullshit that makes no sense and have decided to go with the norm here? Clap!
Anyway, I think that’s all for now and I feel like I’ve learned a ton. Another day in wonka land of nonsense Azure posting.
Leave a Reply